Help us improve
Share bugs, ideas, or general feedback.
From rulebook
Creates a new Rulebook task directory with standardized structure: proposal.md, tasks.md, design.md, and specs. Use for new features, breaking changes, or architectural planning.
npx claudepluginhub hivellm/rulebook --plugin rulebookHow this skill is triggered — by the user, by Claude, or both
Slash command
/rulebook:rulebook-task-createThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Create a new Rulebook task with full directory structure.
Enforces spec-driven task management for new features, breaking changes, and project work using OpenSpec format. Provides CLI commands for task creation, listing, validation, and archiving with mandatory proposal, checklist, and spec workflows.
Creates task specifications via codebase analysis, interactive clarifying questions on scope/constraints/edge cases, feature splitting checks, and agent delegation setup.
Creates tasks or sections in TASKS.md to track project work. Auto-triggers on phrases like 'add a task', 'todo', 'let's plan', or untracked future work.
Share bugs, ideas, or general feedback.
Create a new Rulebook task with full directory structure.
| Parameter | Type | Required | Description |
|---|---|---|---|
taskId | string | Yes | Task ID in kebab-case (e.g., add-auth-system) |
await mcp.rulebook_task_create({ taskId: "add-auth-system" });
{
"success": true,
"taskId": "add-auth-system",
"message": "Task add-auth-system created successfully"
}
rulebook/tasks/add-auth-system/
├── .metadata.json # Status: pending
├── proposal.md # Why + What Changes + Impact
├── tasks.md # Simple checklist items only
├── design.md # Technical design (optional)
└── specs/
└── <module>/
└── spec.md # SHALL/MUST requirements