SkillsAdd

smithery/hivellm

Rulebook Task Management

Spec-driven task management for features and breaking changes with OpenSpec-compatible format

Installation

$ npx skills add smithery/hivellm --skill rulebook-task-management
View on skills.sh ↗ Website ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

memory-management Similar name
anthropics/knowledge-work-plugins

Two-tier memory system that makes Claude a true workplace collaborator. Decodes shorthand, acro…

7K installs
task-management Similar name
anthropics/knowledge-work-plugins

Simple task management using a shared TASKS.md file. Reference this when the user asks about th…

6.8K installs
aws-billing-and-cost-management Similar name
aws/agent-toolkit-for-aws

Analyze AWS costs, find savings, manage budgets, evaluate Savings Plans and Reserved Instances,…

6.6K installs
source-management Similar name
anthropics/knowledge-work-plugins

Manages connected MCP sources for enterprise search. Detects available sources, guides users to…

4.8K installs
close-management Similar name
anthropics/knowledge-work-plugins

Manage the month-end close process with task sequencing, dependencies, and status tracking. Use…

2.7K installs
flutter-state-management Similar name
flutter/agent-plugins

Manage state in your Flutter application

1.1K installs
More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0.0

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,816 B
  • docs SUMMARY.md 125 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Rulebook Task Management

Use Rulebook's task system for spec-driven development. Create a task BEFORE implementing any feature, breaking change, architecture change, or performance/security work. Skip it for bug fixes, typos, and non-breaking dependency updates.

Workflow

  1. Create the task: rulebook task create <task-id> (or rulebook_task via MCP)
  2. Write proposal.md, tasks.md, and spec deltas
  3. Validate: rulebook task validate <task-id>
  4. Implement, checking off tasks.md items in order
  5. Archive when done: rulebook task archive <task-id>

Prefer the MCP tools (rulebook_task/list/show/validate/archive) when the MCP server is enabled. Never create task directories by hand.

Structure

.rulebook/tasks/<task-id>/
├── proposal.md         # Why and what changes
├── tasks.md            # Checklist only — no explanations
├── design.md           # Technical design (optional)
└── specs/<module>/spec.md

Formats

proposal.md: ## Why + ## What Changes + ## Impact (affected specs/code, breaking Y/N).

tasks.md: numbered phases with - [ ] 1.1 <simple item> entries only.

Spec deltas (specs/<module>/spec.md):

## ADDED Requirements

### Requirement: <Name>
The system SHALL <do something>.

#### Scenario: <Name>
Given <context>
When <action>
Then <expected result>

Use ## ADDED / ## MODIFIED / ## REMOVED headers; scenarios use 4 hashtags.

See .rulebook/specs/rulebook.md for the full format reference.