Big Plan

Planning-only skill. Explore the codebase, propose a breakdown, save a plan log to $HOME/cclogs/{slug}/, get a second opinion (codex, with an automatic Opus fallback), create GitHub issues, verify nothing was lost, and hand off to /x-wt-teams in a fresh session.

On Claude Code on the web ($CLAUDE_CODE_REMOTE=true): follow web/web-mode.md. Create/edit the epic + sub-issues via the GitHub MCP (issue_write, sub_issue_write), not gh, and pre-create the epic/sub labels (no create-label MCP tool). The default Codex Step-5 plan reviewer is unavailable — use a Claude reviewer (e.g. /opus-2nd) in its place. Plan logs land in the ephemeral /tmp cclogs stub — Step 11 posts the final plan log as an epic-issue comment so it survives the container; persist anything else important into the epic issue body. The /x-wt-teams / /x-as-pr it auto-invokes runs subagents-only (no agent teams). Branch model — see web-mode.md §5: at runtime the claude/* session branch IS the base ($WEB_BASE); there is no base/{slug} in this session, parent = the fork-from branch ($WEB_PARENT, today the repo default). The Step 6 proposal and the Step 11 pause checks follow that — the session branch being non-main is normal, not a nested-base warning, and is NOT a pause condition. Issue bodies are the opposite: they outlive this session and are usually implemented by a fresh session (terminal or another web container) for which this session's claude/* name is a stale, meaningless ref — write them portable, exactly like a terminal plan (base = base/{impl-title-slug}, parent = the resolved $WEB_PARENT literal, e.g. main), never the session-branch name (resource-handoff exception — web-mode.md §5). Persist every artifact worth keeping to GitHub before the session ends (plan log → epic comment at Step 11; implementer-needed files → _temp-resource/ commit) — local storage is the ephemeral /tmp stub and dies with the container. Super-epic bundling is unsupported on web (web-mode.md §5 — it needs real base/<super> / base/<super>-<epic> branches, neither claude/-prefixed nor the session branch). A -is sweep on web does NOT create a super-epic: it degrades — plan every handled issue as a standalone epic and print the per-epic hand-off with a loud note that they must be run from a terminal session. Degrade, never refuse: a triaged sweep must not be thrown away.

In a limited verification env (Claude Code web) the implementation session's final visual / Mac-only check can't run. /big-plan is planning-only, so the actual mac-label handoff fires downstream in the /x-as-pr / /x-wt-teams it invokes (they receive -m / -v and own it) — see web/mac-handoff.md. /big-plan's only jobs here: seed the mac label in the label bootstrap (Step "Bootstrap labels") so it exists for the downstream skill, do not add a Step 11 pause for this, and let the -m cleanup tail keep mac-deferred issues open.

This skill is useful for almost every implementation task, not just huge ones. It captures intent, breaks work into reviewable units, and creates a paper trail that survives context compression.

Input Parsing

Parse $ARGUMENTS to extract: