stack-plan-style

## What It Does Defines how `gt-stack-plan` should present a proposed stack of branches to the user for confirmation: a base-to-tip visual tree with per-branch intent, commit type, and dependency notes. ## When to Use - `gt-stack-plan` Phase 2, Step 2 ("Present the Stack Plan"), before asking the user to confirm, adjust, or cancel. ## Usage Use this style for Graphite planning and submit workflows. - Present the stack from base to tip. - For each branch, include intent, likely commit type, and dependency notes. - Flag where a branch should stay single-commit and where `gt modify --commit` is justified. - End with the recommended next step: on Claude Code, the `flow:work` skill with `<path>` to execute the stack. On Codex, `flow:work` is not exposed — recommend executing the stack decomposition manually, submitting each branch with `gt submit --no-interactive`. For standalone changes (no stack), recommend `gt submit --no-interactive` directly on either host. - Keep the output easy to scan during implementation. - When saving decomposition to a plan file, use the structured format defined by the `stack-decomposition-format` skill for the `## Stack Decomposition` section. The visual tree format here is for confirmation display; the structured format is the machine-readable contract consumed by `flow:work`.