Agent Skill
2/7/2026

phase-review

Review implementation plans for a particular phase in a larger plan for flaws before committing to them. Use when reviewing phase plans from .tasks/ directory. Triggers on: 'use phase mode', 'review phase', 'review the plan', 'check phase', 'validate phase', 'review phase N', 'check the plan for phase'.

M
mcouthon
21GitHub Stars
2Views
npx skills add mcouthon/agents

SKILL.md

Namephase-review
DescriptionReview implementation plans for a particular phase in a larger plan for flaws before committing to them. Use when reviewing phase plans from .tasks/ directory. Triggers on: 'use phase mode', 'review phase', 'review the plan', 'check phase', 'validate phase', 'review phase N', 'check the plan for phase'.

AGENTS

AI-Guided Engineering — Navigate → Think → Ship

License: MIT PRs Welcome GitHub Discussions

A minimal framework for AI-assisted coding with phase-based workflows, auto-activating skills, and enforced tool safety. Works with VS Code Copilot and Claude Code.


What You Get

ComponentCountWhat It Does
Agents7Phase-based workflow with orchestration (4 core + Orchestrate + 2 internal)
Skills12Auto-activate based on your prompts (debug, mentor, testing, etc.)
Instructions4File-type coding standards that load automatically
git clone https://github.com/mcouthon/agents.git
cd agents
./install.sh    # Works out of the box — generated files are committed to git

Modifying templates? Run make first to regenerate output files, then ./install.sh.

That's it. In VS Code, use the Chat menu to select agents. In Claude Code, use claude --agent AgentName or use AgentName. Or just talk naturally and let skills auto-activate.


The Core Insight

"The highest leverage point is at the end of research and the beginning of the plan. A human can skim 30 seconds and provide feedback that saves hours of incorrect implementation."

This framework is built around that insight. The Explore agent is read-only—it can't accidentally edit your code. You review its research and plan, then hand off to Implement when you're ready.


The Workflow

Manual workflow (use agents directly):

Explore ──→ Implement ──→ Review ──→ Commit
               │            │
               │            └──→ Fix Issues ──→ (back to Implement)
               │
               └──→ Commit (skip review for small changes)

Orchestrated workflow (VS Code: @Orchestrate | CC: use Orchestrate or claude --agent Orchestrate):

┌─────────────────────────────────────────────────────────────┐
│            ORCHESTRATE (conductor agent)                    │
│  Task → For each phase: Plan → Review → Implement → Commit  │
└───────────┬───────────────────────────────────────────┬─────┘
            ↓                                           ↓
        Explore ──→ Implement ──→ Review ──→ Commit

Orchestrate automates multi-phase workflows with pause points for user approval.

AgentPurposeTool AccessKey Handoffs
OrchestrateAutomate multi-phase workflowRead + Agent(coordinates other agents)
ExploreResearch + create plansRead + Task WriteImplement
ImplementExecute planned changesFull accessReview, Commit
ReviewVerify implementation qualityRead + TestCommit Changes, Fix Issues
CommitCreate semantic commitsGit + ReadPush

Internal agents (not user-invokable): Research (read + web), Worker (full access) — used by other agents for context-isolated subtasks.

Task Write: Explore can only write to .tasks/ directory—not your codebase.

Automatic state persistence: Explore saves research to .tasks/[NNN]-[task-name]/ so you can resume across sessions. Tasks are numbered sequentially (001, 002, etc.) for chronological ordering.

In-context actions (VS Code): Each agent has handoff buttons for common next steps that keep your chat history and context intact. To switch agents, just @ mention them (e.g., @Implement when ready to start coding). In Claude Code, type use Implement or start a new session with claude --agent Implement.

Handoff Buttons (VS Code In-Context Actions)

Each agent has buttons that trigger common next steps without leaving your current chat context:

AgentButtonPurpose
OrchestrateContinueProceed to next workflow step
Skip PhaseSkip current phase, move to next
Implement NowJump directly to implementation
ExploreImplementHand off to Implement agent
Plan Next PhaseDetailed plan for next unplanned phase
Re-exploreInvestigate further
Show PlanDisplay phase status from task.md
SavePersist research to .tasks/
ImplementReviewHand off to Review agent
CommitHand off to Commit agent
Check for ErrorsRun linting and type checks
Run TestsExecute the test suite
ReviewCommit ChangesHand off to Commit agent
Fix IssuesHand off to Implement to address problems
Re-reviewCheck again after fixes are applied
Check TestsRun tests and verify they pass
CommitReview CommitsShow commits with git log
Amend Last CommitAmend the last commit with staged changes
PushPush commits to remote

Key benefit: These buttons keep your context and chat history. No reset, no re-explaining.


Skills (Auto-Activate)

Skills activate automatically based on what you say:

You SaySkill Activated
"This test is failing"debug
"Find code smells"tech-debt
"Clean up dead code"tech-debt
"Document the architecture"architecture
"Teach me how this works"mentor
"Challenge my approach"critic
"Create a Makefile"makefile
"Build a dashboard UI"design
"Security review this PR"security-review
"Write tests for this"testing

No manual switching required—just ask naturally.


What AGENTS Is / Isn't

AGENTS IsAGENTS Isn't
Advisory guidanceMandatory enforcement
Phase-based workflowMagic one-shot agent
Minimal and composableBatteries-included framework
IDE-agnostic patternsCursor/Claude-specific
Human-in-the-loop at key pointsFully autonomous

