Stats
Actions
Tags
From rulebook
Validates Rulebook task format and structure against OpenSpec requirements, checking proposal.md, tasks.md, specs with SHALL/MUST, and Given/When/Then scenarios. Use before archiving or for quality checks.
How this skill is triggered — by the user, by Claude, or both
Slash command
/rulebook:rulebook-task-validateThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Validate a Rulebook task's format and structure.
Validate a Rulebook task's format and structure.
| Parameter | Type | Required | Description |
|---|---|---|---|
taskId | string | Yes | Task ID to validate |
await mcp.rulebook_task_validate({ taskId: "add-auth-system" });
{
"valid": true,
"errors": [],
"warnings": ["Consider adding more scenarios to specs/auth/spec.md"]
}
proposal.md must exist with ## Why section (min 20 characters)tasks.md must contain only checklist itemsSHALL or MUST keywords#### headers (4 hashtags)npx claudepluginhub hivellm/rulebook --plugin rulebookEnforces 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.
Reviews task-mapping.md and tasks.md for gaps in vertical slice completeness, TDD structure, story coverage, dependencies, and traceability; generates classified issues.
Runs 3-agent verification loop on complete task lists to ensure PRD coverage, architecture adherence, and design system compliance before implementation.