planner-closure-backfill

Generates revision-fenced Planner backfill proposals for Detailer replans or task-set closures.

3.5k|342|Updated Oct 25, 2025
One-click install
npx skills add https://github.com/bfly123/claude_code_bridge --skill planner-closure-backfill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: planner-closure-backfill
Source: https://github.com/bfly123/claude_code_bridge/tree/main/docs/plantree/plans/agentic-loop-workflow/drafts/agentroles.ccb_planner/skills/planner-closure-backfill
Command: npx skills add https://github.com/bfly123/claude_code_bridge --skill planner-closure-backfill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a PlanTree workflow reaches a Detailer replan or a task-set closure, the Planner must emit a single, strictly structured backfill proposal that copies controller-owned revisions, digests, and evidence refs exactly, without performing any side effects. This Skill enforces that output contract so proposals validate cleanly on import.

Core Features & Use Cases

  • Dual activation modes: Produces exactly one proposal for either detailer_replan or task_set_closure, never mixing or substituting modes.
  • Authority-preserving output: Copies expected PlanTree revision, task identity, closure evidence digest, and ordered evidence refs byte-for-byte, and maps aggregate results (pass, partial, replan_required, blocked) to the correct closure result.
  • Embedded Frontdesk status: Embeds one complete ccb.planner.frontdesk_status.v1 object with a factual user-facing report.
  • Use Case: A controller activates the Planner with validated child round and closure evidence for a finished task set; the Skill returns a task_set_closure proposal JSON that the host validates and imports, with no shell commands, file reads, or notifications issued from the reply.

Quick Start

Ask the Planner to produce a task_set_closure backfill proposal using the controller-supplied revisions, closure evidence digest, and ordered evidence refs.

Frequently Asked Questions about planner-closure-backfill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a Planner backfill proposal for a task-set closure?

Activate the Skill in task_set_closure mode with the controller-supplied expected PlanTree revision, task-set identity, closure evidence digest, and ordered evidence refs. It returns one ccb.planner.backfill_proposal.v1 JSON with the aggregate result mapped to the closure result and an embedded frontdesk_status object.

What is the difference between detailer_replan and task_set_closure modes?

detailer_replan produces a complete replacement macro proposal for one task using Detailer or user macro-adjustment evidence, invalidating the old orchestration bundle. task_set_closure preserves script-owned child status, aggregate, and closure semantics for a finished task set. The two modes must never be combined or substituted.

Can the Planner backfill proposal run shell commands or write files?

No. The reply-only surface forbids shell commands, file reads or writes, tests, CCB commands, and Frontdesk notifications. The host validates and imports the proposal and owns every side effect.

How are aggregate results mapped in a closure proposal?

The mapping is pass to closure_complete, partial to closure_partial, replan_required to task_set_replanned, and blocked to closure_blocked. A pass requires empty unresolved, blocker, and replan fields, while every non-pass result requires non-empty unresolved_scope.

What happens when the expected PlanTree revision is stale?

The Skill never overwrites a newer PlanTree revision or repairs a stale digest in prose. It returns revision_conflict and reports the supplied current revision as a blocker.