Task Add
Add new tasks to Task documents when work items are discovered. Design tasks for parallel development across multiple workers.
Trigger Conditions
| Agent Action |
Example |
| User requests new feature |
"Add dark mode toggle" |
| Discovering bug during work |
Found edge case that needs fix |
| Breaking down large task |
Split into subtasks |
| Identifying follow-up work |
"After this, we need to..." |
Task Format
- [ ] TaskTitle #tag !priority Deadline(yyyy:mm:dd)
- [ ] Subtask 1
- [ ] Subtask 2
- [ ] Subtask 3
⛔ CRITICAL: Subtask is MANDATORY
Every task MUST have at least 3 subtasks. A task without subtasks is INCOMPLETE and will be REJECTED.
❌ FORBIDDEN - Task without subtasks:
- [ ] Implement login feature #auth !high
✅ REQUIRED - Task WITH subtasks:
- [ ] Implement login feature #auth !high
- [ ] Design login UI layout
- [ ] Create LoginView SwiftUI component
- [ ] Implement form validation logic
- [ ] Add API integration for authentication
- [ ] Handle error states and messages
Subtask Requirements
| Requirement |
Rule |
| Minimum Count |
Every task MUST have at least 3 subtasks |
| Granularity |
Each subtask completable in 1-2 hours |
| Specificity |
Use action verbs: Create, Implement, Add, Design, Configure |
| Independence |
Each subtask independently verifiable |
Subtask Generation by Task Type
| Task Type |
Required Subtasks |
| New Feature |
UI 설계, 컴포넌트 생성, 로직 구현, API 연동, 에러 처리 |
| Bug Fix |
원인 분석, 수정 코드 작성, 엣지 케이스 확인, 테스트 검증 |
| Refactoring |
기존 코드 분석, 새 구조 설계, 마이그레이션, 테스트 |
| Documentation |
구조 파악, 내용 작성, 예제 추가 |
Section Placement
| Task Type |
Target Section |
| New feature request |
Backlog |
| Bug found during work |
Backlog |
| Subtask breakdown |
Same section as parent |
| Follow-up work |
Backlog |
🔀 Parallel Development Guidelines
⚠️ CRITICAL: When adding tasks, consider parallel development:
- Design for Independence: Each task should be completable without modifying files that other tasks touch
- Isolate by Directory: Prefer tasks that work in separate directories (e.g.,
/Views/FeatureA/ vs /Views/FeatureB/)
- Avoid Shared File Edits: Don't create multiple tasks that modify the same file
Tag Reference
| Tag |
Use Case |
#feature |
New functionality |
#bug |
Bug fix |
#refactor |
Code improvement |
#docs |
Documentation |
#test |
Testing |
#ui |
UI/UX work |
Priority Reference
| Priority |
Use Case |
Examples |
!high |
Urgent, blocker |
Build failure, crash, critical bug |
!medium |
Normal priority |
General feature development (default) |
!low |
Nice to have |
Refactoring, documentation, code cleanup |
⚠️ CRITICAL: Format Protection
Absolute Rules:
- NEVER modify existing Task document structure
- ONLY add priority tags (
!high, !medium, !low)
- NEVER change section order, table structure, or markdown format
⚠️ CRITICAL: Task Document Format Rules
Strict Format Requirements:
- Subtasks MUST use exactly 2-space indentation (no more, no less)
- NO intermediate grouping headers (e.g.,
### Phase 1, #### Step A) are allowed
- Task hierarchy is flat: Parent task → Subtasks (2-space indent) ONLY
⛔ CRITICAL: Duplicate Section Prevention
Before ANY edit, verify document structure:
- Read entire file first - Check existing section headers
- Count section occurrences - Each section (
## Backlog, ## Worker1, etc.) MUST appear exactly ONCE
- If duplicates found - STOP and fix by merging duplicate sections
- Add tasks to EXISTING sections - NEVER create new section headers
Detection Pattern:
## Review ← First occurrence (KEEP)
...tasks...
## Done ← First occurrence (KEEP)
...tasks...
## Review ← DUPLICATE (REMOVE - merge tasks to first ## Review)
## Done ← DUPLICATE (REMOVE - merge tasks to first ## Done)
Fix Procedure:
- Identify all duplicate sections
- Merge tasks from duplicate sections into first occurrence
- Delete duplicate section headers and empty lines
- Verify only ONE of each section exists
Workflow
- Read entire Task file - Verify no duplicate sections exist
- Identify new work item
- Determine appropriate Task file (by stage)
- Determine priority (use Priority Decision Guide)
- Format task with proper syntax including priority tag
- ⛔ MANDATORY: Generate 3+ subtasks - Analyze scope, break down by work type
- Find existing target section (DO NOT create new section)
- Add task WITH subtasks to section (bottom of existing section)
- Verify subtask count - Must have at least 3 subtasks
- Before saving - Verify no duplicate sections created
- Save file
Related Skills
| Skill |
When to Use |
task-segmentation |
Before moving task to Worker, segment subtasks into granular items |
task-mover |
After adding task, move between sections as work progresses |
1---2name: task-add3description: [Task Mgmt] A Skill that adds new tasks with priority tags to Docs/Task/{StepName}_Task.md documents for multi-agent parallel development. AI agent MUST invoke this skill AUTOMATICALLY when (1) discovering new work items during implementation, (2) user requests a new feature/fix, (3) breaking down a large task into subtasks, (4) identifying follow-up work after completing a task. CRITICAL - Never modify document structure, only add tasks with proper priority tags (!high, !medium, !low). Tasks should be distributed to avoid file conflicts between workers. (user)4---5
6# Task Add
7
8Add new tasks to Task documents when work items are discovered. Design tasks for parallel development across multiple workers.
9
10## Trigger Conditions
11
12| Agent Action | Example |
13|--------------|---------|
14| User requests new feature | "Add dark mode toggle" |
15| Discovering bug during work | Found edge case that needs fix |
16| Breaking down large task | Split into subtasks |
17| Identifying follow-up work | "After this, we need to..." |
18
19## Task Format
20
21```markdown
22- [ ] TaskTitle #tag !priority Deadline(yyyy:mm:dd)
23 - [ ] Subtask 1
24 - [ ] Subtask 2
25 - [ ] Subtask 3
26```
27
28## ⛔ CRITICAL: Subtask is MANDATORY
29
30**Every task MUST have at least 3 subtasks. A task without subtasks is INCOMPLETE and will be REJECTED.**
31
32❌ **FORBIDDEN - Task without subtasks:**
33```markdown
34- [ ] Implement login feature #auth !high
35```
36
37✅ **REQUIRED - Task WITH subtasks:**
38```markdown
39- [ ] Implement login feature #auth !high
40 - [ ] Design login UI layout
41 - [ ] Create LoginView SwiftUI component
42 - [ ] Implement form validation logic
43 - [ ] Add API integration for authentication
44 - [ ] Handle error states and messages
45```
46
47### Subtask Requirements
48
49| Requirement | Rule |
50|-------------|------|
51| **Minimum Count** | Every task MUST have **at least 3 subtasks** |
52| **Granularity** | Each subtask completable in 1-2 hours |
53| **Specificity** | Use action verbs: Create, Implement, Add, Design, Configure |
54| **Independence** | Each subtask independently verifiable |
55
56### Subtask Generation by Task Type
57
58| Task Type | Required Subtasks |
59|-----------|-------------------|
60| New Feature | UI 설계, 컴포넌트 생성, 로직 구현, API 연동, 에러 처리 |
61| Bug Fix | 원인 분석, 수정 코드 작성, 엣지 케이스 확인, 테스트 검증 |
62| Refactoring | 기존 코드 분석, 새 구조 설계, 마이그레이션, 테스트 |
63| Documentation | 구조 파악, 내용 작성, 예제 추가 |
64
65## Section Placement
66
67| Task Type | Target Section |
68|-----------|----------------|
69| New feature request | Backlog |
70| Bug found during work | Backlog |
71| Subtask breakdown | Same section as parent |
72| Follow-up work | Backlog |
73
74## 🔀 Parallel Development Guidelines
75
76**⚠️ CRITICAL: When adding tasks, consider parallel development:**
77
781. **Design for Independence**: Each task should be completable without modifying files that other tasks touch
792. **Isolate by Directory**: Prefer tasks that work in separate directories (e.g., `/Views/FeatureA/` vs `/Views/FeatureB/`)
803. **Avoid Shared File Edits**: Don't create multiple tasks that modify the same file
81
82## Tag Reference
83
84| Tag | Use Case |
85|-----|----------|
86| `#feature` | New functionality |
87| `#bug` | Bug fix |
88| `#refactor` | Code improvement |
89| `#docs` | Documentation |
90| `#test` | Testing |
91| `#ui` | UI/UX work |
92
93## Priority Reference
94
95| Priority | Use Case | Examples |
96|----------|----------|----------|
97| `!high` | Urgent, blocker | Build failure, crash, critical bug |
98| `!medium` | Normal priority | General feature development (default) |
99| `!low` | Nice to have | Refactoring, documentation, code cleanup |
100
101## ⚠️ CRITICAL: Format Protection
102
103**Absolute Rules:**
104- NEVER modify existing Task document structure
105- ONLY add priority tags (`!high`, `!medium`, `!low`)
106- NEVER change section order, table structure, or markdown format
107
108## ⚠️ CRITICAL: Task Document Format Rules
109
110**Strict Format Requirements:**
111- Subtasks MUST use exactly 2-space indentation (no more, no less)
112- NO intermediate grouping headers (e.g., `### Phase 1`, `#### Step A`) are allowed
113- Task hierarchy is flat: Parent task → Subtasks (2-space indent) ONLY
114
115## ⛔ CRITICAL: Duplicate Section Prevention
116
117**Before ANY edit, verify document structure:**
118
1191. **Read entire file first** - Check existing section headers
1202. **Count section occurrences** - Each section (`## Backlog`, `## Worker1`, etc.) MUST appear exactly ONCE
1213. **If duplicates found** - STOP and fix by merging duplicate sections
1224. **Add tasks to EXISTING sections** - NEVER create new section headers
123
124**Detection Pattern:**
125```
126## Review ← First occurrence (KEEP)
127...tasks...
128## Done ← First occurrence (KEEP)
129...tasks...
130## Review ← DUPLICATE (REMOVE - merge tasks to first ## Review)
131## Done ← DUPLICATE (REMOVE - merge tasks to first ## Done)
132```
133
134**Fix Procedure:**
1351. Identify all duplicate sections
1362. Merge tasks from duplicate sections into first occurrence
1373. Delete duplicate section headers and empty lines
1384. Verify only ONE of each section exists
139
140## Workflow
141
1421. **Read entire Task file** - Verify no duplicate sections exist
1432. Identify new work item
1443. Determine appropriate Task file (by stage)
1454. **Determine priority** (use Priority Decision Guide)
1465. Format task with proper syntax including priority tag
1476. **⛔ MANDATORY: Generate 3+ subtasks** - Analyze scope, break down by work type
1487. **Find existing target section** (DO NOT create new section)
1498. Add task WITH subtasks to section (bottom of existing section)
1509. **Verify subtask count** - Must have at least 3 subtasks
15110. **Before saving** - Verify no duplicate sections created
15211. Save file
153
154## Related Skills
155
156| Skill | When to Use |
157|-------|-------------|
158| `task-segmentation` | Before moving task to Worker, segment subtasks into granular items |
159| `task-mover` | After adding task, move between sections as work progresses |
majiayu000