name: Tasks description: Track implementation tasks for features. Use when adding, listing, starting, or completing tasks. Manages specs/[feature]/tasks.json and logs completions to history.md.
Task Management
Track implementation work in specs/[feature]/tasks.json with completion logs in history.md.
Task Lifecycle
add → start → work → verify → complete → logged
Operations
List tasks
bun .claude/skills/tasks/scripts/task-cli.ts list <feature>
Add task
bun .claude/skills/tasks/scripts/task-cli.ts add <feature> "<description>" --steps "Step 1" "Step 2" --validation "Test passes"
Start task (set in-progress)
bun .claude/skills/tasks/scripts/task-cli.ts start <feature> <task-id>
Complete task (logs to history)
bun .claude/skills/tasks/scripts/task-cli.ts complete <feature> <task-id> "<summary>" "<verification>"
Show task details
bun .claude/skills/tasks/scripts/task-cli.ts show <feature> <task-id>
tasks.json Schema
{
"feature": "feature-name",
"tasks": [{
"id": "task-1",
"description": "What to implement",
"steps": ["Step 1", "Step 2"],
"validation": ["Test X passes", "Manual check Y"],
"status": "pending"
}]
}
Status values: pending | in-progress | done
history.md Format
Completions append to specs/[feature]/history.md:
## [YYYY-MM-DD] task-id
**Summary:** What was accomplished
**Verification:** How it was tested
Task Granularity
Good task = completable in one focused session:
- Has clear start/end
- 1-3 steps
- Testable outcome
Split if task has:
- Multiple unrelated steps
- Dependencies on other incomplete tasks
- No clear "done" criteria