claude-plan

# claude-plan — independent plan from Claude's plan mode The host model planning its own work shares its own blind spots. A different-vendor model (Anthropic Claude, pinned to Fable) has a different training distribution, so where its plan diverges from yours is exactly where to dig. This skill runs the Claude Code CLI (`claude -p`) in Claude's **native plan mode** — read-only at the permission layer, with Claude's internal research-then-plan steering — and presents the plan **verbatim**. The consult is **stateless**: Claude cannot see the host session transcript. Everything it needs must travel in the decision brief. If you cannot write the brief, the question is not ready to be asked — that filter is a feature. ## When to use - Mid-execution, a design fork appears that the host should not settle unilaterally (irreversible structure, cross-module contract, risky migration). - A high-stakes decision needs a cross-vendor second plan before committing. ## When NOT to use - Routine planning: use the host's own plan tooling (Codex Plan mode, /think). - Planning known before the task starts: plan in a Claude session directly and hand off via a file-backed plan; do not call back mid-run. - Anything answerable by reading the repo for five minutes. Fable shares the main Claude quota pool — every consult is a full session. One consult per fork; do not iterate plans through repeated calls. ## Step 0 — Preflight (binary) ```bash command -v claude >/dev/null 2>&1 || { echo...