discussion-to-mattlisted
Install: claude install-skill pripanggalih/discussion-to-matt
Settle an open-ended design conversation into a **foundation** that governs every later feature, and an ordered set of **run sheets** that each drop you into the engineering skills already grounded.
Two ways in, one process. Called at the **start** of a build, this skill runs the design conversation itself — step 4 is a full grilling from zero. Called at the **end** of one, it opens from what that conversation settled and grills only the gaps. Either way the run ends the same: `docs/foundation/` written, and one run sheet per roadmap line.
**This skill completes the pipeline; it never stands in for a part of it.** Every engineering skill keeps its whole job. `/grill-with-docs` still holds the feature conversation, `/to-spec` still synthesises the spec, `/to-tickets`' granularity quiz is still its whole value, `/tdd` still makes the user confirm the seams, `/code-review` still reviews. What they lack is a starting position: a stack that was chosen, entities that have names, a seam registry to prefer from, and a definition of done with commands in it. That is the only gap this skill fills.
So the test for anything you are about to write is not "would this be useful downstream" — it is "does anything downstream already own this". Producing a downstream skill's output here does not save a step; it produces a second version that skill will contradict, with no way to tell which is authoritative.
Two rules bound what gets written. A fact belongs to the **foundation** if it stays