Feature Dev

Phase 1: Discovery

Goal: Understand what needs to be built

Initial request: $ARGUMENTS

Actions:

1. Initialize the plan using update_status with all phases.
2. If feature unclear, ask user for:
   • What problem are they solving?
   • What should the feature do?
   • Any constraints or requirements?
3. Summarize understanding and confirm with user.

Phase 2: Codebase Exploration

Goal: Understand relevant existing code and patterns at both high and low levels

Actions:

1. Use the code-explorer skill (via agent_skill_read_doc) to analyze the codebase. Target different aspects:
   • Trace through features similar to the requested one.
   • Map the architecture and abstractions for the relevant area.
   • Identify UI patterns, testing approaches, or extension points.
2. Once exploration is done, read all identified files (using open or open_entire_file) to build deep understanding. Note that open is paginated to 100 lines; use scroll_down to read more.
3. Present comprehensive summary of findings and patterns discovered.

Phase 3: Clarifying Questions

Goal: Fill in gaps and resolve all ambiguities before designing

CRITICAL: This is one of the most important phases. DO NOT SKIP.

Actions:

1. Review the codebase findings and original feature request.
2. Identify underspecified aspects: edge cases, error handling, integration points, scope boundaries, design preferences, backward compatibility, performance needs.
3. Present all questions to the user in a clear, organized list.
4. Wait for answers before proceeding to architecture design.

If the user says "whatever you think is best", provide your recommendation and get explicit confirmation.

Phase 4: Architecture Design

Goal: Design multiple implementation approaches with different trade-offs

Actions:

1. Use the code-architect skill (via agent_skill_read_doc) to design 2-3 approaches with different focuses:
   • Minimal changes (smallest change, maximum reuse).
   • Clean architecture (maintainability, elegant abstractions).
   • Pragmatic balance (speed + quality).
2. Review all approaches and form your opinion on which fits best for this specific task.
3. Present to user: brief summary of each approach, trade-offs comparison, your recommendation with reasoning, and concrete implementation differences.
4. Ask user which approach they prefer.

Phase 5: Implementation

Goal: Build the feature

DO NOT START WITHOUT USER APPROVAL

Actions:

1. Wait for explicit user approval.
2. Read all relevant files identified in previous phases.
3. Implement following chosen architecture.
4. Follow codebase conventions strictly.
5. Write clean, well-documented code.
6. Update plan status as you progress using update_status.

Phase 6: Quality Review

Goal: Ensure code is simple, DRY, elegant, easy to read, and functionally correct

Actions:

1. Use the code-reviewer skill (via agent_skill_read_doc) with different focuses:
   • Simplicity/DRY/elegance.
   • Bugs/functional correctness.
   • Project conventions/abstractions.
2. Consolidate findings and identify highest severity issues that you recommend fixing.
3. Present findings to user and ask what they want to do (fix now, fix later, or proceed as-is).
4. Address issues based on user decision.

Phase 7: Summary

Goal: Document what was accomplished

Actions:

1. Mark all plan items complete in update_status.
2. Summarize:
   • What was built.
   • Key decisions made.
   • Files modified.
   • Suggested next steps.
3. Use submit to provide the final result.