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.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 install dir;
{project-root}
is the working dir.
{workflow.}
resolves to fields in
customize.toml
.
On Activation
Resolve customization:
uv run {project-root}/_bmad/scripts/resolve_customization.py --skill {skill-root} --project-root {project-root} --key workflow
. On failure, read
{skill-root}/customize.toml
directly.
Run
{workflow.activation_steps_prepend}
. Treat
{workflow.persistent_facts}
as foundational context (
file:
entries are loaded).
Resolve config:
uv run {project-root}/_bmad/scripts/resolve_config.py --project-root {project-root}
(merges
_bmad/config.toml
and the
_bmad/custom/
overrides). From the merged JSON resolve
{project_name}
,
{output_folder}
(under
core
), and
{date}
.
Detect mode.
Headless
when any of: no TTY, programmatic caller (another skill or non-interactive runner), or the first message pre-supplies all inputs and asks for an artifact path back.
Interactive
otherwise. In interactive mode, greet the user and mention that
bmad-party-mode
and
bmad-advanced-elicitation
are available for deeper exploration on any field.
Show more
Installs
1.1K
Repository
bmad-code-org/b…d-method
GitHub Stars
52.9K
First Seen
May 24, 2026
Security Audits
Gen Agent Trust Hub
Warn
Socket
Pass
Snyk
Pass