mcaf-feature-spec

You create a feature spec by generating or updating a markdown document at docs/Features/ using a feature template. It enforces executable verification by including business rules, user flows, Mermaid diagrams, verification steps, and a Definition of Done.

The best way to align feature documentation with architecture is by enforcing concrete rules within your spec that create proper ADR references and architecture links. This ensures major feature work maintains verifiable architectural alignment.

You need to write a feature specification with Mermaid diagrams when planning major feature work, implementing non-trivial features, or when system behaviour changes. It provides a standard workflow to keep verifiable specs aligned.

No, this feature spec workflow does not require any dependencies or external components. It operates independently to formalize actionable feature work by generating or updating markdown documents with templates, Mermaid diagrams, and verification plans.

You update existing feature documents by applying the feature template to the current markdown file at docs/Features/. This adds or refines the Definition of Done, business rules, and verification plan to ensure the updated spec remains executable.