---

name: feature-plan description: Start implementing a feature from the backlog with adaptive agent dispatch. Use when user wants to begin work on a backlog item, start implementation, or mentions a specific feature ID to work on. user-invocable: true

Implement Feature Command

You are executing the IMPLEMENT FEATURE workflow - a comprehensive feature kickoff process that ensures proper planning before any implementation begins.

First Step (Do This Now)

Read the file at path: docs/features/DASHBOARD.md

This file contains the backlog. If it doesn't exist, check if docs/features/ directory exists - if not, the project hasn't been set up for feature tracking yet.

Note: To start a feature, create docs/features/[id]/plan.md. The PostToolUse hook automatically updates DASHBOARD.md - do NOT edit DASHBOARD.md directly.

Contents

• Feature Target
• File Organization
• Workflow Overview
• Phase Details
• Completing a Feature
• Error Handling

---

Feature Target

$ARGUMENTS

If no specific feature ID was provided above, you will help the user select from the backlog.

---

File Organization

Features are stored in directories with status determined by file presence:

Copydocs/features/
├── DASHBOARD.md              # Auto-generated, read-only for Claude
├── my-feature/
│   ├── idea.md               # Problem statement + metadata (backlog)
│   ├── plan.md               # Implementation plan (in-progress)
│   └── shipped.md            # Completion notes (completed)
└── another-feature/
    └── idea.md

Status Detection by File Presence

Key Principles:

• /feature-capture creates idea.md only (backlog status)
• /feature-plan adds plan.md (changes to in-progress)
• /feature-ship adds shipped.md (changes to completed)
• DASHBOARD.md is auto-regenerated by hooks - never edit directly

---

Workflow Overview

This command orchestrates a 6-phase workflow:

---

Phase Details

Phase 1: Feature Selection

See: selection.md

• Read DASHBOARD.md and find/select feature from Backlog section
• Read the feature's idea.md for full details
• Verify feature is in backlog status (no plan.md exists yet)
• Handle already-in-progress features with user options

Phase 2: Requirements Deep Dive

See: requirements.md

• Read idea.md for problem statement and context
• Optional: Run code-archaeologist for legacy code
• Run project-manager agent for requirements analysis
• Effort-based scaling (Small/Medium/Large)

Phase 3: System Design (Adaptive)

See: design.md

• Classify feature type (Backend/Frontend/Full-Stack/Infrastructure)
• Dispatch appropriate specialized agents
• Save design documents to feature directory

Phases 4-6: Implementation & Kickoff

See: implementation.md

• Create plan.md with implementation steps
• Writing plan.md triggers hook to update DASHBOARD.md (move to In Progress)
• Set statusline by running: ${CLAUDE_PLUGIN_ROOT}/skills/feature-plan/scripts/set-context.sh <feature-id>
• Stage changes with git
• Display kickoff summary with next steps

---

plan.md Format

Write plan.md with YAML frontmatter followed by content:

Copy---
started: YYYY-MM-DD
---

# Implementation Plan: [Feature Name]

## Overview
Brief summary of what will be implemented...

## Implementation Steps
- [ ] Step 1: Description
- [ ] Step 2: Description
- [ ] Step 3: Description

## Technical Decisions
Key architectural choices made during design...

## Testing Strategy
How this feature will be tested...

## Risks & Mitigations
Any identified risks and how they'll be addressed...

---

Completing a Feature

When the feature is done, use the /feature-ship command:

Copy/feature-ship [feature-id]

This runs quality gates before marking the feature complete:

1. Security Review - Scans for vulnerabilities (OWASP Top 10, CVEs)
2. QA Validation - Verifies test coverage and acceptance criteria
3. Final Verification - Runs tests, type checks, and build
4. Status Update - Creates shipped.md (triggers hook to update DASHBOARD.md)

---

Error Handling

---

Philosophy: "Never Code Without a Plan"

By completing these 6 phases, you ensure:

• Requirements are clearly understood
• Architecture is properly designed
• Implementation is broken into manageable steps
• Documentation will stay current
• Testing is considered upfront
• Risks are identified and mitigated

---

Let's get started!