afc

all-for-claudecode

Claude Code plugin that automates the full development cycle — spec → plan → implement → review → clean.

One command (/afc:auto) runs the entire cycle. Zero runtime dependencies — pure markdown commands + bash hook scripts.

Quick Start

# Option A: Inside Claude Code
/plugin marketplace add jhlee0409/all-for-claudecode
/plugin install afc@all-for-claudecode

# Option B: npx
npx all-for-claudecode

Then:

/afc:setup                             # Set up global routing in ~/.claude/CLAUDE.md
/afc:init                              # Detect your stack, generate project config
/afc:auto "Add user authentication"    # Run the full pipeline

The pipeline will:

1. Write a feature spec with acceptance criteria
2. Design an implementation plan with file change map
3. Implement tasks with CI gates (auto task decomposition + parallel execution)
4. Run code review with architecture/security agent analysis
5. Clean up artifacts and prepare for commit

How It Works

/afc:auto "Add feature X"

Spec (1/5) → Plan (2/5) → Implement (3/5) → Review (4/5) → Clean (5/5)
  │              │              │                │              │
  │              │              │                │              └─ Artifact cleanup
  │              │              │                └─ 8 perspectives + agent review
  │              │              └─ Auto task decomposition, parallel execution, CI gates
  │              └─ File change map, ADR recording, research persistence
  └─ Acceptance criteria, pre-implementation gates

Skill Advisor checkpoints (A–E) between phases dynamically invoke
auxiliary skills (ideate, consult, architect, security, test, qa, learner)
when LLM evaluation detects they would add value. Budget: max 5 per run.

Hooks run automatically at each step.
CI failure → debug-based RCA (not blind retry).
Critic Loops verify quality at each gate until convergence.

Walkthrough: What a Pipeline Run Looks Like

Running /afc:auto "Add password reset flow" produces this (abbreviated):

Spec (1/5) — Generates spec.md with requirements and acceptance criteria:

FR-001: POST /auth/reset sends email with token
FR-002: GET /auth/reset/:token validates and shows form
FR-003: Token expires after 1 hour
Acceptance: Given expired token, When user submits, Then show error

Plan (2/5) — Creates plan.md with file change map and architecture decisions:

File Change Map:
  src/routes/auth.ts        — ADD reset endpoint handlers
  src/services/email.ts     — ADD sendResetEmail()
  src/middleware/validate.ts — MODIFY add token validation
  tests/auth.test.ts        — ADD reset flow tests

Implement (3/5) — Auto-decomposes into tasks, executes with CI gates:

Tasks: 4 total (2 parallel)
  [1] Add reset endpoint     ✓
  [2] Add email service       ✓  ← parallel with [1]
  [3] Add token validation    ✓  ← depends on [1]
  [4] Add tests               ✓
CI: npm test → passed

Review (4/5) — 8-perspective review + specialist agent analysis:

Architecture (afc-architect): ✓ layer boundaries respected
Security (afc-security): ⚠ rate-limit reset endpoint
Performance: ✓ no N+1 queries
→ Auto-fixed: added rate limiter middleware

Clean (5/5) — Removes pipeline artifacts, final CI check.

Slash Commands