galaxyproject / galaxyproject/foundry

interview-to-freeform-summary is reviewed + pipelined but declares zero references

Open
#377 0 comments 0 reactions 0 assignees View on GitHub
priority/mvp roadmap/substep
Dominant language
TypeScript
Stars
2
Forks
3
Avg merge
1d 22m
Merged PRs (30d)
63

Description

_Filed by Claude (AI assistant) on behalf of @jmchilton._

## The inconsistency

`content/molds/interview-to-freeform-summary/index.md` is `status: reviewed` and a live phase in the `interview-to-galaxy` pipeline, yet it declares **no `references:` manifest at all**. It's the one outlier in the reviewed cohort — a promoted, actively-pipelined Mold with zero runtime references.

For contrast:
- Its downstream `freeform-summary` consumers (`freeform-summary-to-galaxy-interface`, `-data-flow`, `-template`, `-test-plan`) all carry references.
- The other producer of the shared `freeform-summary` shape, `summarize-paper`, also has no references — but it's still `draft` (undeveloped paper corner), so its emptiness is honest. `interview-to-freeform-summary` is the only *reviewed* producer with none.

## Why it matters

`references:` is what casting packages into the SKILL.md as runtime grounding (pattern pages, CLI manuals, research notes). A reviewed, shipped skill with an empty manifest runs with only its procedural body — no packaged guidance on the `freeform-summary` shape, interview normalization, or the uncertainty-preservation discipline the body itself stresses ("Don't over-specify").

Not a validation error — `references` is schema-optional — so this is a health/consistency gap, not a blocker.

## Scope

Figure out what the Mold *actually* leans on and add a real manifest (not a mirror of a sibling). Candidates to investigate:
- A pattern/research note on the shared `freeform-summary` handoff shape (paired with `summarize-paper`), if one exists or should.
- Any interview-conduct / requirements-elicitation guidance worth packaging.
- The uncertainty-vs-invention discipline the body describes — is there a note that codifies it?

If the honest answer is "it genuinely relies on nothing packaged," that's worth recording explicitly rather than leaving an implicit gap.

Contributor guide

No contributing guide indexed for this repository

Research direction

Read content/molds/interview-to-freeform-summary/index.md first, then inspect the sibling freeform-summary molds and available pattern or research notes for relevant grounding. Done means adding a genuine references manifest to that file, or explicitly recording why no packaged references are appropriate.

Written by the indexing model from the issue text.

Assessment

Domain
content, documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.