Feature Dev — 7-Phase Structured Feature Development

🎯 7-Phase Workflow🔎 Parallel Exploration🏗️ Architecture Design✅ Quality Review

Architecture

flowchart TB
    subgraph Phase1_2["Phase 1-2: Discovery"]
        P1["Phase 1: Understand Request"] --> P2["Phase 2: Explore Codebase"]
        P2 --> EX1["code-explorer ×3"]
    end
    subgraph Phase3_4["Phase 3-4: Design"]
        EX1 --> P3["Phase 3: Architecture Design"]
        P3 --> ARCH["code-architect"]
        ARCH --> P4["Phase 4: Implementation Plan"]
    end
    subgraph Phase5["Phase 5: Build"]
        P4 --> P5["Phase 5: Implementation"]
        P5 --> CODE["Write Code"]
    end
    subgraph Phase6_7["Phase 6-7: Review"]
        CODE --> P6["Phase 6: Quality Review"]
        P6 --> REV["code-reviewer"]
        REV --> P7["Phase 7: Polish & Commit"]
    end

Key Components

Agent Configuration Details

Workflow Example

Basic Usage

The /feature-dev command accepts a natural-language feature description and guides the entire development process through 7 structured phases.

# Start a feature development workflow
/feature-dev "Add JWT authentication to the API layer"

# With more specific description
/feature-dev "Implement rate limiting middleware with Redis backend, \
  supporting per-user and per-endpoint limits"

# The command will automatically:
# 1. Parse your request into requirements
# 2. Launch 3 parallel code-explorers
# 3. Design architecture via code-architect
# 4. Create implementation plan
# 5. Write the code
# 6. Review with code-reviewer (Opus)
# 7. Polish and prepare commit

Phase Output Artifacts

Explorer Assignment Strategies

Data Flow

sequenceDiagram
    participant Dev as Developer
    participant Cmd as /feature-dev
    participant EX as code-explorer (x3)
    participant AR as code-architect
    participant RV as code-reviewer
    participant Git as Git

    Dev->>Cmd: /feature-dev "Add user auth"
    Note over Cmd: Phase 1: Parse request
    Cmd->>Cmd: Read CLAUDE.md guidelines
    Note over Cmd: Phase 2: Explore codebase
    par Parallel Exploration
        Cmd->>EX: Explore auth patterns
        Cmd->>EX: Explore API routes
        Cmd->>EX: Explore test patterns
    end
    EX-->>Cmd: Exploration reports
    Note over Cmd: Phase 3: Design
    Cmd->>AR: Design architecture
    AR-->>Cmd: Architecture blueprint
    Note over Cmd: Phase 4: Plan
    Cmd->>Cmd: Break into implementation steps
    Note over Cmd: Phase 5: Implement
    Cmd->>Cmd: Write code (Edit, Write tools)
    Note over Cmd: Phase 6: Review
    Cmd->>RV: Review implementation
    RV-->>Cmd: Quality report + suggestions
    Note over Cmd: Phase 7: Polish
    Cmd->>Git: git diff (verify changes)
    Cmd-->>Dev: Summary + commit message

Design Patterns Enforced

The feature-dev workflow encourages several design patterns through its phased approach:

Error Recovery

If any phase fails or produces insufficient results:

• Explorer failure: Re-run with adjusted search patterns and expanded scope
• Architect rejection: Return to Phase 2 with additional exploration questions
• Reviewer findings: Loop back to Phase 5 to address issues, then re-review
• Build failures: Diagnose with Bash tool, fix, and re-verify before Phase 7

Interactions

Phase Reference

Detailed Phase Breakdown

Each phase has specific entry criteria, activities, and exit deliverables that gate progression to the next phase.

Configuration Reference

Agent Model Selection

Model selection follows a cost-quality optimization: Sonnet handles high-volume exploration and design tasks efficiently, while Opus is reserved for the single code-reviewer pass where reasoning depth has the highest impact on finding subtle bugs.

Directory Map

feature-dev/
├── .claude-plugin/plugin.json          ← Plugin manifest
├── README.md                           ← Usage guide and examples
├── commands/
│   └── feature-dev.md                  ← 7-phase orchestration command
└── agents/
    ├── code-explorer.md                ← Codebase analysis (Sonnet, parallel)
    ├── code-architect.md               ← Architecture design (Sonnet)
    └── code-reviewer.md                ← Quality review (Opus)