task-splitting
Split large tasks into smaller subtasks. Use when a task spans many modules or requires phased implementation.
When & Why to Use This Skill
The Task Splitting skill is designed to enhance AI productivity by decomposing complex, multi-module requirements into manageable, independent subtasks. It ensures a structured approach to software development and project execution by focusing on verifiable functionality and maintaining a clear implementation roadmap, which significantly reduces context overload and improves execution accuracy.
Use Cases
- Complex Feature Engineering: Breaking down a high-level software requirement that spans multiple modules into 2-3 independently testable units of work.
- Phased Implementation Planning: Organizing large-scale projects into sequential phases to ensure each milestone delivers complete, functional, and verifiable results.
- Documentation & Roadmap Management: Automatically updating implementation plans and documentation to maintain a clear, concise structure for team collaboration or AI-driven development.
| name | task-splitting |
|---|---|
| description | Split large tasks into smaller subtasks. Use when a task spans many modules or requires phased implementation. |
Task Splitting
Instructions
Split specified task into 2-3 subtasks. Each subtask must:
- Be independently completable and testable
- Deliver complete functionality that can be verified (avoid partial implementations that are untestable)
- Focus on functionality and requirements (not code details)
Update docs/Implementation Plan.md with the new subtask structure. Keep concise—avoid redundancy to reduce AI context usage.