claude-swe-workflows
A system of composable software engineering workflows for [Claude Code][cc].
Plan projects, implement tickets, and run quality passes — from a single
ticket to a multi-batch project, using the same layered architecture.
Installation
claude plugin marketplace add https://github.com/chrisallenlane/claude-swe-workflows.git
claude plugin install claude-swe-workflows@claude-swe-workflows
How It Works
These workflows form a layered system where higher-level workflows
orchestrate lower-level ones. Each layer adds coordination, quality gates,
and autonomy.
/implement-project ← full project lifecycle
├── /implement-batch (per batch) ← multi-ticket orchestration
│ ├── /implement (per ticket) ← single-ticket implementation
│ │ ├── SME implementation ← language-specific specialist
│ │ ├── QA verification ← practical + coverage
│ │ ├── Code review ← security, refactor, perf
│ │ └── Documentation ← targeted doc updates
│ ├── /refactor ← per-batch cleanup
│ └── /review-doc ← per-batch doc audit
├── /refactor (MAXIMUM aggression) ← project-level cleanup
├── /review-arch ← architectural restructuring
├── /refactor (conditional) ← post-restructuring cleanup
├── /review-test ← test suite review
├── /review-doc ← documentation audit
└── /review-release ← pre-release readiness
Planning feeds implementation. /scope-project plans a multi-batch
project with adversarial review, producing tagged tickets that /implement-project
consumes directly:
/scope-project → /implement-project
plan implement + verify + polish
For single tickets: /scope plans, /implement implements.
Two supporting workflows are available at any level: /deliberate
(adversarial decision-making for hard choices) and /bug-fix
(diagnosis-first bug fixing).
Choosing a Workflow
Not everything needs the full pipeline. Enter at the level that matches
your task:
| You want to... | Use |
|---|
| Implement an entire multi-batch project autonomously | /implement-project |
| Implement a batch of related tickets | /implement-batch |
| Implement a single ticket or feature | /implement |
| Plan a multi-batch project with adversarial review | /scope-project |
| Plan a single feature and create a ticket | /scope |
| Fix a bug with diagnosis and root-cause analysis | /bug-fix |
| Proactively hunt for bugs before they're reported | /bug-hunt |
| Make a hard decision with adversarial deliberation | /deliberate |
| Clean up code quality (DRY, dead code, naming) | /refactor |
| Rethink module boundaries and architecture | /review-arch |
| Review and strengthen the test suite | /review-test |
| Verify test quality via mutation testing | /test-mutation |
| Audit all project documentation | /review-doc |
| Pre-release readiness check | /review-release |
| Audit web content for accessibility barriers | /review-a11y |
| Assess code health across all project languages | /review-health |
| Review performance (compute and/or web) | /review-perf |
| Perform a white-box security audit | /audit-security |
Rules of thumb:
- Multiple batches of tickets forming a project?
/implement-project
- One batch of 2+ related tickets?
/implement-batch
- One ticket?
/implement (or /bug-fix if it's a bug)
- Not sure what to build yet? Start with
/scope or /scope-project
Skills
Orchestration
These workflows manage the lifecycle of tickets — from implementation
through quality passes to a merge-ready branch.
/implement-project — Full-Lifecycle Project Workflow
Orchestrates an entire project from tickets to release-ready code. Takes
batched tickets, implements each batch via /implement-batch in autonomous mode,
runs smoke tests, then executes a comprehensive quality pipeline (refactor,
review-arch, review-test, review-doc, review-release). The result is a
single project branch ready for human review and merge.
Maximizes autonomy — the andon cord (stop-the-line escalation) is the only
planned intervention path.
Detailed documentation
/implement-batch — Multi-Ticket Orchestration
chrisallenlane