Coding Agent Toolkit
This repository is archived. The workflow system has evolved into a new project:
AndThen is the successor to cc-workflows — a focused, opinionated workflow system for agentic development with a clean new structure and identity. Please use that repo going forward.
Development workflows, rules, guidelines, and safety hooks for Claude Code.
The centerpiece is the cc-workflows plugin — structured workflows that take you from requirements through implementation to review. Everything else (rules, guidelines, hooks) supports and enhances those workflows.
Getting Started
1. Install the plugin (see cc-workflows README for detailed instructions)
# Add as marketplace
/plugin marketplace add tolo/coding-agent-toolkit
# Install plugin
/plugin install cc-workflows@coding-agent-toolkit
This gives you slash commands like /spec, /exec-spec, /review-code, /quick-implement, and more. See cc-workflows commands below.
2. Set up your project's CLAUDE.md
The plugin's commands reference a "Workflow Rules, Guardrails and Guidelines" section in your project's CLAUDE.md. Use the included template to set this up:
# Copy the template (or merge sections into your existing CLAUDE.md)
cp CLAUDE.template.md /path/to/your-project/CLAUDE.md
Then copy the rules and guidelines it references:
# Copy everything
cp -r docs/ /path/to/your-project/docs/
# Or pick only what you need
cp -r docs/rules/ /path/to/your-project/docs/rules/
cp -r docs/guidelines/ /path/to/your-project/docs/guidelines/
Fill in the [TODO] placeholders in your CLAUDE.md and KEY_DEVELOPMENT_COMMANDS.md, remove sections you don't need.
All docs/ paths in the template are relative to your project root, so the directory structure should match after copying.
3. Optionally add hooks
See Hooks for safety and workflow automation scripts.
cc-workflows Plugin
Structured development workflows — from requirements to implementation with built-in quality gates.
┌──────────────────────────────────────────────────────┐
│ FEATURE WORKFLOW (see cc-workflows README for more) │
│ │
│ (optional) (optional) │
│ clarify ────────────→ spec ─────────→ review-doc │
│ │ │
│ ▼ │
│ exec-spec │
│ │ │
│ ▼ │
│ review-gap │
└──────────────────────────────────────────────────────┘
┌──────────────────────────────────────────────────────┐
│ QUICK PATH (small features/fixes) │
│ │
│ quick-implement ──→ review-code (optional) ──→ done │
└──────────────────────────────────────────────────────┘
For the full plan workflow (MVP / multi-feature), see the cc-workflows README.
Commands / Skills
Invoke with /cc-workflows:<command> or just /<command> if unambiguous.
| Command | Purpose |
|---|
clarify | Transform vague ideas into clear, actionable requirements |
prd | Create comprehensive PRD from refined requirements |
spec | Create implementation spec from feature requirements |
plan | Create implementation plan with story breakdown from PRD |
exec-spec | Execute spec with validation loops until complete |
exec-plan | Execute entire plan through Agent Team pipeline |
exec-plan-codex | Execute plan via Agent Teams + Codex CLI delegation |
quick-implement | Fast path for small features/fixes (supports --issue for GitHub) |
review-code | Comprehensive code review (quality, security, architecture, UI/UX) |
review-gap | Gap analysis: implementation vs requirements |
review-council | Multi-perspective review with Agent Teams (5-7 reviewers + debate) |
trade-off-analysis | Evaluate technical alternatives with structured comparison |
wireframes | Generate HTML wireframes for UI planning |
design-system | Create design tokens and component styles |
troubleshoot | Diagnose and fix implementation issues systematically |
Quick examples
# Implement a feature from scratch
/spec "user data export as CSV and JSON"
/exec-spec
/review-gap
# Quick fix from GitHub issue
/quick-implement --issue 123
# Architectural decision
/trade-off-analysis "caching strategy for API responses"
Full usage examples, agents, skills, and key concepts are documented in the cc-workflows README.
Plugin installation options