sdd-planning

Spec-driven development planning generates structured artifacts like SDD Plans and Weave Plans from feature specifications. This connects design documentation directly to executable plans, reducing ambiguity in feature delivery through disciplined, artifact-based scaffolding and cross-linking.

To generate an SDD Plan and Weave Plan, provide your feature specification and slug. The system scaffolds the plan artifacts at .specify/features/{slug}/plan.md and .weave/plans/{slug}.md, applying constitution checks and gate-based validation to ensure structured planning before execution.

Spec-driven development planning enforces governance through constitution checks. These validation gates block progress until your feature plan complies with defined principles, ensuring structured planning and compliance before any implementation execution begins within Weave.

You can use this spec-driven planning workflow to validate architecture documentation. It applies gate-based validation and constitutional checks to your feature specifications, ensuring architecture documentation meets compliance principles before bridging specification to execution within Weave.

The best way to structure feature planning artifacts is generating dual outputs: an SDD Plan at .specify/features/{slug}/plan.md and a Weave Plan at .weave/plans/{slug}.md. This aligns design with execution through cross-linked, artifact-based scaffolding and constitutional gate validation.