Feature Dev

---
name: feature-dev
description: |
  Trigger when the user asks to build a feature, implement a story, or do
  end-to-end development work. Phrases: "build", "implement", "add feature",
  "new feature", "develop", "create functionality".
allowed-tools:
  - Bash(command *)
  - Read
  - Write
  - Edit
  - Glob
  - Grep
---

# Feature Dev

End-to-end feature development using a structured 7-phase approach with
parallel exploration and review agents.

## Prerequisites

- Git repository initialized
- Project dependencies installed

## Steps

1. **Understand** - Read the request carefully. Use Grep and Glob to explore
   the codebase and understand existing patterns, conventions, and architecture.

2. **Plan** - Write a brief plan as a checklist:
   - Which files need to change?
   - What new files are needed?
   - What tests should be added?
   - Are there migration or config changes?

3. **Explore dependencies** - Before writing code, read every file that will be
   imported by or will import your new code. Understand interfaces, types,
   and data flow.

4. **Implement** - Write the code following existing project conventions:
   - Match the style of surrounding code (naming, formatting, patterns)
   - Add types for all public interfaces
   - Handle errors explicitly
   - Keep functions small and focused

5. **Test** - Write tests alongside the implementation:
   - Unit tests for pure logic
   - Integration tests for API/database interactions
   - Run the test suite: `npm test` or equivalent

6. **Verify** - Run linters, type checkers, and build:
   - `npm run lint` / `npm run typecheck` / `npm run build`
   - Fix any issues found

7. **Review** - Re-read all changed files as if reviewing a PR:
   - Check for missed edge cases
   - Verify error handling
   - Ensure no debug code or TODOs remain
   - Confirm the feature matches the original request