Orchestrates complex or architectural code changes through a structured workflow. Use when the user requests multi-file changes, new features, architectural refactoring, database schema changes, new API endpoints, or any task requiring significant planning. Triggers context gathering, planning, code review, TDD execution, and manual testing.
This skill orchestrates large or architectural code changes through a structured, quality-focused workflow.
Activate this workflow when the user's request involves:
Do NOT use for:
Before planning, thoroughly understand the landscape.
Use the Explore agent to investigate:
Identify and note:
If the request is ambiguous, ask clarifying questions NOW before planning.
Create a detailed, reviewable plan.
Create a plan file at docs/claude-plans/{descriptive-task-name}.md
The plan MUST include:
# Plan: {Task Name}
## Objective
{One sentence describing what we're building and why}
## Context Summary
{Key findings from Phase 1 - patterns found, conventions to follow}
## Implementation Steps
### Step 1: {Description}
- **Files**: {files to create/modify}
- **Test**: {what test will verify this step}
- **Acceptance**: {how we know this step is done}
### Step 2: {Description}
...
## Risks & Mitigations
- {Risk}: {How we'll handle it}
## Out of Scope
- {Things we're explicitly NOT doing}
Get architectural feedback before executing.
Invoke the code reviewer with the Fowler personality:
/code-reviewer fowler docs/claude-plans/{task-name}.md
The reviewer will assess:
Document the review feedback in the plan file under a new section:
## Review Feedback
- {Feedback point 1}
- {Feedback point 2}
## Plan Adjustments
- {How we're addressing the feedback}
If feedback raises questions without clear answers, ask the user for guidance.
Present the final plan to the user for approval before proceeding.
Implement using strict TDD discipline.
Use the TodoWrite tool to track each step:
[ ] Step 1: Create migration for X
[→] Step 2: Add model with validations
[✓] Step 3: Write service object
If any frontend code was touched, verify visually.
Provide a clear summary of what was accomplished.
## Task Complete: {Task Name}
### Files Changed
- `path/to/file.rb` - {what changed}
- `path/to/file_spec.rb` - {tests added}
### Key Decisions Made
- {Decision 1}: {Rationale}
- {Decision 2}: {Rationale}
### Limitations & Known Issues
- {Any limitations discovered}
- {Edge cases not handled}
### Suggested Follow-ups
- {Future improvements}
- {Related refactoring opportunities}
| Phase | User Approval Required? |
|---|---|
| Context Gathering | No (unless clarification needed) |
| Planning | No |
| Plan Review | YES - must get approval before execution |
| Execution | No (unless plan needs changing) |
| Manual Testing | No |
| Summary | No |
User: "Add a feature to let guests upload dietary requirements"
Claude activates this workflow:
docs/claude-plans/guest-dietary-upload.md/code-reviewer fowler on the plan