If you're using BMAD (Breakthrough Method for Agentic AI Development), you know the pain: every story requires running through create → develop → test → review → fix → update status. For an Epic with 8 stories, that's potentially 40+ manual commands.
I wrapped this entire workflow into Claude Code Skills. Now one command delivers a complete Epic:
/bmad-epic-worktree
For a single story:
/bmad-story-deliver
It handles:
- Development implementation
- QA automated testing
- Code review
- Auto-fix HIGH/MEDIUM issues
- Update status to Done
Three modes available:
1. Fast mode - Quick iteration, tests run but failures don't block
2. Safe mode - Git worktree isolation, won't merge if tests fail
3. Batch mode - Deliver entire Epic with one command (my favorite)
For company projects, I recommend splitting the flow: manually review the story design first (since that determines what to build), then let automation handle the rest.
The core idea: automate the repetitive stuff, but keep human oversight where it matters.
suchuanyi|13 days ago
I wrapped this entire workflow into Claude Code Skills. Now one command delivers a complete Epic:
/bmad-epic-worktree
For a single story: /bmad-story-deliver
It handles: - Development implementation - QA automated testing - Code review - Auto-fix HIGH/MEDIUM issues - Update status to Done
Three modes available: 1. Fast mode - Quick iteration, tests run but failures don't block 2. Safe mode - Git worktree isolation, won't merge if tests fail 3. Batch mode - Deliver entire Epic with one command (my favorite)
For company projects, I recommend splitting the flow: manually review the story design first (since that determines what to build), then let automation handle the rest.
The core idea: automate the repetitive stuff, but keep human oversight where it matters.