/scout commands

The /scout command drives Teamtrail from your agent's chat.

teamtrail connect claude installs it as .claude/commands/scout.md in the repo. teamtrail connect codex installs it as a Codex prompt (~/.codex/prompts/scout.md), used as /prompts:scout …. With no arguments, it runs status.

Command	Does
`/scout new "<idea>"`	Frames the idea with you, charts a trail, does discovery, then works it.
`/scout resume [trail]`	Picks up the trail and works ready tickets until none is ready.
`/scout status`	Progress, running sessions, what's waiting on you and what interrupts, blocked and rework tickets, spend.
`/scout inbox`	The ranked Waiting on you list. Answer questions in the chat; everything else is decided in the Lookout.

#new ""

Checks the work is trail-sized; a bug fix or a single endpoint is done directly, unless you ask for a trail.
Asks 3–4 framing questions, one at a time (ask_human with framing: true): who it's for, what done looks like, what's out of scope, what's decided.
Drafts the map: destination, decided, not yet specified, out of scope, assumptions and tickets wired with blockedBy, then calls start_trail.
Does discovery and calls submit_brief; continues once you accept it.

#resume [trail]

For each ticket, the agent:

declares the files it will change (touches) and works in its workspace when it gets one;
reads the knowledge that came with the claim, and proposes or flags knowledge;
agrees on acceptance criteria (set_criteria) before implementation work;
asks you only calls that are yours (by your risk policy), with honest urgency, and decides and records the rest;
challenges assumptions and proposes reroutes instead of working around them;
closes with a resolution, rationale, alternatives and evidence per criterion, and handles rework or blocked results.

#In Codex

text

/prompts:scout new "<idea>"
/prompts:scout resume
/prompts:scout status
/prompts:scout inbox