cvg-plan-loop

Plan Loop

Use this skill for plan-only cvg-multi-session orchestration.

Before doing anything, open and read references/cvg-multi-session-protocol.md, then apply the protocol gates from cvg-multi-session:

• transport binding gate,
• real specialist session gate,
• orchestrator callback transport gate,
• waiting handoff gate,
• cvg-plan-review-feedback gate,
• fresh-reviewer exit gate.

Do not implement product code in this workflow.

Phase 0: Orchestrator Setup

Record:

• current orchestrator session id (Codex thread id; on Claude Code the harness tracks it),
• worktree or repo path,
• current git rev-parse HEAD if available,
• dirty worktree state,
• source prompt or input document,
• expected plan path or target docs directory when known,
• the loop ledger path, created per the Gate 5 loop-ledger rule.

Classify dirty files:

• plan-owned files,
• unrelated user artifacts,
• files the planner must not touch.

Phase 1: Planner Handoff

Spawn the planner as a real specialist session (Gate 0 spawn operation) and record the id returned by the tool. Verify it per Gate 1; if it is not verifiable, do not continue.

Planner prompt must include:

• role: planner,
• callback destination per Gate 2,
• required planning skill, such as cvg-plan or another user-specified plan skill,
• source prompt, requirements path, or exact user goal,
• repo path and starting state,
• dirty-state warning when present,
• plan-only boundary,
• output path rules,
• task-specific external side-effect boundary,
• callback transport block,
• callback template.

Do not restate the planning skill's process or paste broad repo rules, likely files, or local policy summaries unless they are the user's source authority.

Planner callback template:

I am the planner. My specialist id is <planner-id>. This planning round is complete. Plan path: <absolute path>. Key status: <brief>. Please decide the next step.

Complete the waiting handoff per Gate 3 and end the active turn.