bmad-spec
Condense any input — an idea, brief, PRD, transcript, or mixed notes — into a short spec: one kernel file plus supporting files that downstream skills build from. Also updates and validates existing specs. Use when the user says "create a spec", "distill this into a spec", "validate this spec", or "update the spec"
Install
git clone https://github.com/bmad-code-org/BMAD-METHOD /tmp/BMAD-METHOD && ln -s /tmp/BMAD-METHOD/skills/bmad-spec ~/.claude/skills/bmad-spec
From README
BMad Spec Overview Canonical transformer for the BMad spec-kernel ecosystem. Takes any intent input — vague idea, brain dump, PRD, GDD, RFC, brief, Slack thread, customer email, meeting transcript, mockups, mixed multi-source — and produces spec-{slug}.md carrying the five-field kernel (Why, Capabilities, Constraints, Non-goals, Success signal) plus companion files for load-bearing content that does not fit or would bloat the kernel with expansive line-item detail. Together they are the machine contract every downstream BMad skill consumes. Multiple skills may call to update the same spec over time. Conventions Bare paths (e.g. assets/spec-template.md) resolve from the skill root. {skill-root} is this skill's dir; {project-root} is the nearest folder containing bmad/, starting at the working dir and moving up through its parents. {workflow. } resolves to fields in customize.toml.
