bmad-spec

Distills ideas, PRDs, and transcripts into a five-field SPEC.md contract with companions.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/ArchaonHW/MingGoRTS --skill bmad-spec-archaonhw
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-spec
Source: https://github.com/ArchaonHW/MingGoRTS/tree/main/.agents/skills/bmad-spec
Command: npx skills add https://github.com/ArchaonHW/MingGoRTS --skill bmad-spec-archaonhw

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? Raw intent — vague ideas, brain dumps, PRDs, meeting transcripts — is too unstructured for downstream planning and implementation skills to consume reliably. This Skill condenses any input into a canonical SPEC.md kernel (Why, Capabilities, Constraints, Non-goals, Success signal) plus companion files, so every downstream BMad skill works from one machine-readable contract. ## Core Features & Use Cases - Spec distillation: Converts any intent input into the five-field kernel, routing overflow content (glossaries, diagrams, entity catalogs) into named companion files. - Append-only memory: Records every decision, capability, and assumption in .memlog.md and re-derives SPEC.md from it, so updates never drift or lose stable capability IDs. - Validation and story breakdown: Self-validates against eight Spec Law rules, and can interactively break a spec into a stories.yaml execution plan. - Use Case: Paste a messy customer email thread and receive a spec folder with SPEC.md, a glossary companion, and a memlog recording every decision and open question. ## Quick Start Ask the assistant to distill the attached PRD or idea notes into a BMad spec with a slug like "quarter-drop".

Frequently Asked Questions about bmad-spec

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I turn a PRD or idea into a structured spec?

Provide the PRD, brief, transcript, or idea notes as input and the skill distills it into SPEC.md with five fields: Why, Capabilities, Constraints, Non-goals, and Success signal. Overflow content like glossaries or diagrams is routed into companion files.

How do I update an existing spec without losing capability IDs?

Invoke the skill again with the same slug; it lands on the existing spec folder and updates in place. The append-only .memlog.md is the authority, so existing CAP-N IDs are preserved and new capabilities get the next unused number.

Can this skill run headless from another tool or script?

Yes. When invoked programmatically or without a TTY it runs headless and returns JSON with status and the list of files written. It blocks with defined error codes like insufficient_intent or missing_slug when input is inadequate.

What is the difference between SPEC.md and companion files?

SPEC.md holds the lean five-field kernel; companions hold load-bearing content that does not fit, such as glossaries, entity catalogs, and diagrams. Downstream consumers discover companions through the companions array in SPEC.md frontmatter.

When should I not use this spec skill?

Do not use it when the input is too thin to distill, such as a one-line idea with no context. In that case the skill suggests running bmad-prd first to draw out the vision before distillation.