eff7e339af
- Remove legacy rule files (documentation.mdc, general_development.mdc, etc.) - Implement new meta-rule system with core, app, and feature categories - Add meta-rule files for different workflows (bug diagnosis, feature planning, etc.) - Create organized directory structure: core/, app/, features/, database/, etc. - Add comprehensive README.md for rules documentation - Establish new rule architecture with always-on and workflow-specific rules This restructuring improves rule organization, enables better workflow management, and provides clearer separation of concerns for different development tasks.
161 lines
3.5 KiB
Plaintext
161 lines
3.5 KiB
Plaintext
# Planning Examples — No Time Estimates
|
|
|
|
> **Agent role**: Reference this file for detailed planning examples and
|
|
anti-patterns when creating project plans.
|
|
|
|
## 🎯 Example Planning (No Time Estimates)
|
|
|
|
### **Example 1: Simple Feature**
|
|
|
|
```
|
|
|
|
Phase 1: Core implementation
|
|
|
|
- Basic functionality
|
|
|
|
- Single platform support
|
|
|
|
- Unit tests
|
|
|
|
Phase 2: Platform expansion
|
|
|
|
- Multi-platform support
|
|
|
|
- Integration tests
|
|
|
|
Phase 3: Polish
|
|
|
|
- User testing
|
|
|
|
- Edge case handling
|
|
|
|
```
|
|
|
|
### **Example 2: Complex Cross-Platform Feature**
|
|
|
|
```
|
|
|
|
Phase 1: Foundation
|
|
|
|
- Architecture design
|
|
|
|
- Core service implementation
|
|
|
|
- Basic web platform support
|
|
|
|
Phase 2: Platform Integration
|
|
|
|
- Mobile platform support
|
|
|
|
- Desktop platform support
|
|
|
|
- Cross-platform consistency
|
|
|
|
Phase 3: Testing & Polish
|
|
|
|
- Comprehensive testing
|
|
|
|
- Error handling
|
|
|
|
- User experience refinement
|
|
|
|
```
|
|
|
|
## 🚫 Anti-Patterns to Avoid
|
|
|
|
- **"This should take X days"** - Red flag for time estimation
|
|
|
|
- **"Just a few hours"** - Ignores complexity and testing
|
|
|
|
- **"Similar to X"** - Without considering differences
|
|
|
|
- **"Quick fix"** - Nothing is ever quick in software
|
|
|
|
- **"No testing needed"** - Testing always takes effort
|
|
|
|
## ✅ Best Practices
|
|
|
|
### **When Planning:**
|
|
|
|
1. **Break down everything** - no work is too small to plan
|
|
|
|
2. **Consider all platforms** - web, mobile, desktop differences
|
|
|
|
3. **Include testing strategy** - unit, integration, and user testing
|
|
|
|
4. **Account for unknowns** - there are always surprises
|
|
|
|
5. **Focus on dependencies** - what blocks what
|
|
|
|
### **When Presenting Plans:**
|
|
|
|
1. **Show the phases** - explain the logical progression
|
|
|
|
2. **Highlight dependencies** - what could block progress
|
|
|
|
3. **Define milestones** - clear success criteria
|
|
|
|
4. **Identify risks** - what could go wrong
|
|
|
|
5. **Suggest alternatives** - ways to reduce scope or complexity
|
|
|
|
## 🔄 Continuous Improvement
|
|
|
|
### **Track Progress**
|
|
|
|
- Record planned vs. actual phases completed
|
|
|
|
- Identify what took longer than expected
|
|
|
|
- Learn from complexity misjudgments
|
|
|
|
- Adjust planning process based on experience
|
|
|
|
### **Learn from Experience**
|
|
|
|
- **Underestimated complexity**: Increase complexity categories
|
|
|
|
- **Missed dependencies**: Improve dependency mapping
|
|
|
|
- **Platform surprises**: Better platform research upfront
|
|
|
|
## 🎯 Integration with Harbor Pilot
|
|
|
|
This rule works in conjunction with:
|
|
|
|
- **Project Planning**: Focuses on phases and milestones
|
|
|
|
- **Resource Allocation**: Based on complexity, not time
|
|
|
|
- **Risk Management**: Identifies blockers and dependencies
|
|
|
|
- **Stakeholder Communication**: Sets progress-based expectations
|
|
|
|
---
|
|
|
|
**See also**: `.cursor/rules/development/realistic_time_estimation.mdc` for
|
|
the core principles and framework.
|
|
|
|
## Model Implementation Checklist
|
|
|
|
### Before Planning
|
|
|
|
- [ ] **Requirements Review**: Understand all requirements completely
|
|
- [ ] **Stakeholder Input**: Gather input from all stakeholders
|
|
- [ ] **Complexity Assessment**: Evaluate technical and business complexity
|
|
- [ ] **Platform Analysis**: Consider requirements across all target platforms
|
|
|
|
### During Planning
|
|
|
|
- [ ] **Phase Definition**: Define clear phases and milestones
|
|
- [ ] **Dependency Mapping**: Map dependencies between tasks
|
|
- [ ] **Risk Identification**: Identify potential risks and challenges
|
|
- [ ] **Testing Strategy**: Plan comprehensive testing approach
|
|
|
|
### After Planning
|
|
|
|
- [ ] **Stakeholder Review**: Review plan with stakeholders
|
|
- [ ] **Documentation**: Document plan clearly with phases and milestones
|
|
- [ ] **Team Communication**: Communicate plan to team
|
|
- [ ] **Progress Tracking**: Set up monitoring and tracking mechanisms
|