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 machine contract (SPEC.md plus companions) that every downstream workflow reads from one place. ## Core Features & Use Cases - Spec distillation: Converts any intent input into the five-field kernel (Why, Capabilities, Constraints, Non-goals, Success signal) using a configurable template, with stable CAP-N capability IDs preserved across updates. - Memlog-driven derivation: Records every decision in an append-only .memlog.md and re-derives SPEC.md from it, so multiple skills can update the same spec without merge drift. - Validation and story breakdown: Runs two-pass self-validation (coherence and preservation) against eight Spec Law rules, and optionally breaks capabilities into a stories.yaml file with human-set checkpoints. - Use Case: Paste a customer email thread and a meeting transcript, and receive a spec folder containing SPEC.md, a glossary companion, and a memlog with open questions flagged for human decision. ## Quick Start Ask the assistant to distill the attached product brief into a spec using the bmad-spec skill and return the spec folder path.