.claude/commands/tasks.md · dumber

Break down the plan into executable tasks.

This is the third step in the Spec-Driven Development lifecycle.

Given the context provided as an argument, do this:

Run scripts/check-task-prerequisites.sh --json from repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute.
Load and analyze available design documents:
- Always read plan.md for tech stack and libraries
- IF EXISTS: Read data-model.md for entities
- IF EXISTS: Read contracts/ for API endpoints
- IF EXISTS: Read research.md for technical decisions
- IF EXISTS: Read quickstart.md for test scenarios
Note: Not all projects have all documents. For example:
- CLI tools might not have contracts/
- Simple libraries might not need data-model.md
- Generate tasks based on what's available
Generate tasks following the template:
- Use /templates/tasks-template.md as the base
- Replace example tasks with actual tasks based on:
  - Setup tasks: Project init, dependencies, linting
  - Test tasks [P]: One per contract, one per integration scenario
  - Core tasks: One per entity, service, CLI command, endpoint
  - Integration tasks: DB connections, middleware, logging
  - Polish tasks [P]: Unit tests, performance, docs
Task generation rules:
- Each contract file → contract test task marked [P]
- Each entity in data-model → model creation task marked [P]
- Each endpoint → implementation task (not parallel if shared files)
- Each user story → integration test marked [P]
- Different files = can be parallel [P]
- Same file = sequential (no [P])
Order tasks by dependencies:
- Setup before everything
- Tests before implementation (TDD)
- Models before services
- Services before endpoints
- Core before integration
- Everything before polish
Include parallel execution examples:
- Group [P] tasks that can run together
- Show actual Task agent commands
Create FEATURE_DIR/tasks.md with:
- Correct feature name from implementation plan
- Numbered tasks (T001, T002, etc.)
- Clear file paths for each task
- Dependency notes
- Parallel execution guidance

Context for task generation: $ARGUMENTS

The tasks.md should be immediately executable - each task must be specific enough that an LLM can complete it without additional context.

source

1
2Break down the plan into executable tasks.
3
4This is the third step in the Spec-Driven Development lifecycle.
5
6Given the context provided as an argument, do this:
7
81. Run `scripts/check-task-prerequisites.sh --json` from repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute.
92. Load and analyze available design documents:
10   - Always read plan.md for tech stack and libraries
11   - IF EXISTS: Read data-model.md for entities
12   - IF EXISTS: Read contracts/ for API endpoints
13   - IF EXISTS: Read research.md for technical decisions
14   - IF EXISTS: Read quickstart.md for test scenarios
15
16   Note: Not all projects have all documents. For example:
17   - CLI tools might not have contracts/
18   - Simple libraries might not need data-model.md
19   - Generate tasks based on what's available
20
213. Generate tasks following the template:
22   - Use `/templates/tasks-template.md` as the base
23   - Replace example tasks with actual tasks based on:
24     * **Setup tasks**: Project init, dependencies, linting
25     * **Test tasks [P]**: One per contract, one per integration scenario
26     * **Core tasks**: One per entity, service, CLI command, endpoint
27     * **Integration tasks**: DB connections, middleware, logging
28     * **Polish tasks [P]**: Unit tests, performance, docs
29
304. Task generation rules:
31   - Each contract file → contract test task marked [P]
32   - Each entity in data-model → model creation task marked [P]
33   - Each endpoint → implementation task (not parallel if shared files)
34   - Each user story → integration test marked [P]
35   - Different files = can be parallel [P]
36   - Same file = sequential (no [P])
37
385. Order tasks by dependencies:
39   - Setup before everything
40   - Tests before implementation (TDD)
41   - Models before services
42   - Services before endpoints
43   - Core before integration
44   - Everything before polish
45
466. Include parallel execution examples:
47   - Group [P] tasks that can run together
48   - Show actual Task agent commands
49
507. Create FEATURE_DIR/tasks.md with:
51   - Correct feature name from implementation plan
52   - Numbered tasks (T001, T002, etc.)
53   - Clear file paths for each task
54   - Dependency notes
55   - Parallel execution guidance
56
57Context for task generation: $ARGUMENTS
58
59The tasks.md should be immediately executable - each task must be specific enough that an LLM can complete it without additional context.

tasks.md RawHistoryFolder

tasks.md Raw History Folder