// Turn a shaped project kickoff transcript into a reference document for the builder. Use when the user has a transcript (VTT, etc.) from a kickoff call and wants to produce a document that captures what was shaped and agreed.
Create a framing document from conversation transcripts. Use when the user has transcripts (VTT, call notes, etc.) and wants to produce a frame that captures the problem worth solving and why it was chosen over alternatives.
Use this methodology when collaboratively shaping a solution with the user - iterating on problem definition (requirements) and solution options (shapes).
Transform a workflow description into affordance tables showing UI and Code affordances with their wiring. Use to map existing systems or design new ones from shaped parts.
| name | kickoff-doc |
| description | Turn a shaped project kickoff transcript into a reference document for the builder. Use when the user has a transcript (VTT, etc.) from a kickoff call and wants to produce a document that captures what was shaped and agreed. |
Turn a kickoff call transcript into a builder-facing reference document for a shaped project.
Ask the user:
The transcript is your source material. The document is NOT a summary of the call — it's a map of the territory that was shaped.
A kickoff transcript is sequential — people talk through things in the order they come up, circle back, go on tangents, get sidetracked by browser issues. Your job is to reconstruct the territory they were describing, not replay the conversation.
Organize by the thing being built. Each section should describe one area of the system fully — so the builder can look up "how does the Criteria tab work?" and find everything in one place.
Do NOT organize by build sequence. If the team identified slices (a sequence of vertical slices to build in order), those are managed separately — not in this document.
The document has two top-level sections: Frame and Shape. Both are ## headings. Their subsections are ###.
## Frame)The strategic context and boundary conditions. This is NOT fluff — the builder needs this to make judgment calls when they hit ambiguity.
### Problem — Why this project, why now. What's broken or missing.### Outcome — The specific outcomes expected. What success looks like.## Shape)One ### section per area of the system. For each area, describe:
Do NOT include a Build Sequence section. Slices are tracked separately from this document.
The document is a record of shared understanding from the kickoff call.
For every sentence, you should be able to point to a moment in the transcript where someone said it or clearly meant it. If you can't, either cut it or flag it as your own synthesis.
Exception: Editorializing that clarifies or synthesizes what was said IS fine. "The criteria screen is how filtering is expressed in the new world" — nobody said that exact sentence, but it accurately captures a point made across several turns. That's the job: make scattered discussion legible without adding your own conclusions.
Do NOT create a grab-bag "Design Decisions" section. Instead, put each decision inline in the section where it matters.
If a decision only matters when building one specific area, it belongs in that area's section. The builder shouldn't have to cross-reference a separate decisions list while working on a specific screen.
### sections under ## Shape.## Frame with ### Problem and ### Outcome) from the framing/outcomes discussion (usually near the start of the call).### ...), pulling from wherever in the transcript that area was discussed. A single section may draw from moments scattered across the whole call.