Installation Details

Generated files are committed to git, so ./install.sh works immediately after clone.

For contributors modifying templates:

make            # Regenerate generated/ from templates/
./install.sh    # Symlink generated files to home directories

After ./install.sh:

ComponentInstalled To
Agents (VS Code)~/.copilot/agents/
Instructions (VS Code)~/.copilot/instructions/
Instructions (IntelliJ)~/.config/github-copilot/intellij/
Skills~/.copilot/skills/ (with ~/.claude/skills symlink)
Agents (Claude Code)~/.claude/agents/
Task state gitignoreAdded to global gitignore (.tasks/)

IntelliJ users: Only global instructions are installed. Agents and skills require VS Code's agent discovery mechanism and tool restrictions, which IntelliJ doesn't support.

The installer also configures VS Code settings (chat.agentFilesLocations, chat.instructionsFilesLocations) to discover agents and instructions from these locations.


Claude Code Usage

Agents are available as native subagents in Claude Code:

AgentPurpose
ExploreResearch and plan
ImplementExecute the plan
ReviewVerify changes
CommitCreate semantic commits

Example workflow:

$ claude
> use Explore to add user authentication

[Claude researches, produces plan]

> use Implement

[Claude implements based on conversation context]

> use Review

[Claude reviews changes]

> use Commit

[Claude creates commits]

Note: Claude Code supports tool restrictions, model selection, and skills. The only VS Code feature not available in Claude Code is handoff buttons — use the next agent manually when ready.

Shell helpers (optional): Run ./install.sh helpers to add a-explore, a-implement, a-review, a-commit, and a-orchestrate commands to your PATH. Each supports a-explore, a-explore continue (auto-detect task), and a-explore "prompt" modes. See cc-quickstart.md for details.


Customization

Adding an Agent

Create templates/agents/my-agent.template.md (see templates/README.md for format), then:

make            # Regenerate generated/ from templates/
./install.sh    # Install locally

Adding a Skill

Create templates/skills/my-skill/SKILL.template.md (see templates/README.md for format), then:

make && ./install.sh

Validating Skills (TDD for Documentation)

  1. RED - Run task WITHOUT the skill, note failures
  2. GREEN - Add skill, verify improvement
  3. REFACTOR - If agent rationalizes around it, strengthen guidance

If you didn't see it fail without the skill, you don't know if the skill helps.

Run make && ./install.sh after adding agents or skills.


Task Continuity

Explore persists state to .tasks/[NNN]-[task-name]/:

.tasks/001-add-auth/
  task.md                      # Research + phases + main plan
  plan/
    phase-1-config.md          # Detailed plan for phase 1 (optional)
    phase-2-user-model.md      # Detailed plan for phase 2 (optional)

Phase-Based Workflow

  1. Initial researchtask.md with research findings + phase table
  2. Plan Next Phase (optional) → detailed plan for complex phases → plan/phase-N-[name].md
  3. Implement → picks smallest planned unit (phase plan if exists, else task.md)
  4. Mark phase ✅ Done, repeat
AgentReadsUpdates
Exploretask.md, plan/*.mdtask.md, plan/*.md, phase status
ImplementPhase plan or task.mdPhase status (⬜→📋→🔄→✅)
ReviewAll plan + implement

To continue a task: Just say "Continue working on [task-name]"


Agents vs Skills

Use CaseUse
Need enforced tool restrictionsAgent
Need handoffs between phasesAgent
Want auto-activation from promptsSkill
Role-based workflow phasesAgent
Specialized methodologiesSkill

File Structure

templates/                # SOURCE OF TRUTH — edit these
├── agents/               #   7 agent templates
├── skills/               #   12 skill templates
└── instructions/         #   4 instruction templates

generated/                # GENERATED — do not edit
├── copilot/              #   Copilot output
│   ├── agents/           #     Agent files
│   ├── skills/           #     Skill files
│   └── instructions/     #     Instruction files
└── claude/               #   Claude Code output
    ├── agents/           #     CC subagent files
    ├── skills/           #     CC skill files
    └── rules/            #     CC rule files

scripts/
├── generate.js           # Bidirectional template generator
└── configure-vscode-settings.js

Makefile                  # Build targets: make [copilot|cc|all|validate]
install.sh                # Symlinks generated files to ~/.copilot/ and ~/.claude/

docs/
├── synthesis/        # Core principles and framework analysis
└── research/         # Research Decision Records (RDRs)

Troubleshooting

Skills not auto-activating?

  1. Run make && ./install.sh to ensure generated files and symlinks exist
  2. Check ~/.copilot/skills/ for your skills
  3. Be more explicit: "Use debug mode to investigate..."

Generated files out of date?

make validate   # Check if generated files match templates
make            # Regenerate if needed

Need to uninstall?

./install.sh uninstall

Contributing

We welcome contributions! See CONTRIBUTING.md for guidelines.

Quick ways to contribute:


Further Reading

TopicDocument
Core principlesprevailing-wisdom.md
Framework analysisframework-comparison.md
Memory & session continuitymemory-and-continuity.md
Claude Code quickstartcc-quickstart.md
Research decisionsdocs/research/
12-Factor Agentsdocs/sources/12-factor-agents/

Why This Exists

Synthesized from multiple frameworks into something minimal and useful:

Model recommendation: Claude Opus 4.5 for heavy lifting. When Sonnet struggles, Opus delivers.

Skills Info
Original Name:phase-reviewAuthor:mcouthon