task-segmentation
2
总安装量
2
周安装量
#62817
全站排名
安装命令
npx skills add https://github.com/cantagestudio/cosmicatlaspacker --skill task-segmentation
Agent 安装分布
amp
2
gemini-cli
2
github-copilot
2
codex
2
kimi-cli
2
cursor
2
Skill 文档
Task Segmentation
Segment subtasks into granular, actionable items before starting implementation.
â CRITICAL: Every Task MUST Have Subtasks
A task without subtasks is INCOMPLETE. AI MUST ensure every task has at least 3 specific, actionable subtasks.
Trigger Conditions
| Agent Action | Required Action |
|---|---|
| Any new task is added | â MUST have 3+ subtasks immediately |
| Moving task to In Progress | Segment subtasks BEFORE starting work |
| Subtask is vague or broad | Break into specific implementation steps |
| Subtask takes >30 min to complete | Split into smaller units |
| Task has no subtasks | â STOP – Add subtasks first |
Workflow
- BEFORE moving task to Worker
- Read the task and its subtasks
- Analyze each subtask for granularity
- Segment vague subtasks into specific, actionable items
- Update the Task document with segmented subtasks
- THEN move task to Worker (use
task-mover)
Segmentation Rules
When to Segment:
- Subtask description is vague (e.g., “Implement feature”)
- Subtask covers multiple concerns (e.g., “Add UI and logic”)
- Subtask would take significant time to complete
When NOT to Segment:
- Subtask is already specific and actionable
- Subtask is a single, atomic operation
- Further breakdown adds no clarity
â ï¸ CRITICAL: Format Rules
- ALL subtasks MUST use exactly 2-space indentation
- NO deeper nesting (no 4-space or 6-space indents)
- NO intermediate grouping headers (e.g.,
### Phase 1)
Example
Before Segmentation:
- [ ] Implement user authentication #feature !high
- [ ] Add login functionality
- [ ] Handle errors
After Segmentation:
- [ ] Implement user authentication #feature !high
- [ ] Create login form UI component
- [ ] Add form validation logic
- [ ] Implement API call to auth endpoint
- [ ] Store auth token in secure storage
- [ ] Add loading state during auth
- [ ] Display error message for invalid credentials
- [ ] Handle network error with retry option
Subtask Generation by Task Type
| Task Type | Required Subtask Categories |
|---|---|
| New Feature | UI ì¤ê³ â ì»´í¬ëí¸ ìì± â ë¡ì§ 구í â API ì°ë â ìë¬ ì²ë¦¬ â í ì¤í¸ |
| Bug Fix | ìì¸ ë¶ì â ì¬í íì¸ â ìì ì½ë ìì± â ì£ì§ ì¼ì´ì¤ íì¸ â í ì¤í¸ |
| Refactoring | 기존 ì½ë ë¶ì â ì 구조 ì¤ê³ â ì ì§ì ë§ì´ê·¸ë ì´ì â í ì¤í¸ íì¸ |
| Documentation | 구조 íì â ë´ì© ìì± â ìì ì¶ê° â 리뷰 ë°ì |
| UI/UX | ë ì´ìì ì¤ê³ â ì»´í¬ëí¸ êµ¬í â ì¤íì¼ ì ì© â ë°ìí ì²ë¦¬ â ì ê·¼ì± íì¸ |
More Examples
Example: New Feature Task
- [ ] ë¤í¬ëª¨ë í ê¸ ê¸°ë¥ ì¶ê° #feature #ui !medium
- [ ] ë¤í¬ëª¨ë ìí ì ì¥ ë¡ì§ 구í (UserDefaults)
- [ ] ThemeManager ì±ê¸í¤ ìì±
- [ ] ì¤ì íë©´ì í ê¸ UI ì¶ê°
- [ ] ìì íë í¸ ë¤í¬ëª¨ë ë²ì ì ì
- [ ] ì ì²´ ì± í
ë§ ì ì© íì¸
Example: Bug Fix Task
- [ ] ë¡ê·¸ì¸ ì¤í¨ ì í¬ëì ë²ê·¸ ìì #bug !high
- [ ] í¬ëì ë¡ê·¸ ë¶ì ë° ìì¸ íì
- [ ] nil ì²´í¬ ë¡ì§ ì¶ê°
- [ ] ìë¬ í¸ë¤ë§ ì½ë ìì
- [ ] ë¤ìí ì¤í¨ ì¼ì´ì¤ í
ì¤í¸
- [ ] íê· í
ì¤í¸ ìí
Pre-Segmentation Checklist
Before saving any task, verify:
- Task has at least 3 subtasks
- Each subtask uses action verb (Create, Implement, Add, Design, Configure, Handle)
- Each subtask is specific and actionable (not vague)
- Each subtask is completable in 1-2 hours
- Subtasks cover all aspects of the task (UI, Logic, Data, Integration, Testing)
- Subtasks use exactly 2-space indentation