Rulebook Task Management

Automate spec-driven task creation, validation, and archiving with Rulebook commands.

15|2|Updated Oct 23, 2025

Search Tags:#workflow #validation #spec #OpenSpec #task-management #proposal

Ready to run

npx skills add https://github.com/hivellm/rulebook --skill rulebook-task-management

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Rulebook Task Management
Source: https://github.com/hivellm/rulebook/tree/main/templates/skills/core/rulebook
Command: npx skills add https://github.com/hivellm/rulebook --skill rulebook-task-management

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a formalized, spec-driven workflow for creating, validating, and archiving tasks before implementing features.

Core Features & Use Cases

Built-in, spec-driven task management for feature development and breaking changes.
Enforces a mandatory task creation step before any implementation and provides a clear directory structure (proposal.md, tasks.md, design.md, and specs/).
Supports end-to-end task lifecycle: create, validate, and archive tasks using Rulebook commands; MCP integration when enabled.
Useful for coordinating teams, documenting decisions, and maintaining traceable specs and implementation plans.

Quick Start

Use the rulebook task create <task-id> to start a new task. List tasks with rulebook task list. Inspect a task with rulebook task show <task-id>. Validate structure with rulebook task validate <task-id>. Archive a completed task with rulebook task archive <task-id>.

Frequently Asked Questions about Rulebook Task Management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I formalize feature proposals before implementation in a spec-driven workflow?▼

You can validate task structures by running the rulebook task validate command, which inspects the defined directory structure and ensures all required spec documents and proposals meet formalization requirements before implementation.

What's the best way to manage the lifecycle of breaking-change proposals and specs?▼

Managing breaking-change proposals is handled end-to-end through Rulebook commands: create to start, list to track, show to inspect, validate to check structure, and archive to close completed tasks, ensuring full traceability.

Do I need a specific directory structure to enforce task validation for feature development?▼

Yes, task validation requires a specific directory structure containing proposal.md, tasks.md, design.md, and a specs/ directory to ensure formalization requirements are met before implementation begins.

Does spec-driven task management work with MCP integration for team coordination?▼

Spec-driven task management supports MCP integration when enabled, allowing teams to coordinate feature development, document decisions, and maintain traceable implementation plans across the task lifecycle.

When should I not use a formalized spec-driven workflow for task creation?▼

You should avoid formalized spec-driven workflows for rapid prototyping or isolated minor fixes where the overhead of creating proposal.md and specs/ documents outweighs the need for traceable implementation plans.