ring:pre-dev-full

A 9-gate pre-development workflow systematically guides teams through research, PRD creation, feature mapping, TRD, API design, data modeling, dependency decisions, and task breakdown to ensure traceable planning before implementation begins.

To start the pre-development workflow, initiate the guided process by providing your feature name and requirements, which creates the docs/pre-dev/<feature-name>/ directory and begins the Gate 0 research phase.

You need a gated pre-development workflow when planning large features that require cross-functional alignment among product, design, and tech leads, ensuring scope is validated and artifacts are auditable before implementation to reduce rework.

Yes, the pre-development workflow enforces technology selections at Gate 6 and loads prior artifacts during the process to accurately map dependencies and ensure traceable planning from the PRD down to subtasks.

The best way to ensure traceable planning from PRD to subtasks is to use an artifact-driven workflow that saves structured documents at each gate, requiring human approvals to validate scope and dependencies before moving forward.