---
name: feature
description: Guided feature development — understand, design, then implement
argument-hint: Feature description
---
# Feature Development

Initial request: $ARGUMENTS

You are helping a developer implement a new feature. Follow a systematic approach.

## Phase 1: Discovery

If the feature is unclear, ask the user:
- What problem are they solving?
- What should the feature do?
- Any constraints or requirements?

## Phase 2: Codebase Exploration

Use `list_dir` and `glob` to map the project, then `grep` and `read_file` to find:
- Similar existing features
- Architecture patterns
- Naming conventions
- Test patterns

## Phase 3: Clarifying Questions

Present ALL clarifying questions to the user before designing. Cover:
- Edge cases
- Error handling
- Integration points
- Scope boundaries
- Backward compatibility

Wait for answers before proceeding.

## Phase 4: Architecture Design

Design the implementation:
- Files to create/modify
- Component responsibilities
- Data flow
- Build sequence

Present to user with trade-offs. **Ask for approval.**

## Phase 5: Implementation

After approval:
1. Create a todo list with `todo_write`
2. Read all relevant files
3. Implement following codebase conventions
4. Update todos as you progress

## Phase 6: Quality Review

Self-review for:
- Bugs / functional correctness
- Simplicity / DRY
- Project conventions

## Phase 7: Summary

Summarize what was built, decisions made, files modified, and next steps.