agile-team

Agile Team for Claude Code

An AI agentic team designed for your agile workflow. For anyone building a product independently — with the discipline of a real team behind every decision.

Quick Start • Agents • Commands • Contributing

---

The problem it solves

When you're building a product alone, you skip the things that matter most — not because you don't care, but because there's nobody to hold you to them.

You ship without a proper review. You make a product decision, forget the reasoning, then reverse it two weeks later. You write a story with no acceptance criteria and call it done anyway. Security holes slip through. Tech debt piles up quietly. You know what good process looks like — you just have no one to run it with.

It doesn't matter if you're a developer, a founder, or someone building with AI for the first time. The gap is the same: the work is solo, but the discipline that makes teams ship well — review loops, clear ownership, sprint memory — isn't.

This gives you that team. An AI agentic team designed around your agile workflow, not a single assistant trying to do everything at once.

---

What it actually does

Seven agents. Each one has a single job and won't budge from it. When you run /review, QA checks first — if your code doesn't meet the acceptance criteria, the review stops there. No code review of broken code. If it passes, four agents process your diff in sequence, then the PO collects all findings and gives you one verdict:

You run:  /review

  qa           → tests pass? AC met? edge cases covered?
                 ↓ FAIL → stop here. back to dev. no exceptions.
                 ↓ PASS → proceed

  pr-reviewer  → correctness, style, edge cases, dead code
  security     → secrets, OWASP, CVEs, input validation, auth
  tech-lead    → architecture alignment, tech debt, patterns

  po           → collects all findings:
                   FIX NOW    → blocks merge
                   BACKLOG    → added to BACKLOG.md automatically
                   WON'T FIX  → documented with reasoning

You get:  APPROVED → run /complete to commit
          CHANGES REQUESTED → fix → /review again
          + every non-blocking issue in your backlog, not forgotten

That's the pattern for every command. Multiple specialists. One synthesizer. One artifact.

---

Before and after

Before	After
Commit and hope nothing breaks	4 specialist agents review every diff
Security issues show up in production	Security reviewed on every commit — OWASP, secrets, CVEs
Lose context switching sessions	NEXT.md tells you exactly what to do, every session
Backlog is a pile of random notes	Stories written, groomed, and prioritized by a product owner
Tech debt accumulates silently	Tech debt gets a story the moment it's introduced
Ship without acceptance criteria	QA hard veto — nothing ships without passing tests
Retros never happen	Every sprint closes with a retro that produces real backlog items

---

The 7 Agents

po-agent

pm-agent

dev-agent

qa-agent

pr-reviewer

security

tech-lead