Development Workflow

Single source of truth for how development work flows. Three modes:

Mode A (Plan Writing): Embed a ## Workflow section into plans using templates/plan-workflow-section.md
Mode B (Implementation): Guide step-by-step execution through all 5 phases
Mode C (Orchestration): Coordinate multiple parallel agents across dependency rounds — see orchestration.md

Announce at start: "I'm using the development skill to [write the workflow section / guide this implementation]."

When This Skill Activates

Mode A: Writing or finalizing an implementation plan (before ExitPlanMode)
Mode B: User says "implement this", "build this", "execute this plan", "run the implementation plan end to end" — any branch → code → deliver flow. For focused bug diagnosis prefer /swe-workbench:debug (invokes the debugger subagent, which composes superpowers:systematic-debugging); escalate here when the fix needs the full 5-phase lifecycle.
- Prefer entering here rather than calling superpowers:executing-plans directly — Phase 2 already delegates to it while adding the surrounding Branch → Verify → Review → Deliver lifecycle.
Mode C: User says "orchestrate these issues", "run in parallel", multi-issue campaigns with >3 issues