cornerman-where-am-i

/cornerman where-am-i

Read-only. One screen of "where does this work stand" for an issue. Pairs with /cornerman resume (#22) — where-am-i is the fast snapshot, resume is the full reasoning + diff-against-main.

Args

Flag	Default	What it does
--issue <N>	auto-detect	Filter to a specific issue. Auto-detects from branch when omitted.

Branch auto-detection

Looks at the current branch name and extracts the first numeric run that looks like an issue number:

feat/issue-211-foo      → 211
feat/211-foo            → 211
something-211           → 211
chore/docs-lowercase    → no match → asks for --issue explicitly

If detection fails, the report explains how to fix it.

How

python3 .claude/plugins/cornerman/scripts/where-am-i/report.py \
  ${ISSUE:+--issue "$ISSUE"}

Reads .claude/loop-events.jsonl, .claude/runs/*/manifest.json, and .claude/incidents/*/timeout.json. Filters to events / manifests / incidents tagged with this issue (or whose run_id appears in this issue's event stream).

Output sections

1. Branch + head SHA + behind-origin/main — git state at the moment of the call
2. Current tracker status — last state_transition event's target status
3. Last 5 events — most recent telemetry tagged to this issue
4. Latest run manifest — most recent .claude/runs/<run_id>/manifest.json whose inputs.issue == N
5. Last contract result per transition — per-transition latest pass/fail
6. Watchdog incidents — timeouts recorded for runs that touched this issue (omitted when none)
7. Suggested next step — best-effort heuristic naming the most-likely next agent (/architect <N>, /pr-reviewer <pr>, etc.) based on the last end outcome

Empty-state behavior

When no events are tagged to the issue (typical for issues that haven't been touched by an agent yet), the report says so explicitly. Doesn't print sections with placeholder values.

What this is NOT

• /cornerman resume (Phase 2 #22) — that's the heavier skill that also reasons about "what changed in main since work started", "which contract gates still pass", and "what needs re-running." where-am-i is the cheap snapshot
• /cornerman retro (#13) — retro is cross-issue, time-windowed. where-am-i is single-issue, point-in-time
• A linter — surfaces facts, doesn't judge them. The "suggested next step" is a guess; the human can override

Pairs with

• /cornerman retro (#13) — when you want the global view instead of single-issue
• /cornerman resume (#22) — when you need to reason about what's still valid
• Loop telemetry (#5), contracts (#4), watchdog (#6), run manifests (#11) — the substrate this consumes