Start ticket workflow

Issue number: $ARGUMENTS

Execute phases in order. Report completion after each phase.

Phase 1: Issue and worktree

1. gh issue view $ARGUMENTS — read title, body, labels, acceptance criteria
2. Ensure label in-progress exists; create if missing (gh label create in-progress ...). On permission error, stop.
3. gh issue edit $ARGUMENTS --add-label in-progress
4. Resolve main repo root (see git-worktree.md):

   COMMON=$(git rev-parse --git-common-dir)
   MAIN_ROOT=$(cd "$COMMON/.." && pwd)
   REPO=$(basename "$MAIN_ROOT")
   WORKTREES_ROOT="$(dirname "$MAIN_ROOT")/${REPO}-worktrees"

5. git fetch origin
6. Create or reuse worktree:

   BRANCH="feature/$ARGUMENTS"
   DIR=$(echo "$BRANCH" | tr '/' '-')
   mkdir -p "$WORKTREES_ROOT"
   git worktree add -b "$BRANCH" "${WORKTREES_ROOT}/${DIR}" origin/main 2>/dev/null || cd "${WORKTREES_ROOT}/${DIR}"
   cd "${WORKTREES_ROOT}/${DIR}"

7. All further edits run in this worktree.

Report: issue summary to the user.

Phase 2: Plan

1. Read relevant docs/ (docs/_inventory.md → area index → detail files). Use /spec-lookup for quick lookups.
2. Grep/Glob for affected code paths.
3. Present implementation plan; wait for user approval if scope is unclear.

Phase 3: Implement

1. Implement per plan and acceptance criteria.
2. Update docs in the same PR when behavior or SSOT changes.

Phase 4: Quality gates

Run only what exists in the repo:

• If lint/test scripts exist (package.json, Makefile, etc.), run them and report results.
• If none exist, skip and state "no lint/test toolchain configured" in the PR.

Phase 5: PR

1. Commit with explicit git add (no git add -A).
2. Push branch.
3. Open PR to main with body containing Fixes #$ARGUMENTS and template sections filled in.
4. gh pr create --base main ...

Report: PR URL.