
dev-loop
Development lifecycle outer loop: brainstorm → TDD planning → ralph → review → feedback loop
- version
- 1.0.0
- GitHub stars
- 6
Install
/plugin install dev-loop@workers-do-marketplaceRun it inside Claude Code after adding the marketplace with /plugin marketplace add dot-do/workers.
Contents
Discovered from sourceCommands 4
Advance Dev Loop Phase
Manually advance to the next phase of the development loop.
-
Read
.claude/dev-loop.local.mdto get current phase -
Validate prerequisites for advancement:
- BRAINSTORM → PLAN: Design document must exist
- PLAN → IMPLEMENT: Beads issues must be created
- IMPLEMENT → REVIEW: All issues should be closed
- REVIEW → APPROVED or FEEDBACK_PLAN: Based on findings
- FEEDBACK_PLAN → FIX: Fix issues must be created
- FIX → FINAL_REVIEW: All fixes closed
- FINAL_REVIEW → APPROVED or back to FEEDBACK_PLAN
-
Update the phase in the state file
-
Announce the new phase and what to do next
Phase-specific actions:
- Entering PLAN: Use extended thinking to create TDD beads issues
- Entering IMPLEMENT: Start Ralph loop with implementation prompt
- Entering REVIEW: Launch 5 parallel review agents
- Entering FEEDBACK_PLAN: Use extended thinking on review findings
- Entering FIX: Start Ralph loop with fix prompt
- Entering FINAL_REVIEW: Launch 5 parallel review agents
- Entering APPROVED: Celebrate! Clean up state file.
Cancel Dev Loop
Cancel the current development loop:
- Check if
.claude/dev-loop.local.mdexists - If not: "No active dev loop to cancel."
- If yes:
- Read the file to get current phase and iteration
- Remove the state file:
rm .claude/dev-loop.local.md - Report: "Dev loop cancelled (was in [PHASE] phase, iteration [N])"
Note: This does NOT delete:
- Design documents in docs/plans/
- Beads issues that were created
- Any code that was implemented
Those remain for you to use or clean up manually.
Dev Loop Status
Check the current state of the development loop:
- Check if
.claude/dev-loop.local.mdexists - If not: "No active dev loop. Start one with /dev-loop"
- If yes: Read the file and display:
═══════════════════════════════════════════════════════════
DEV LOOP STATUS
═══════════════════════════════════════════════════════════
Phase: [CURRENT_PHASE] ([N]/7)
Iteration: [N] of [MAX]
Started: [TIMESTAMP]
Task: [ORIGINAL_TASK]
Progress:
[✓] BRAINSTORM - Design: [design_doc or "pending"]
[✓] PLAN - Issues: [count] created
[ ] IMPLEMENT - Issues: [closed]/[total]
[ ] REVIEW - Findings: [count]
[ ] FEEDBACK_PLAN
[ ] FIX
[ ] FINAL_REVIEW
Next action: [what to do next based on phase]
═══════════════════════════════════════════════════════════
Dev Loop Command
Execute the setup script to initialize the development loop:
"${CLAUDE_PLUGIN_ROOT}/scripts/setup-dev-loop.sh" $ARGUMENTS
Now invoke the workers-do:brainstorming skill to begin the design exploration.
After brainstorming completes and the user approves the design:
- Write the design to
docs/plans/YYYY-MM-DD-<topic>-design.md - Update
.claude/dev-loop.local.mdphase to PLAN - Use extended thinking to create TDD beads issues
- Continue through the phases as described in workers-do:development-loop skill
PHASE TRANSITIONS:
- BRAINSTORM → PLAN: User says "design approved" or approves design
- PLAN → IMPLEMENT: Issues created, user approves plan
- IMPLEMENT → REVIEW: All issues closed, tests passing
- REVIEW → APPROVED: No critical findings
- REVIEW → FEEDBACK_PLAN: Critical findings need addressing
- FEEDBACK_PLAN → FIX: Fix issues created
- FIX → FINAL_REVIEW: All fixes complete
- FINAL_REVIEW → APPROVED: Quality verified
- FINAL_REVIEW → FEEDBACK_PLAN: More work needed
For IMPLEMENT and FIX phases, use Ralph loop with appropriate prompts. For REVIEW phases, launch 5 parallel review agents. For PLAN and FEEDBACK_PLAN phases, use extended thinking for issue creation.
Sponsors
Details
- Marketplace
- dot-do/workers
- Source
- plugins/dev-loop
- Author
- workers.do
- Category
- Community