OpenParable
Skip to content
← Back to skills

Rulebook Task Management

Productivity
rulebook-task-management

Rulebook Task Management is an Agent Skill for productivity published in the majiayu000/claude-skill-registry repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/majiayu000/claude-skill-registry/blob/HEAD/skills/data/rulebook-task-management/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/rulebook-task-management, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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

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 archive