What problem does it solve? Turning vague ideas, brain dumps, PRDs, transcripts, or mixed multi-source material into a single canonical machine-readable contract is error-prone, and downstream planning steps drift when the spec is hand-edited by many contributors. This Skill produces a preservation-validated SPEC.md kernel plus companion files that every downstream BMad skill consumes. ## Core Features & Use Cases - Five-field kernel distillation: Extracts Why, Capabilities (with stable CAP-N IDs), Constraints, Non-goals, and Success signal from any intent input into SPEC.md. - Memlog-driven derivation: Records every decision in an append-only .memlog.md and re-derives SPEC.md from it, so updates never cause merge drift and capability IDs stay stable. - Companion management and self-validation: Routes overflow content (glossaries, diagrams, catalogs) into named companion files and runs two-pass validation against eight Spec Law rules. - Use Case: Paste a customer email thread and a rough feature list, 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 agent to distill the attached product brief into a spec using the bmad-spec workflow and return the spec folder path.