feature-dev

Feature Development — Multi-phase Orchestration

A systematic feature development process: understand → explore → ask → design → implement → review → wrap up.

Core Principles

• Ask specific questions — identify all ambiguities, edge cases, unspecified behaviors. Wait for user's answer before implementing. Ask early — after understanding the codebase, before designing the architecture.
• Understand before writing — read existing code, conventions, and patterns before creating new code.
• Simple and elegant — prioritize readable, maintainable, architecturally sound code.
• Read files from agents — when launching agents, ask them to return a list of the most important files. After agents finish → read all listed files to build deep context.
• Use TodoWrite — track progress throughout all phases.

Phase 1: Discovery

Goal: Understand the feature to build.

1. Create a todo list with all phases.
2. Feature request: $ARGUMENTS
3. If unclear, ask user:
   • What problem does it solve?
   • What specifically should the feature do?
   • Any constraints or requirements?
4. Summarize understanding, confirm with user before continuing.

Phase 2: Codebase Exploration

Goal: Understand existing code relevant to the feature.

Skip if: user says they already know the codebase ("I know already", "skip explore") — jump directly to Phase 3.

Each agent must trace through the code comprehensively, focusing on understanding abstractions, architecture, and flow of control; each focused on a different aspect of the codebase.

Launch 2-3 code-explorer agents in parallel, each with a different focus:

• Agent 1: "Find features similar to [feature] and trace implementation"
• Agent 2: "Map architecture and abstractions for [relevant area]"
• Agent 3: "Analyze current implementation of [existing feature/area], trace through code comprehensively"
• Agent 4 (optional): "Analyze UI patterns / testing approaches / extension points related to [feature]"