Repository navigation
Hierarchical Task Numbering System #1497
Description
Activity
yup, that would be great.
Today I asked LLM to remove 3 tasks, and it got really messy, because summaries at the bottom of the tasks.md were hard to update
Let's say initially there were tasks T001-T100, and I asked to remove T61, T71 and T82.
Renumbering of the existing tasks was done more or less correctly, but summaries were not### By Type: - Configuration: 2 tasks (T001-T002) - Foundation: 6 tasks (T003-T008) - Test Tasks: 18 tasks (T009-T021, T036-T039, T046-T049) - Implementation: 16 tasks (T022-T028, T040-T042, T050-T054) - added cache metrics task - Verification: 17 tasks (T029-T035, T043-T045, T055-T058) - Documentation/Polish: 11 tasks (T059-T069) - added user documentation task
it became out of order and hard to fix
This issue has been automatically marked as stale because it has not had any activity for 150 days. It will be closed in 30 days if no further activity occurs.
This issue has been automatically closed due to inactivity (180 days total). If you believe this issue is still relevant, please reopen it or create a new issue.
When LLMs add new tasks to
tasks.md, they must renumber all subsequent tasks in the entire file. This is inefficient:Proposed Solution
Use hierarchical task numbering (e.g., T1.1, T1.2, T1.3) grouped by phase/story. Adding a task only requires renumbering within the same parent group.
Format Example
Current (Sequential):
Proposed (Hierarchical):
Adding a new task: