architect-phase

Architecture annotation enriches user stories with API endpoints, database models, component names, and cross-cutting concerns. Run architect-phase after design completion to convert high-level stories into detailed specifications with implementation guidance, file paths, and import statements saved as enriched story artifacts.

The annotation process documents Context7 references, pattern implementations, and cross-references to reference repositories. It captures architectural decisions, import structures, and model definitions alongside endpoint specifications to provide complete implementation context.

Architecture annotation operates after design-phase completion. It assumes prior design decisions exist and enriches those outputs with implementation-level details—endpoints, models, components, and patterns—rather than establishing foundational architecture.

The annotation process uses scope references and existing solutions for guidance. It analyzes completed stories and applies reference repository patterns to generate appropriate endpoints, database models, and component structures aligned with established architectural conventions.

Architecture-annotated specifications include enriched stories with embedded API endpoints, database model definitions, component names, file paths, import statements, and architecture notes. Output is saved as structured story artifacts with cross-references and pattern documentation.

Reference repositories accelerate pattern discovery and consistency, but the annotation process can operate with scope references alone. Existing solutions guide endpoint and model generation, though custom definitions can substitute when standard references are unavailable.