scout

Map a codebase slice and produce a scout report of touchpoints and risks.

5|Updated Apr 29, 2026
One-click install
npx skills add https://github.com/friedbotstudio/baseline --skill scout-friedbotstudio
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scout
Source: https://github.com/friedbotstudio/baseline/tree/main/.claude/skills/scout
Command: npx skills add https://github.com/friedbotstudio/baseline --skill scout-friedbotstudio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you rapidly identify the exact slice of a codebase that matters for a task, so you can understand scope, constraints, and affected paths before making changes.

Core Features & Use Cases

  • Targeted codebase mapping: Finds the primary files, modules, and patterns related to a feature or bug.
  • Entry point discovery: Locates routes, commands, jobs, or other triggers that reach the relevant code.
  • Test and constraint inventory: Surfaces existing tests, configuration dependencies, and co-change risks that shape implementation work.
  • Use case: A developer wants to add or change behavior in one area and needs a concise report of what is touched, what is coupled, and what may break.

Quick Start

Ask the scout skill to map the relevant slice of the codebase for your task and write the report to docs/scout/<slug>.md.

Frequently Asked Questions about scout

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

FAQPage Schema
How do I map codebase scope and identify affected files before making changes?

Codebase scope mapping identifies the exact files, modules, and patterns constraining a task to understand impact and affected paths. It captures touchpoints, entry points, existing tests, and co-change risks before implementation begins.

What is impact analysis and how does it find entry points in a codebase?

Impact analysis traces routes, commands, and job triggers reaching relevant code to locate primary entry points. It discovers execution paths and configuration dependencies that shape implementation work and constrain feature behavior.

How do I inventory existing tests and dependencies for a specific feature?

Test and constraint inventorying surfaces existing tests, configuration dependencies, and co-change risks related to a feature. It captures patterns and coupled modules to reveal what may break during implementation.

Can I use codebase scouting for feature discovery in large software projects?

Codebase scouting applies to feature discovery in large software projects by mapping relevant code slices and capturing constraints. It produces a scoped report with touchpoints, risks, and co-changes while respecting workflow prerequisites.

What is the best way to document codebase constraints and touchpoints for a task?

Documenting codebase constraints involves generating a scoped report mapping touchpoints, entry points, existing tests, and risks. The report captures coupled files and patterns that constrain the task, writing output to a designated markdown file.