architecting

Feature lifecycle architecture governs a feature from concept to deployment across teams. You need it to enforce a consistent DESIGN, EXTEND, and BUILD workflow, ensuring architectural decisions and UX integrity are documented in spec.md files.

Generate feature specifications by creating a feature directory under src/features/{name} and using DESIGN mode. This mode produces a spec.md document detailing architecture decisions, dependencies, and design validation for the new feature.

Plan implementation for extending features by using EXTEND mode. It generates extension plans and implementation guidance, ensuring the evolved feature aligns with existing architecture and maintains UX integrity across teams.

Yes, the approach enforces a DESIGN/EXTEND/BUILD workflow. BUILD mode implements features using a layered, type-first approach with self-verification, ensuring alignment with the generated spec.md before deployment.

Maintain architectural consistency by applying end-to-end governance through the DESIGN/EXTEND/BUILD workflow. This provides guardrails for architecture decisions, generates spec.md documentation, and enforces self-verification during the build phase.

You can use it for both. DESIGN mode handles new feature architecture and spec generation, while EXTEND mode specifically handles evolving existing features with targeted extension plans and implementation guidance.