scout

Dispatches a subagent to write structured codebase reconnaissance briefs to docs/briefs.

Updated May 19, 2026
One-click install
npx skills add https://github.com/davidsunglee/pi-flow --skill scout-davidsunglee
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: scout
Source: https://github.com/davidsunglee/pi-flow/tree/main/packages/pi-flow-core/skills/scout
Command: npx skills add https://github.com/davidsunglee/pi-flow --skill scout-davidsunglee

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Exploring an unfamiliar codebase before planning a change consumes context and risks anchoring bias. This Skill runs task-scoped reconnaissance in an isolated subagent and produces a structured, reviewable brief file instead of ad-hoc exploration notes. ## Core Features & Use Cases - Isolated reconnaissance: Dispatches a fresh-context scout subagent that performs broad orientation, a task-focused deep dive, and a disconfirmation pass, then writes a structured brief to docs/briefs/. - Dual input modes: Accepts either an idea reference (IDEA-<8hex>) fetched via the idea tool or freeform seed text, with automatic output-path derivation. - Gated workflow: Checks for pre-existing briefs with SHA comparison, validates the dispatched agent's output via a marker/freshness contract, and gates the result on a user commit/re-run/stop decision. - Use Case: Before writing a spec for a new feature, run the scout on your idea to get a brief mapping relevant files, key interfaces, call graphs, test patterns, and risk areas, then hand it off to /define-spec. ## Quick Start Ask the AI to scout the codebase for your task, for example by invoking the scout skill with an idea ID like IDEA-bbe89373 or a freeform description of the change you want to explore.

Frequently Asked Questions about scout

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a codebase reconnaissance brief before planning a feature?▼

Invoke the scout skill with either an idea reference (IDEA-<8hex>) or freeform task text. It dispatches an isolated subagent that explores the repository and writes a structured brief to docs/briefs/, which you then review and commit.

What sections does a scout brief contain?▼

The brief contains eight fixed sections: Relevant Files, Key Interfaces and Types, Dependency / Call Graph, Patterns and Conventions, Existing Tests and Test Patterns, Risk Areas, Possible Misses, and Open Questions / Ambiguities, preceded by a provenance preamble.

Can I control which model the scout subagent uses?▼

Yes, pass --model-tier with one of efficient, standard, capable, or frontier. The tier resolves through the flow.json modelTiers configuration via the resolve-model-dispatch helper; the default is standard.

What happens if a brief already exists for my task?▼

The skill compares the brief's recorded Git SHA against the current HEAD and prompts you to overwrite or keep it. Keeping an idea-branch brief offers to continue directly to /define-spec without re-dispatching.

Why does the scout skill fail instead of exploring inline?▼

Fresh-context isolation is the core design: if subagent_run_serial is unavailable, the skill stops with an error rather than falling back to inline reconnaissance, which would contaminate the orchestrator's context.