bmad-spec

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

1|Updated Sep 18, 2026
One-click install
npx skills add https://github.com/PastaSus/egg-defender --skill bmad-spec-pastasus
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bmad-spec
Source: https://github.com/PastaSus/egg-defender/tree/main/.agents/skills/bmad-spec
Command: npx skills add https://github.com/PastaSus/egg-defender --skill bmad-spec-pastasus

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve? Raw intent — vague ideas, brain dumps, PRDs, meeting transcripts, or mixed notes — is too unstructured for downstream planning and development skills to consume reliably. This Skill condenses any such input into a canonical SPEC.md kernel (Why, Capabilities, Constraints, Non-goals, Success signal) plus companion files, creating a single machine-readable contract that every downstream BMad skill builds from. ## Core Features & Use Cases - Spec distillation: Transforms any intent input into the five-field kernel, routing overflow content (glossaries, diagrams, entity catalogs) into appropriately named companion files. - Update and validation: Re-derives specs from an append-only .memlog.md memory log, preserving stable capability IDs, and runs a two-pass self-validation (coherence and preservation) against eight Spec Law rules. - Story breakdown: Optionally breaks a spec into a stories.yaml file of independently shippable slices with human-set checkpoints, in interactive mode. - Use Case: Paste a messy Slack thread about a new feature and receive a spec folder containing SPEC.md, a glossary companion, and a memlog recording every decision — ready for PRD, UX, or architecture skills to consume. ## Quick Start Ask the AI to distill the attached product brief into a spec using the bmad-spec skill.

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 brain dump into a structured spec?

Provide the file path or paste the content, and the skill distills it into a SPEC.md with five fields: Why, Capabilities, Constraints, Non-goals, and Success signal. Load-bearing overflow content is routed into companion files like glossaries or diagram documents.

How do I break a spec into development stories?

In interactive mode, ask to break the spec into stories once SPEC.md exists. The skill walks capabilities with you conversationally and writes a stories.yaml file with per-story checkpoints and dispatch notes.

Can I update an existing spec without losing capability IDs?

Yes. Re-invoking the skill with the same slug updates the existing spec folder in place. Capability IDs are preserved from the append-only .memlog.md log, new capabilities get the next unused ID, and retired IDs are never reused.

What happens when the input is too vague to distill?

Sparse input triggers either an express mode that logs gaps as open questions, or a guided walkthrough of the five fields. If the input is genuinely too thin, the skill stops and suggests using a PRD skill instead of inventing answers.

Why should SPEC.md never be edited by hand?

SPEC.md is derived from .memlog.md, an append-only chronological decision log, on every run. Hand edits are overwritten on the next derivation, so all changes must be appended to the memlog to keep the contract consistent.