rulebook-task-management
Spec-driven task management for features and breaking changes using OpenSpec format. Use when creating new features, planning breaking changes, organizing development work, or managing project tasks with proposals and specifications.
Best use case
rulebook-task-management is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Spec-driven task management for features and breaking changes using OpenSpec format. Use when creating new features, planning breaking changes, organizing development work, or managing project tasks with proposals and specifications.
Teams using rulebook-task-management should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/rulebook-task-management/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How rulebook-task-management Compares
| Feature / Agent | rulebook-task-management | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Spec-driven task management for features and breaking changes using OpenSpec format. Use when creating new features, planning breaking changes, organizing development work, or managing project tasks with proposals and specifications.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# 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:**
1. **STOP** - Do not start coding
2. **Create task** - `rulebook task create <task-id>`
3. **Plan** - Write proposal.md and tasks.md
4. **Spec** - Write spec deltas
5. **Validate** - `rulebook task validate <task-id>`
6. **THEN** - Start implementation
## Task Directory Structure
```
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
1. **Always create task first** - Document before implementing
2. **Keep tasks.md simple** - Only checklist items
3. **Put details in specs** - Technical requirements in spec files
4. **Validate before implementing** - Run `rulebook task validate`
5. **Archive when done** - Move completed tasks to archiveRelated Skills
rulebook-typescript
TypeScript development with strict mode, Vitest testing, ESLint linting, and CI/CD best practices. Use when working on TypeScript projects, writing tests, configuring linting, or setting up build pipelines.
rulebook-task-validate
Validate a Rulebook task format and structure against OpenSpec requirements. Use before archiving or to verify task quality.
rulebook-task-update
Update a Rulebook task status. Use to mark tasks as in-progress, completed, or blocked.
rulebook-task-show
Show complete details of a Rulebook task including proposal, checklist, design, and specs. Use to understand task requirements before implementation.
rulebook-task-list
List all Rulebook tasks with optional status filtering and archive inclusion. Use to check project tasks, progress, or find tasks by status.
rulebook-task-delete
Permanently delete a Rulebook task. Cannot be undone. Prefer archiving completed tasks instead.
rulebook-task-create
Create a new Rulebook task with standardized directory structure. Use when starting a new feature, breaking change, or architectural work that needs spec-driven planning.
rulebook-task-archive
Archive a completed Rulebook task to the archive directory with date prefix. Use after a task is fully implemented and validated.
rulebook-skill-validate
Validate the current skills configuration for conflicts, missing dependencies, and errors. Use to ensure skills are properly configured.
rulebook-skill-show
Show detailed information about a specific skill including metadata, content preview, and enabled status. Use to inspect a skill before enabling it.
rulebook-skill-search
Search for skills by name, description, or tags. Use to find skills matching specific requirements or technologies.
rulebook-skill-list
List all available Rulebook skills, optionally filtered by category or enabled status. Use to discover what skills are available for the project.