dev-cycle
Development Cycle — Router
Pick one primary workflow per task from the table below, load that skill before starting the work (the Skill tool in Claude Code; read its SKILL.md elsewhere), and follow it — this router is not a workflow by itself. Choose from the table; do not open other workflow skills to compare them. Load supporting skills only when needed; dev-code-style supplies the shared code and comment guidance for implementation and review.
Routing
| Situation | Skill |
|---|---|
| Straightforward localized change with an obvious implementation | dev-feature-lite |
| Coordinated scoped change where sequencing or contract alignment across behavioral surfaces needs a short in-chat plan | dev-feature |
| Open problem, several viable approaches: "how should we…" | dev-problem-solving |
| "Review this / ready to merge?" | dev-review |
| Bug resisting the first fix; "still broken", debugger setup | dev-debug |
| Writing tests / "how to test this" | dev-testing |
| E2E suite against a real stack; network-failure / resilience testing; SDK smoke tests | dev-e2e-testing |
Lesson worth keeping; "remember this"; task start in a repo with docs/knowledge/ |
dev-knowledge |
| Writing or reviewing code; simplifying abstractions or comments | dev-code-style (supporting skill) |
Ambiguous between lite and coordinated feature work? Start with dev-feature-lite; escalate when code inspection finds sequencing or contract alignment across behavioral surfaces, a real design fork, a cross-cutting migration, or material risk. Ambiguous between a coordinated feature and problem-solving? Start with dev-feature; it escalates itself when it finds multiple viable architectures.