Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →seemseam/planner-closure-backfill
Produce one revision-fenced Planner backfill proposal for either a Detailer replan or task-set closure, with compact Frontdesk status evidence.
Passed 20 of 22 test cases with the skill, and 9 of 22 without it.
and 14 more in the full report
11 fixed9 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 11 test cases the skill fixed. Same model, same prompt, with and without the skill.
For a `task_set_closure` activation, the script supplied `closure_ref.path` as `./custom/relative/path/closure.json`. The user prompt suggests normalizing this to `custom/relative/path/closure.json`. What exact path string must be appended into `evidence_refs`?
| Checked | Without skill | With skill |
|---|---|---|
| The evidence_refs array copies the supplied closure_ref.path exact string without rewriting or normalizing it. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this output contract only when the controller activation mode is exactly
one of detailer_replan or task_set_closure. Initial intake remains owned by
planner-task-packet. Return one proposal for one activation; never combine
the two modes or substitute one mode for the other.
detailer_replanUse only the controller-provided task identity and task revision, expected PlanTree revision, closure evidence digest, accepted facts, and supplied Detailer/user macro-adjustment evidence. Copy those authority fields and evidence refs exactly; do not read or infer unsupplied state.
Preserve accepted facts. Then return a complete replacement macro proposal for
the task: it invalidates and replaces the old orchestration semantics rather
than continuing, replaying, or patching the prior orchestration bundle. Do not
lower acceptance criteria. The proposal mode must be exactly
detailer_replan; it must never masquerade as task_set_closure.
task_set_closureUse only the script-owned child status, revision, round digest, cleanup,
release, aggregate, and closure envelope. Preserve the task-set aggregate,
closure, and Frontdesk-status rules below. The proposal mode must be exactly
task_set_closure; do not treat a closure as a Detailer replacement proposal.
detailer_replan: validated Detailer macro-impact and user evidencetask_set_closure: validated child round, release, cleanup, aggregate,
and closure evidenceclosure_evidence_digest and ordered evidence refstask_set_closure: script-owned closure_ref with its canonical
project-relative closure pathtest cases passed, vs 9 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.