What problem does it solve? Turning vague ideas, brain dumps, PRDs, transcripts, or mixed multi-source material into a single canonical specification is error-prone: decisions get lost, capability IDs drift, and downstream planning steps consume inconsistent documents. This Skill produces a preservation-validated SPEC.md contract that every downstream BMad workflow can rely on. ## Core Features & Use Cases - Five-field kernel distillation: Converts any intent input into SPEC.md carrying Why, Capabilities (with stable CAP-N IDs), Constraints, Non-goals, and a testable Success signal. - Companion file management: Routes load-bearing overflow content (glossaries, diagrams, entity catalogs) into named companion files referenced from SPEC.md frontmatter. - Append-only memlog derivation: Records every decision in .memlog.md and re-derives SPEC.md from it, so updates never cause merge drift and capability IDs stay stable. - Two-pass self-validation: Checks coherence against eight Spec Law rules and walks the source claim-by-claim to confirm preservation. - Use Case: Paste a customer email thread and a meeting transcript, and receive a spec folder with SPEC.md, a glossary companion, and a memlog recording every decision, assumption, and open question. ## Quick Start Ask the assistant to distill the attached product brief into a BMad spec and validate it against Spec Law.
