plan-feature

Plan Feature Implementation

Create a detailed implementation plan for a new feature using deep thinking and structured task breakdown.

Usage

/plan-feature

This command uses "think harder" mode for comprehensive analysis.

Planning Framework

Phase 1: Requirements Analysis

Questions to Answer:

1. What needs to be built?

   • Feature description
   • Success criteria
   • Acceptance criteria

2. Why is it needed?

   • Business value
   • User benefit
   • Technical debt addressed

3. Who will use it?

   • End users
   • Internal systems
   • APIs

4. When is it needed?

   • Deadline
   • Milestone
   • Priority level

Phase 2: Technical Design

Architecture Considerations:

• Which modules will be affected?
• What new modules need to be created?
• How does it integrate with existing code?
• What design patterns apply?
• Are there relevant ADRs to follow?

Data Model:

• What data structures are needed?
• Database schema changes required?
• API request/response models?
• Validation rules?

Dependencies:

• External libraries needed?
• Internal module dependencies?
• Infrastructure requirements (Redis, PostgreSQL, etc.)?
• Configuration changes needed?

Phase 3: Task Breakdown

Create detailed TodoWrite task list with these categories:

Tests (TDD - Write First!):

• Unit tests for core logic
• Integration tests for APIs
• Edge case tests
• Error scenario tests
• Performance tests (if applicable)

Implementation:

• Data models (Pydantic classes)
• Business logic (core functions/classes)
• API endpoints (FastAPI routes)
• Middleware (if needed)
• Background tasks (if needed)

Integration:

• Database migrations (if schema changes)
• Configuration updates (env vars, config files)
• Dependency injection wiring
• OpenTelemetry instrumentation
• LangSmith tracing (if LLM-related)

Documentation:

• Docstrings for all public APIs
• CHANGELOG.md entry
• ADR (if architectural decision)
• README update (if user-facing)
• API documentation (OpenAPI)