plan-tick

You are ticking master-plan phases. Two modes:

• Auto mode (no <phase> arg) — detect the current branch, find the master plan matching it, audit each unticked phase against the working tree + branch diff, tick all phases the auditor verdicts ACHIEVED. Conservative — never ticks an UNCERTAIN or NOT_ACHIEVED phase.
• Manual override (<phase> arg supplied) — tick that one phase in the resolved plan without running the auditor.

Both modes are non-interactive. You must not call AskUserQuestion anywhere in this command. If something cannot be resolved deterministically, error with a clear message — never prompt.

Input: $ARGUMENTS

Parse arguments:

• First positional integer → manual override mode, target phase number.
• Second positional path (or first if first arg is a path) → explicit plan file.
• No args → auto mode.

---

Step 1 — Detect git context

Run a single bash block that captures:

git rev-parse --is-inside-work-tree || { echo "ERROR: not in a git repo"; exit 1; }
ROOT="$(git rev-parse --show-toplevel)"
BRANCH="$(git branch --show-current)"
# Base branch: try origin/HEAD symbolic-ref, fallback to main, then master
BASE="$(git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null | sed 's|^origin/||')"
[ -z "$BASE" ] && git rev-parse --verify --quiet origin/main >/dev/null && BASE=main
[ -z "$BASE" ] && git rev-parse --verify --quiet origin/master >/dev/null && BASE=master
[ -z "$BASE" ] && BASE=main
MERGE_BASE="$(git merge-base HEAD "$BASE" 2>/dev/null || git merge-base HEAD "origin/$BASE" 2>/dev/null)"
echo "ROOT=$ROOT"
echo "BRANCH=$BRANCH"
echo "BASE=$BASE"
echo "MERGE_BASE=$MERGE_BASE"

If not in a git repo, error: /planning-tools:plan-tick requires a git repository.

---

Step 2 — Resolve the plan path

If the user supplied an explicit path argument: validate the file exists; otherwise error with the path.

Else:

1. Discover candidate plans. Glob *.md under $ROOT/context/tickets/, $ROOT/docs/plans/, $ROOT/.claude/plans/master/. Filter to files containing ## Implementation Phases.
2. 0 candidates: error with the searched paths.
3. 1 candidate: use it.
4. 2+ candidates — branch-match selection:
   • Normalize the branch name: strip leading feature/, fix/, chore/, bugfix/, hotfix/; lowercase; replace _ and / with -.
   • For each candidate plan, normalize its basename: strip -PLAN.md or .md; lowercase; replace _ and / with -.
   • Find candidates whose normalized basename appears as a substring of the normalized branch name (case + separator insensitive).
   • 1 match: use it. Print: Auto-ticking against <path> (branch <BRANCH> matched).
   • 2+ matches: pick the most-recently-modified among the matches. Print: Auto-ticking against <path> (branch <BRANCH> matched ambiguously; picked most-recent).
   • 0 matches: fall back to the most-recently-modified plan across all candidates. Print: Auto-ticking against <path> (no branch match; picked most-recent).