create-working-branchlisted

## Quick Reference Rules: `GIT-01` (no trunk commits), `GIT-02` (required git preflight) Before: - [ ] Orchestrator provided `base`, `working_branch`, and `classification` - [ ] Orchestrator confirmed trunk freshness, user acknowledged stale trunk, or orchestrator recorded trunk-freshness: skipped - [ ] `base` branch exists locally or can be fetched - [ ] No uncommitted changes that make switching unsafe - [ ] `working_branch` name follows branch taxonomy After: - [ ] Current branch is `working_branch` - [ ] Branch created from or confirmed on `base` - [ ] Final action is a Bash tool call (exit 0 = succeeded, exit 1 = blocked) Create or confirm the working branch for the current approved plan. Follow `${CLAUDE_PLUGIN_ROOT}/governance/workflow.md`. ## Required Inputs The orchestrator resolves and passes these. The skill does not resolve them on its own. - `base`: base branch the working branch is created from (typically the resolved trunk; may differ for stacked work). - `working_branch`: requested working branch name (must follow branch taxonomy and naming rules). - `classification`: work classification (`feature|bugfix|hotfix|refactor|chore|docs|test|ci`). - `trunk-freshness`: resolved trunk freshness state from the orchestrator's preflight check per `${CLAUDE_PLUGIN_ROOT}/governance/workflow.md` (Trunk Freshness). One of: `fresh`, `stale (N behind)`, `stale (diverged — local N ahead)`, `stale (diverged — local M ahead, N behind)`, or `skipped`. Absent = skill exits