prd

Kit Preamble — prd

Kit Script Root

Kit root: ${CLAUDE_PLUGIN_ROOT}

• Absolute path above → plugin install (substituted at load time; no project scripts/ dir): prefix every kit script command with it, e.g. bash <kit-root>/scripts/checkpoint.sh …. Absolute paths also work from worktrees.
• Literal ${…} placeholder above → standalone layout: run commands as written.

Project Context Detection

Run these checks silently at the start. Use results to adapt behavior:

• [ -f issues.md ] — if true, this project uses the sprint system. Respect issue numbering and STATUS.md.
• [ -f docs/sprint_state.md ] — if true and Status shows running, a sprint is active. Be aware of parallel work in worktrees.
• [ -f docs/prd_digest.md ] — if true, read it for quick project context before starting.

Kit Rules

• Verify gh auth status before any GitHub operation. Steps:

1. Determine the output path ($ARGUMENTS or PRD.md).
2. Check if the file already exists at that path.
3. Read docs/example_prd.md to load the reference PRD format. 3.5) Check if docs/brainstorm_notes.md exists. If it does, read it and use as additional context — problem space, target users, chosen direction. Pre-fill answers to questions already covered in the brainstorm notes. 3.6) Check if docs/business_analysis.md exists. If it does, read it and use as additional context — market analysis, competitive landscape, business model direction, risks.

If the file does NOT exist (New PRD):

4a) Ask the user to freely describe their product idea. 5a) Analyze the input and identify missing PRD sections (Background, Goals, Target User, User Stories, Functional Requirements, Non-functional Requirements, Out of Scope, Success Metrics, Technical Notes). 6a) Ask clarifying questions conversationally — one or two gaps at a time. 7a) When enough information is gathered, generate a PRD draft following the example format and present it to the user.