architecture

name

architecture

description

Route architecture using exact migration registry [{"unit":"architecture/default","routing":{"negative_boundaries":["Analyze the product problem and write feature-wide requirements.","Implement the approved architecture and modify production code.","Write a feature-level technical specification with work breakdown and test strategy."],"positive_triggers":["Create a 3-architecture.md component and data-flow design from the approved technical specification.","Document component responsibilities, integration points, and architecture decisions for the billing feature.","Update the existing feature architecture document after repository boundaries changed."]}}].

Architecture Documentation

Create or incrementally refine one feature-level docs/features/{slug}/3-architecture.md. Turn an accepted technical specification and verified repository boundaries into a durable component model, data flow, integration map, and architecture-decision record.

Stay at architecture-document scope. Do not invent product requirements, rewrite the parent technical specification, implement code, create execution tickets, update progress state, or perform Git mutations. Architecture advice that does not need a lifecycle artifact belongs to an answer-only consulting workflow.

1. Resolve the feature and inputs

Accept an explicit feature key, a contained feature-directory path, a canonical 2-tech-spec.md or 3-architecture.md path, or repository context. Resolve in this order: explicit path/key, current branch prefix, exactly one changed feature, then exactly one non-archived feature directory. Reject conflicts, traversal, absolute paths, symlink components, ambiguous changed features, and every other lifecycle-document form. Ask one concise question when no unique feature remains.

Read the complete parent technical specification, existing architecture document, relevant requirements, and active request links when present. A missing technical specification is Need Human unless the user supplied an equally concrete approved design. For a small change contained to one component and one flow, recommend keeping the architecture section in the technical specification and continue only when a separate lifecycle document is wanted.