Plan

Turn an idea into a parent PRD plus thin vertical-slice GitHub issues, with marketing requirements captured in the same pass.

Output shape per feature:

• 1 parent PRD issue — durable product spec using the PRD template, labelled prd.
• N child slice issues — each one shippable by /ship in a single PR, labelled planned,afk,p{1,2,3}.
• M marketing issues — blog posts, launch assets, social content, labelled planned,hitl,marketing.

Philosophy

• Parent PRD is the durable context. Slices close and delete themselves; the PRD persists as the single source-of-truth for why the feature exists and how it hangs together.
• Thin vertical slices — each child issue cuts through every layer (schema → API → UI → tests) end-to-end. Not horizontal layers.
• AFK over HITL — prefer slices /ship can do autonomously. Mark hitl only when human judgement is genuinely required (design calls, sensitive UX, architectural forks).
• Marketing is part of shipping. A feature without launch content is a feature nobody hears about. Capture it at planning time, not as an after-thought.
• Quiz the user before creating. Never run ahead. Show the breakdown, get approval, then create.
• Durable issue text. No file paths, no line numbers, no code snippets. Describe behaviours and contracts.