PRD Creation — WHAT and WHY Before HOW

When to use

• Starting new product or major feature
• User asks to "plan", "design", or "architect"
• About to write code without documented requirements
• Asked to create PRD or requirements document

Skip when

• PRD already exists and validated → proceed to next gate
• Pure technical task without product impact → TRD directly
• Bug fix → systematic-debugging

Sequence

Runs after: ring:researching-features (Gate 0) Runs before: ring:mapping-feature-relationships (Gate 2, Large track) or ring:writing-trds (Gate 2, Small track)