mhrezaee/dev-crew

### A complete AI software engineering team for Claude Code
16 specialist subagents · 28 engineering skills · 18 workflow commands · guardrail hooks
The whole SDLC, from a vague ticket to a tagged release. Evidence-based, guarded and lean on tokens.
## Why?
Claude Code is great at writing code. Software engineering is more than writing code: refining requirements, designing, planning, testing, reviewing, securing, shipping, releasing and handling incidents.
Dev Crew gives Claude a team of senior specialists and the checklists real engineering teams use every day, so you get:
✅ Requirements that are testable before anyone writes code
✅ Designs with trade-offs and ADRs instead of "just start coding"
✅ Small, ordered plans that keep the build green
✅ Tests and reviews by default, not as an afterthought
✅ Security, performance and operability built in
✅ Language-agnostic: .NET, Java/Kotlin, TypeScript, Python, Go, Rust, Flutter, Swift and more. Every agent follows your codebase's conventions first
✅ Trustable: answers cite file:line, nothing is called "passing" until it ran, and guardrail hooks stop destructive commands and leaked secrets
✅ Lean: about 2.7k tokens of always-on context; the 18 workflows cost nothing until you type them
## ⚡ Quick start
### Option 1: Claude Code plugin (recommended)
bash
# inside Claude Code
/plugin marketplace add mhrezaee/dev-crew
/plugin install dev-crew@dev-crew
### Option 2: install script (copies into ~/.claude)
bash
git clone https://github.com/mhrezaee/dev-crew.git
cd dev-crew
./install.sh # macOS / Linux / Git Bash
# or
./install.ps1 # Windows PowerShell
Use --project / -Project to install into the current repository's .claude/ folder instead, so the whole team gets it via git.
> The guardrail hooks are only active with the plugin install (Option 1). The scripts copy agents and skills only.
### Try it
/onboard # understand the repo you're in
/architect # choose the right architecture, write blueprint + ADRs
/feature Users can export their bookings as CSV
/fix-bug NullReferenceException in InvoiceService.Calculate when discount is null
/review-code main
/ship PAY-142
/standup
## 🔄 The SDLC, covered
mermaid
flowchart LR
Z[/architect/] --> A
A[/refine/] --> B[/design/] --> C[/plan/] --> D[implement] --> E[/test/] --> F[/review-code/] --> G[/ship/] --> H[/release/]
H -. incident .-> I[/postmortem/]
I -. learnings .-> A
## 🏛️ An architect that decides, not just suggests
Run /architect and the solution-architect works like a senior architect would. It never picks microservices or DDD because they're trendy.
1. Collects evidence from your code (or your product vision) and asks at most 5 questions.
2. Scores 11 drivers: domain complexity, team scale, deployability, scale heterogeneity, ops maturity, consistency, integration intensity, read/write asymmetry, audit needs, uncertainty, workload shape.
3. Decides at every level, with the rejected alternatives written down:
| Level | Options it chooses between |
| System | Modular monolith (default) · layered monolith · microservices · serverless · event-driven |
| Domain | DDD strategic design: subdomains, bounded contexts, context map |
| Code | Layered · vertical slice · clean / hexagonal / onion · DDD tactical (core domain only) · CQRS · event sourcing |