plan-readiness-review
Review planner task packets for readiness without rewriting authoritative task state.
git clone --depth 1 https://github.com/SeemSeam/claude_codex_bridge /tmp/plan-readiness-review && cp -r /tmp/plan-readiness-review/docs/plantree/plans/agentic-loop-workflow/drafts/agentroles.ccb_plan_reviewer/skills/plan-readiness-review ~/.claude/skills/plan-readiness-reviewSKILL.md
# Plan Readiness Review Use this skill when a planner artifact needs an independent quality gate before execution or clarification. ## Inputs - task packet - readiness recommendation - candidate questions - acceptance and verification contract - prior round evidence if replanning ## Output Return a planner review with one decision: - `approve` - `needs_revision` - `needs_clarification` - `blocked` ## Required Checks - scope and non-goals are explicit; - acceptance criteria are observable; - verification can be executed or reviewed; - unresolved risks are named; - no hidden fallback or degradation is accepted; - current-phase user questions are separated from deferrable questions.
Maintain this CCB project's GitHub-facing release and npm publication surface. Use when preparing, publishing, auditing, or fixing CCB releases; updating README.md, README/zh.md, localized README files, CHANGELOG.md, VERSION, package.json, GitHub release notes/assets, repository description/topics, npm registry state, or GitHub Actions release/test status.
Private built-in CCB configuration skill for agentroles.ccb_self. Design, edit, validate, and prepare reloads for .ccb/ccb.config, role bindings, providers, windows, workspaces, tool windows, sidebar, and provider startup inputs. Use only inside ccb_self; non-self agents should delegate CCB config changes to ccb_self.
Diagnose and repair CCB ask/job/message/reply/artifact/callback lineage. Use for missing replies, incomplete artifacts, pending callbacks, retry/resubmit/ack decisions, reply delivery problems, or work-chain resume advice.
Diagnose CCB runtime, mounted daemon graph, tmux namespace and panes, provider context, queue/inbox/trace, replies/artifacts, config drift, and storage boundaries. Use when the user asks what is broken, which agent is stuck, whether CCB is mounted, why a reply did not arrive, or what to check first.
Recover CCB agents, panes, mounts, provider contexts, API/provider failures, config reload aftermath, clear operations, and guarded single-agent restarts. Use when the user asks to fix, recover, restart if safe, clear context, reload, remount, or keep work going after provider/API failure.
Send a request to a CCB agent with `ask`.
Clear CCB managed agent conversation context with `ccb clear`. Use when the user writes `$ccb-clear`, `$ccb_clear`, or asks to clear/reset one or more CCB agent contexts without restarting or deleting project state.