Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →aj-geddes/bmad-handoff
Emits a dev-tool-agnostic handoff manifest from ready-for-dev stories so an external dev plugin or runner can pick up and execute the work.
Passed 4 of 12 test cases with the skill, and 5 of 12 without it.
and 1 more in the full report
3 fixed4 passed either way11 still failing5 broke
Tokens, turns and time describe resource use, not a dollar price.
The instructions your model reads when the skill loads.
Purpose: Scan the planning output folder for all stories at status ready-for-dev,
compile them into a single handoff-manifest.json, and leave it where any downstream
dev tool can read it — without coupling to any specific runner.
This is the last artifact the planning plugin produces. What happens next is owned by the external dev tool, not by this skill.
Run this skill after the story-writing phase is complete and you (or the user) have
confirmed that at least one story carries status ready-for-dev. The manifest is a
point-in-time snapshot; re-run the skill to refresh it.
Use TodoWrite to track progress through these steps.
Look for bmad-output/project-context.md (the default output folder) or ask the
user for the output folder. Default: bmad-output/.
Glob for **/{epic}.{story}.*.story.md under the output folder.
Accept alternative flat layouts (stories/*.story.md) if the glob turns up nothing.
Read the **Status:** header field of each story file (in the story header block, not a
## Status heading). Include only stories whose status value is exactly ready-for-dev.
If none are found, report which statuses were seen and stop — do not produce an empty manifest.
For each qualifying story file, extract:
test cases passed, vs 5 / 12 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.