Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →seemseam/planner-task-packet
Draft CCB workflow task packets, readiness recommendations, and candidate clarification questions without mutating authoritative state.
Passed 20 of 21 test cases with the skill, and 11 of 21 without it.
and 11 more in the full report
10 fixed11 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are processing a task with route context needs_detail. An activation contains a verified stop structure with schema_version set to 1, status set to detail_ready, basis set to verified_detail_ready_stop_contract, valid task and state versions, SHA-256 digests, and matching required_reason. Produce the corresponding readiness json payload.
| Checked | Without skill | With skill |
|---|---|---|
| The readiness field is set to ready. | Missed | Passed |
| The route field is set to needs_detail. | Missed | Passed |
| The status_recommendation field is set to detail_ready. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill when converting macro user intent or a frontdesk request into a plan artifact for review.
Produce these exact reply-visible sections. Do not replace them with prose, tables, alternate headings, or "equivalent" sections.
Do not run shell commands, file searches, file reads, tests, builds, or CCB commands before replying. Use only the intake evidence and compact artifacts provided in the prompt.
task-packet.mdreadiness.jsontask-set.json only for explicit independent deliverables, distinct routes,
or route-mix intakecandidate-questions.jsonl when user input may be neededFor single-slice work, use fenced blocks with these exact labels:
**task-packet.md**
```markdown
# Task: <title>
Route: <direct_execution|needs_detail|macro_adjustment_request|blocked|partial_completion>
## Goal
<complete product outcome>
## Acceptance Criteria
- <observable behavior; preserve every intake requirement>
## Interface Contracts
- <concrete module/import path, callable/signature, CLI, data/error shape, or None declared>
test cases passed, vs 11 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.