- Home
- Skills
- Bacoco
- Bmad Skills
- Bmad Development Execution
bmad-development-execution_skill
- Python
61
GitHub Stars
4
Bundled Files
3 weeks ago
Catalog Refreshed
2 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstart where the catalogue uses aiagentskills.
npx veilstart add skill bacoco/bmad-skills --skill bmad-development-execution- CHECKLIST.md530 B
- REFERENCE.md11.7 KB
- SKILL.md3.2 KB
- WORKFLOW.md876 B
Overview
This skill implements developer-ready user stories end-to-end by producing code, tests, and traceable documentation. It emphasizes small, reviewable changes, strict testing discipline, and clear links back to requirements and architecture. Outputs include code diffs, test results, an updated story record, and an implementation-notes summary.
How this skill works
The skill first verifies prerequisites and restates the story scope from the provided story file. It plans the work, lists affected files and tests, applies incremental code changes with explanatory notes, runs required test suites capturing output verbatim, and updates the story status and implementation-notes. Blockers halt work and produce remediation steps rather than speculative changes.
When to use it
- You have a developer-ready story file and want it implemented in code and tests
- You say phrases like “Implement story X”, “Start coding”, or “Develop this story”
- Architecture references and UX guidance are available for the story
- You need traceable, test-driven delivery that maps to requirements and architecture
- You want small, reviewable diffs and a documented development summary
Best practices
- Confirm the story file and architecture refs before starting; do not proceed without them
- Keep changes minimal and focused to make reviews fast and safe
- Run the full test suite and include verbatim command output in the record
- Update the story’s Dev Agent Record with status, learnings, and risks
- Stop and document blockers; provide concrete remediation steps rather than guessing
Example use cases
- Implement a new API endpoint described in a prepared story with accompanying tests
- Complete a frontend feature using provided UX guidance and component architecture notes
- Add validation logic and unit tests tied to quality-plan scenarios from QA
- Deliver a backend change where architecture patterns and story acceptance criteria exist
- Produce an implementation-notes summary for stakeholder handoff after completion
FAQ
Work halts, the blocker is documented in the story, and the skill returns clear remediation steps and who to notify.
Are tests required before marking a story done?
Yes. All checklist items must pass and test outputs are captured verbatim before closing the story.