GENERATE A PRD
Ship Track — Step 1
A campaign without a PRD is a fleet without orders. The /prd command interviews you in five structured acts, then produces a complete product requirements document — valid YAML frontmatter, feature breakdown, and deployment spec. No blank-page syndrome. No guessing.
SiskoWHY A PRD MATTERS
Every VoidForge command reads the PRD. It determines which build phases apply, which agents activate, and what stack gets scaffolded. A missing or incomplete PRD means the agents are flying blind — they will ask questions, stall, or build the wrong thing.
The /prd command eliminates this problem. It walks you through every decision — name, stack, auth, payments, deploy target, features — and outputs a file that the entire system can read without ambiguity.
THE 5-ACT INTERVIEW
Open Claude Code in your project directory and type:
/prdSisko runs a structured interview across five acts: vision and identity, technical stack, features and flows, deployment and infrastructure, and stretch goals. Each act produces a section of the final PRD. The output lands at docs/PRD.md with valid YAML frontmatter that every downstream command can parse.
The interview is feature-by-feature. Sisko does not ask vague questions — he asks specific ones: “Do users authenticate? With what provider? Do you need role-based access?” Every answer maps directly to a PRD field.
USING --CHALLENGE
If you want your PRD stress-tested before you build, add the challenge flag:
/prd --challengeThis activates Boromir — an adversarial reviewer who pushes back on every assumption. Scope too wide? He'll say so. Missing edge cases? He'll find them. Tech stack mismatch? He'll call it out. The result is a tighter, more defensible PRD that survives contact with reality.
Think of it as a red-team pass on your product plan. Your PRD comes out battle-hardened — and your campaign starts on solid ground.