rulebook-task-validate
Validate a Rulebook task format and structure against OpenSpec requirements. Use before archiving or to verify task quality.
11 stars
byhivellm
Best use case
rulebook-task-validate is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Validate a Rulebook task format and structure against OpenSpec requirements. Use before archiving or to verify task quality.
Teams using rulebook-task-validate should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
$curl -o ~/.claude/skills/rulebook-task-validate/SKILL.md --create-dirs "https://raw.githubusercontent.com/hivellm/rulebook/main/skills/rulebook-task-validate/SKILL.md"
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/rulebook-task-validate/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How rulebook-task-validate Compares
| Feature / Agent | rulebook-task-validate | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Validate a Rulebook task format and structure against OpenSpec requirements. Use before archiving or to verify task quality.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# rulebook_task_validate
Validate a Rulebook task's format and structure.
## Input Schema
| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| `taskId` | string | Yes | Task ID to validate |
## Usage
```typescript
await mcp.rulebook_task_validate({ taskId: "add-auth-system" });
```
## Response
```json
{
"valid": true,
"errors": [],
"warnings": ["Consider adding more scenarios to specs/auth/spec.md"]
}
```
## Validation Rules
- `proposal.md` must exist with `## Why` section (min 20 characters)
- `tasks.md` must contain only checklist items
- Specs must use `SHALL` or `MUST` keywords
- Scenarios must use `####` headers (4 hashtags)
- Scenarios should follow Given/When/Then structure
## When to Use
- Before archiving a completed task
- After writing specs to verify format
- As a quality check during task planningRelated Skills
We are still matching the closest adjacent skills for this page. In the meantime, continue through the full directory.