plan-to-bmad

To convert a project plan into BMAD-ready Markdown and JSON, you provide the plan or issue description to the skill, which then applies deterministic scope mapping, P0/P1/P2/P3 structuring, and touched-path allowlisting to generate governance-aware output templates for downstream story generation.

BMAD structuring in governance-heavy Claude Code projects is the process of transforming vague intent into standardized implementation input by capturing scope, risks, invariants, constraints, and repo-10x guardrails for later story generation within a process-specific main-merge worktree.

Yes, you can use this to transform CTO review notes into structured implementation input. The skill acts as a Universal CTO intake capture mechanism, converting existing plans or review results into the standard BMAD template without losing CTO guardrails.

Plan-to-bmad targets a process-specific main-merge worktree for output generation. It requires deterministic scope mapping and output templating to ensure the resulting Markdown and JSON files are correctly structured for downstream story generation in governance-heavy environments.

The best way to structure plan analysis for downstream story generation is to enforce P0/P1/P2/P3 structuring alongside invariants and constraints. This approach ensures the resulting BMAD-ready Markdown and JSON capture all necessary repository research and guardrails.

You need to apply touched-path allowlisting in plan transformation when working in governance-heavy Claude Code projects. It restricts scope to approved repository paths, ensuring the BMAD-ready Markdown and JSON output adheres to deterministic scope mapping and CTO guardrails.