flow-start git:20261023.652c011A

Immutable. This exact content never changes and is served at /api/v1/blob/9c7fdbe4493a7d7c.

---
name: "flow-start"
description: "Flow: Start Working on an Issue - Create a worktree and branch for a GitHub issue. Stateless - all context from git and GitHub."
---
<!-- GENERATED by claude-power-pack - scripts/codex-skill-sync.py; edit .claude/commands/flow/start.md instead -->

## Codex harness adaptations

Generated from a Claude Code command. Where the procedure references these Claude-only surfaces, adapt as follows:

- Native worktrees (`EnterWorktree`/`ExitWorktree` tool calls, `.claude/worktrees/` paths): use plain git instead, with the worktree as a VISIBLE SIBLING of the repo - `git worktree add ../<repo>-<branch> -b <branch>` (or `$FLOW_WORKTREE_BASE/<repo>-<branch>` when that env var is set), work inside it, then `git worktree remove ../<repo>-<branch>` when done.
- Helper scripts are bundled under `scripts/` in this skill directory (byte-identical copies from the claude-power-pack checkout). Commands run them as `"${CPP_SKILL_DIR:-/dev/null}"/scripts/<name>`: `CPP_SKILL_DIR` is the absolute directory containing THIS SKILL.md - the location the skills catalog gives, with any alias such as `r0` expanded. A shell resolves a bare `scripts/<name>` against your working directory (the target project), never this skill, so substitute that directory, or set it in the same command (`CPP_SKILL_DIR=/abs/skill/dir; ...`) - each command is a fresh shell. "Not a directory" on `/dev/null/scripts/<name>` (exit 126, or 127 in some shells) means `CPP_SKILL_DIR` is unset: set it and re-run; never run the target project's own `scripts/<name>` in its place. Read every "exit 127" fallback in this skill as "exit 127, or 126 Not a directory": set the variable and re-run before falling back. A helper whose verdict gates a step and that prints no verdict line after the whole fallback chain did not run - for the finish gate, no `FLOW_FINISH_GATE:` verdict line: STOP, never read it as skipped, never commit on it (issue #1547). A bare `scripts/<name>` inside a command is a CPP-checkout operation that the text says so about; in prose, `scripts/<name>` NAMES the bundled helper. Some helpers expect sibling repo resources, so prefer a full checkout when one is available.
- Network: this skill's bundled helpers appear to call the network (`gh`, `git fetch`/`push`, `curl`, `aws`, HTTP). Codex's workspace sandbox has no network, and an allow rule for `gh` covers only a top-level `gh` command, never one a helper runs. Run these helpers with escalated permissions. From inside the sandbox, "error connecting to api.github.com" means no network, not a GitHub outage or a bad login.

# Flow: Start Working on an Issue

Create a worktree and branch for a GitHub issue. Stateless - all context from git and GitHub.

## Full procedure

Read `reference.md` in this skill directory for the complete, authoritative procedure before acting on this skill.