bmad-spec

To consolidate fragmented product requirements from transcripts and PRDs, you distill multi-source inputs into a structured five-field kernel covering Why, Capabilities, Constraints, Non-goals, and Success signal, producing a canonical machine-readable contract.

A machine contract specification is a structured, validated document that distills project intent into a stable kernel and append-only decision log. You need one to maintain traceable requirements when managing complex product workflows across diverse input formats.

To maintain stable capability tracking when updating specifications, you use a preservation-validated append-only memory log file that ensures every decision and capability ID remains stable and traceable across updates.

Yes, you need the uv dependency installed to run the bmad-spec workflow automation, which processes multi-source inputs into a validated machine contract for requirements engineering.

Yes, you can use Slack threads, emails, and mockups as input formats. The skill synthesizes diverse inputs like transcripts and PRDs into a formal SPEC.md that downstream agents can consume as a single source of truth.

A limitation of using a spec-kernel ecosystem is the strict adherence required to its rules for capability tracking and load-bearing content management, meaning inputs must fit the five-field kernel structure of Why, Capabilities, Constraints, Non-goals, and Success signal.