A systematic approach to development that prioritizes context from project notes, MECE task breakdowns, and type-safe code changes with proper documentation.
A structured development workflow that ensures you always have full project context before making changes. This skill enforces reading project documentation, creating MECE (Mutually Exclusive, Collectively Exhaustive) task breakdowns, and maintaining type safety across all code changes.
This skill establishes a disciplined workflow for software development that:
Before responding to any development request, you MUST:
1. Read `.notes/project_overview.md` to understand the project's architecture, goals, and constraints
2. Read `.notes/task_list.md` to understand current priorities and work in progress
3. If these files don't exist, inform the user and ask if they should be created
**Never skip this step.** All decisions must be informed by project documentation.
When given a development task:
1. Create a MECE (Mutually Exclusive, Collectively Exhaustive) breakdown:
- Break the task into distinct, non-overlapping subtasks
- Ensure all aspects of the task are covered
- Present the breakdown to the user for confirmation
2. Identify affected code sections before making changes
3. Assess potential impacts on:
- Type safety
- Existing functionality
- Error handling
- Documentation needs
When writing or modifying code:
1. **Read First**: Always read relevant code sections before editing
2. **Preserve Functionality**: Maintain all existing behavior unless explicitly changing it
3. **Type Safety**: NEVER break type safety. Add proper types for all new code.
4. **Error Handling**: Ensure all new code has appropriate error handling
5. **Documentation**: Add comments and documentation for new code, especially:
- Complex logic
- Public APIs
- Non-obvious design decisions
You MUST:
**Base Mode** (default):
**Enhanced Mode** (for complex problems):
- Architectural changes
- Complex algorithms
- Cross-cutting concerns
- Performance optimization
- Multiple implementation approaches
- Trade-offs and recommendations
- Impact assessment across codebase
- Testing strategy
To activate Enhanced Mode, user should say: "Use enhanced mode" or the task complexity will trigger it automatically.
If `.notes/` directory doesn't exist, suggest creating these files:
**`.notes/project_overview.md`** should contain:
**`.notes/task_list.md`** should contain:
Always prioritize information from `.notes/` directory as the source of truth (weight: 1.0). If conflicts arise between notes and code, flag them to the user.
```
User: "Add user authentication to the app"
Agent:
1. [Reads .notes/project_overview.md and .notes/task_list.md]
2. "Based on project notes, I see we're using [framework]. Here's a MECE breakdown:
A. Authentication Infrastructure
- Set up auth provider configuration
- Create auth middleware
B. User Interface
- Login/logout UI components
- Protected route handling
C. Data Layer
- User model with proper types
- Session management
D. Testing & Documentation
- Auth flow tests
- Update project documentation
Should I proceed with this breakdown?"
```
```
User: "Fix the search not working on mobile"
Agent:
1. [Reads project notes]
2. [Reads search component code]
3. "I've reviewed the search implementation. The issue appears to be [explanation].
Task breakdown:
- Identify root cause in SearchComponent
- Fix type issue with event handlers
- Add mobile-specific error handling
- Test on mobile viewports
- Update component documentation
This will preserve all existing functionality while fixing the mobile issue."
```
Leave a review
No reviews yet. Be the first to review this skill!
# Download SKILL.md from killerskills.ai/api/skills/project-notes-driven-development/raw