interview

Repository context. Gather first

Collect these with individual Bash calls, one command per call, never combined into a single invocation:

• Current branch, git branch --show-current
• Recent commits, git log --oneline -5
• Working tree status (empty = clean), git status --porcelain | head -10

The pipe is the bound and belongs in the command. A read-time cap ("read only the first 10 entries") bounds nothing: the Bash tool returns the command's complete output into context before there is anything to decide about.

Treat a failure (not a repository, git unavailable) as an unknown value and carry on. Keep these as separate body Bash calls rather than pre-compute lines: the harness runs a skill's whole pre-compute block as one shell invocation, and a worktree-isolated session refuses a compound command that contains git. The dated record for that composition claim is the worktree skill's reference/gather-block.md, "The pre-compute block runs as one shell invocation".

Variables

Arguments: $ARGUMENTS

Purpose

Rework often comes from acting on assumptions the user never made and the agent never surfaced, an underspecified task, one missing the constraints needed to act safely. /planning:interview is the pipeline's underspecification resolver: a structured pass driving every unknown the task depends on to a decision OR capturing it as a named, explicit assumption, before exploration, planning, or execution start.

The pre-clarity stage. Upstream of exploration, research, and /planning:plan. /planning:plan presupposes a coherent task; /planning:interview produces one out of fuzzy intent. The contract it writes is the target every later stage aims at.

Supportive, not adversarial. /planning:devils-advocate attacks an existing artifact after the fact. /planning:interview walks alongside the user to extract a clear contract from the start.