featurelisted

<codex_skill_must> 1. Phase 2 is gated on `permission_mode='plan'`; if not plan, stop and ask the user to run `/plan`. 2. Run `mkdir -p` and `git worktree add -b feat/<name> ... main` as separate `exec_command` calls. 3. Submit plans only inside `<proposed_plan>...</proposed_plan>`. 4. After `<proposed_plan>`, stop until plan-review approval; ordinary chat approval is not implementation approval. 5. After approval, write `.feature-plan-path` before implementation. 6. Allowed tools: `exec_command`, `request_user_input`, `spawn_agent`, `wait_agent`, `update_plan`, `apply_patch`; every `spawn_agent` needs `wait_agent`. </codex_skill_must> Start a new feature in an isolated git worktree. Feature description: $ARGUMENTS ## Instructions Follow these phases in order. Each phase has a gate — do not proceed until the gate is satisfied. Before every action, identify the current phase and check its gate. If a gate is not satisfied, stop instead of falling back. If you violate phase order, halt and report the violated gate. --- ### Phase 1: Setup 1. Derive a short kebab-case name from the description 2. Derive the app name from the git repo: `basename $(git rev-parse --show-toplevel)` 3. Switch to main: `git checkout main` 4. Pull latest: `git pull origin main` 5. Create branch `feat/<name>` and worktree `../worktrees/<app>/<name>` from main. Run **two separate `exec_command` tool calls** — do not chain them with `&&`. The dashboard's PostToolUse hook only stamps `worktree_cwd` +