Automate analysis and planning for new feature implementations on a codebase. Use when asked to plan a new feature, design a feature implementation, or analyze how to add functionality to an existing project. This skill reads debate.md to track discussions, then analyzes the codebase via its codewiki folder to create comprehensive, context-aware feature implementation plans with step-by-step guides that respect existing architecture patterns.
التثبيت
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
Automate analysis and planning for new feature implementations on a codebase. Use when asked to plan a new feature, design a feature implementation, or analyze how to add functionality to an existing project. This skill reads debate.md to track discussions, then analyzes the codebase via its codewiki folder to create comprehensive, context-aware feature implementation plans with step-by-step guides that respect existing architecture patterns.
Feature Planner
Overview
Automates the complete workflow for planning new feature implementations on existing codebases. The skill follows a systematic approach:
### Phase 6: Create Implementation Plan
Generate a step-by-step implementation guide.
Document in `.feature-plans/<feature-name>/implementation-plan.md`:
```markdown
# Implementation Plan: <feature-name>
## Pre-Implementation Checklist
- [ ] Review and approve design document
- [ ] Create feature branch: `feature/<feature-name>`
- [ ] Install any new dependencies
- [ ] Set up development environment (if needed)
## Implementation Steps
### Step 1: Database/Model Changes
**Why first:** Schema changes should be in place before code that uses them
**Tasks:**
1. [ ] Create migration file: `migrations/<timestamp>_add_<feature>.sql`
- File: `<path>`
- Add tables/columns: [list]
2. [ ] Define data models
- File: `<path>/models.py` or `<path>/types.ts`
- Models: [list]
3. [ ] Run migration
```bash
<migration-command>
Verify schema changes
<verify-command>
Files to create/modify:
<file-path-1> - [description]
<file-path-2> - [description]
Estimated complexity: [Low/Medium/High]
Step 2: Backend Service/API Layer
Why next: Core logic before UI
Tasks:
Create service module
File: <path>/service.py
Methods: [list]
Implement business logic
Validation rules
Data processing
Error handling
Create API endpoints
File: <path>/routes.py or <path>/api.ts
Endpoints: [list]
Write unit tests
File: <path>/test_service.py
Coverage: [methods]
Code patterns to follow:
# Example following project conventionsclass <FeatureName>Service:
def__init__(self, db):
self.db = db
asyncdefcreate(self, data):
# Implementationpass
Files to create/modify:
<file-path-1> - [description]
<file-path-2> - [description]
Estimated complexity: [Low/Medium/High]
Step 3: Frontend Components (if applicable)
Tasks:
Create UI components
File: <path>/Component.tsx
Props: [list]
Implement state management
Hook/store: <path>
State shape: [description]
Add form validation
Library: [validation library]
Rules: [list]
Style components
Follow design system: [reference]
Write component tests
File: <path>/Component.test.tsx
Code patterns to follow:
// Example following project conventionsexportfunction <ComponentName>() {
const [state, setState] = useState()
return (
// JSX
)
}
Files to create/modify:
<file-path-1> - [description]
<file-path-2> - [description]
Estimated complexity: [Low/Medium/High]
Step 4: Integration
Tasks:
Wire up frontend to API
API client: <path>
Endpoints used: [list]
Add navigation/routing
Route: <route-path>
File: <router-file>
Update menu/navigation UI
File: <nav-component>
Write integration tests
File: <test-file>
Scenarios: [list]
Files to create/modify:
<file-path-1> - [description]
<file-path-2> - [description]
Estimated complexity: [Low/Medium/High]
Step 5: Testing & Documentation
Tasks:
Run all tests
<test-command>
Manual testing
Happy path: [scenario]
Error cases: [scenarios]
Edge cases: [scenarios]
Update documentation
Update README.md if needed
Update API docs: <api-doc-file>
Add inline code comments for complex logic
Update codewiki (if exists)
Add feature to relevant pages
Update architecture diagrams if structure changed
Files to create/modify:
<file-path-1> - [description]
<file-path-2> - [description]
Estimated complexity: [Low/Medium/High]
Step 6: Code Review & Deployment Prep
Tasks:
Self-review checklist
Code follows project conventions
No console.log/debug statements
Error handling in place
Tests passing
No sensitive data exposed
Create pull request
Title: "feat: "
Description: Link to design doc and requirements
Reviewers: [suggest reviewers]
Address review feedback
Merge to main branch
Estimated complexity: [Low/Medium/High]
Post-Implementation
Verification
Test in staging environment
Performance testing (if needed)
Security review (if handling sensitive data)
Monitoring
Set up logging for new endpoints
Add metrics/monitoring (if applicable)
Document runbook for operational issues
Rollout
Deploy to production
Monitor for errors
Announce to team/users
Rollback Plan
If issues arise:
[Rollback step 1]
[Rollback step 2]
Notes
[Any additional notes, gotchas, or considerations]
### Phase 7: Present Plan to User
**Summary output:**
Feature Plan Created:
📁 Location: .feature-plans//
📄 Documents:
requirements.md - Feature requirements and constraints
context-analysis.md - Codebase context and integration points
design.md - Architectural design and technical specifications
