bmad-spec

Topics in the source

• BMad Spec
• Overview
• Conventions
• On Activation
• Workspace
• Memory and derivation
• The Operation
• Load-bearing

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. 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 nearest folder containing bmad/, starting at the working dir and moving up through its parents. {workflow. } resolves to fields in customize.toml. 1. Resolve customization: node {project-root}/bmad/ade-runtime.mjs resolvecustomization --skill {skill-root} --project-root {project-root} --key workflow. Script not found: BMad is not set up here. Offer to run the bmad skill's setup, installing bmad first if you do not have it (npx skills add bmad-code-org/BMAD-METHOD --skill b

This is an excerpt. Refer to the complete source and its current requirements.