You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit f1b749f
Browse filesBrowse the repository at this point in the historyBrowse files
feat: add explicit task dependency declarations and execution wave DAG (github#1934)
Add `(depends on T###)` suffix to the task format for explicit
inter-task dependency tracking. This enables AI agents to identify
which tasks can run in parallel and which must wait.
Changes:
- tasks-template.md: Document dependency suffix in format section,
add dependency annotations to sample tasks, replace Parallel
Example section with structured Execution Wave DAG
- commands/tasks.md: Add dependency suffix as format component github#6,
instruct task generation to include Wave DAG section
Co-Authored-By: Claude Sonnet 4.6 <[email protected]>
Copy file name to clipboardExpand all lines: templates/commands/tasks.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -85,8 +85,9 @@ You **MUST** consider the user input before proceeding (if not empty).
85
85
- Final Phase: Polish & cross-cutting concerns
86
86
- All tasks must follow the strict checklist format (see Task Generation Rules below)
87
87
- Clear file paths for each task
88
+
- Explicit `(depends on T###, T###)` suffix on every task that has dependencies on other tasks
89
+
- An **Execution Wave DAG** section that groups tasks into waves by dependency resolution — tasks within the same wave can run in parallel, each wave starts after its dependencies complete
88
90
- Dependencies section showing story completion order
5. **Report**: Output path to generated tasks.md and summary:
@@ -141,7 +142,7 @@ The tasks.md should be immediately executable - each task must be specific enoug
141
142
Every task MUST strictly follow this format:
142
143
143
144
```text
144
-
- [ ] [TaskID] [P?] [Story?] Description with file path
145
+
- [ ] [TaskID] [P?] [Story?] Description with file path [(depends on ...)]
145
146
```
146
147
147
148
**Format Components**:
@@ -152,17 +153,18 @@ Every task MUST strictly follow this format:
152
153
4.**[Story] label**: REQUIRED for user story phase tasks only
153
154
- Format: [US1], [US2], [US3], etc. (maps to user stories from spec.md)
154
155
- Setup phase: NO story label
155
-
- Foundational phase: NO story label
156
+
- Foundational phase: NO story label
156
157
- User Story phases: MUST have story label
157
158
- Polish phase: NO story label
158
159
5.**Description**: Clear action with exact file path
160
+
6.**(depends on ...)**: Append at end if the task depends on specific other task IDs. Omit if the task has no dependencies within its phase. Use comma-separated IDs for multiple dependencies.
0 commit comments