Help us improve
Share bugs, ideas, or general feedback.
From ironforge
Converts existing BMAD artefacts (brief, PRD, architecture) into Sudocode specs and issues. Invocable standalone on projects that already have BMAD docs. Checks which files exist, maps each to Sudocode, and generates a dependency graph between issues.
npx claudepluginhub romaindecoster/ironforge --plugin ironforgeHow this skill is triggered — by the user, by Claude, or both
Slash command
/ironforge:bmad-to-sudocodeThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are executing the Ironforge BMAD → Sudocode handoff. Your job is to read the existing BMAD
Distills any intent input (ideas, brain dumps, PRDs, RFCs, transcripts) into a validated SPEC kernel with five fields and companion files for BMad downstream workflows.
Manages sudocode specs and issues: view (show_spec, list_issues), create/modify (upsert_spec, upsert_issue), plan features, build dependency graphs, add feedback. Supports markdown editing and Obsidian-style links.
Guides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.
Share bugs, ideas, or general feedback.
You are executing the Ironforge BMAD → Sudocode handoff. Your job is to read the existing BMAD artefacts and persist them into Sudocode as specs and issues.
Do not regenerate or rewrite the BMAD docs. Work strictly from what exists.
Verify which BMAD files are present. Report status before doing anything.
| File | Path | Status |
|---|---|---|
| Brief | docs/briefs/brief.md | ✓ / missing |
| PRD | docs/prd/prd.md | ✓ / missing |
| Architecture | docs/arch/architecture.md | ✓ / missing |
If none of the three files exist, stop and tell the user:
No BMAD artefacts found. Run
/ironforge:bmad-analyzefirst to produce them.
If some files are missing, continue with what is available and note the gaps clearly.
Check if .sudocode/ exists and is initialized. If not, run:
sudocode init
Then check for existing specs and issues to avoid creating duplicates. If specs already exist, ask the user whether to update them or skip.
If docs/briefs/brief.md exists:
upsert_spec():
["brief", "top-level"]If docs/prd/prd.md exists:
upsert_spec():
["prd", "functional"]If docs/arch/architecture.md exists:
For each major component, create one technical spec via upsert_spec():
["architecture", "technical"]For each implementation task implied by the architecture, create one issue via upsert_issue():
After all issues are created:
upsert_issue()[issue-id] Title
└─ depends on: [issue-id] Title
Output a final summary:
## BMAD → Sudocode — Done
**Specs created:** X
**Issues created:** Y
**Artefacts skipped:** [list missing files]
**Next step:** /ironforge:implement
If issues existed before this run, report what was updated vs. created.