mcaf-feature-spec

To create feature specifications, generate or update docs/Features/<feature>.md using the canonical Feature-Template.md. This enforces consistent documentation by embedding business rules, user flows, Mermaid diagrams, verification plans, and a Definition of Done directly into the spec.

Maintain traceability by keeping ADR and architecture map references in sync within your feature specs. Mapping spec items to tests and architecture boundaries enables end-to-end verification and ensures explicit decisions align with the modules defined in your architecture overview.

Scope feature planning to specific architecture modules by referencing docs/Architecture/Overview.md when generating specifications. This ensures the feature spec accurately reflects system boundaries and maintains alignment with the broader architectural map.

Yes, you can update existing feature documentation. The process reads your current docs/Features/<feature>.md and applies the canonical template to refresh business rules, user flows, diagrams, and verification plans without losing your original context.

Testable requirements and explicit verification steps are needed to enable end-to-end verification and automate delivery speed. By mapping spec items directly to tests, you prevent manual planning inconsistencies and ensure clear, verifiable system behavior.

A complete feature spec should include business rules, user flows, system behavior, Mermaid diagrams, verification plans, and a Definition of Done. It must also maintain traceability to ADRs and architecture maps to ensure consistent and testable requirements.