Rulebook Task Management
When to Create Tasks
Create tasks for:
- •New features/capabilities
- •Breaking changes
- •Architecture changes
- •Performance/security work
Skip for:
- •Bug fixes
- •Typos, formatting, comments
- •Dependency updates (non-breaking)
Task Commands
bash
rulebook task create <task-id> # Create new task rulebook task list # List all tasks rulebook task show <task-id> # Show task details rulebook task validate <task-id> # Validate structure rulebook task archive <task-id> # Archive completed task
Mandatory Workflow
NEVER start implementation without creating a task first:
- •STOP - Do not start coding
- •Create task -
rulebook task create <task-id> - •Plan - Write proposal.md and tasks.md
- •Spec - Write spec deltas
- •Validate -
rulebook task validate <task-id> - •THEN - Start implementation
Task Directory Structure
code
rulebook/tasks/<task-id>/
├── proposal.md # Why and what changes
├── tasks.md # Implementation checklist
├── design.md # Technical design (optional)
└── specs/
└── <module>/
└── spec.md # Technical specifications
Best Practices
- •Always create task first - Document before implementing
- •Keep tasks.md simple - Only checklist items
- •Put details in specs - Technical requirements in spec files
- •Validate before implementing - Run
rulebook task validate - •Archive when done - Move completed tasks to archive