scouting-facts

Inspect code and documents to generate a Reconnaissance Report with citations.

Updated Aug 18, 2025
One-click install
npx skills add https://github.com/masa-codehub/gemini_agent --skill scouting-facts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scouting-facts
Source: https://github.com/masa-codehub/gemini_agent/tree/main/.gemini/skills/scouting-facts
Command: npx skills add https://github.com/masa-codehub/gemini_agent --skill scouting-facts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Systematically investigates the current state of code and documents to gather objective facts, and outputs a factual Reconnaissance Report without interpretation or proposals.

Core Features & Use Cases

  • Objective facts collection: Actively inspects code and docs to compile verifiable evidence.
  • Evidence-driven reporting: Generates a Reconnaissance Report template with citations to exact file paths and lines.
  • Handoff readiness: Provides an audit-ready artifact for downstream analysis (analyzing-intent).

Quick Start

Ask the Scout to begin a facts-first survey of the repository and generate the Reconnaissance Report using the provided templates.

Frequently Asked Questions about scouting-facts

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

FAQPage Schema
How do I collect objective facts from a codebase for an audit or handoff?

To collect objective facts for an audit, systematically inspect code and documents to gather verifiable evidence. This process generates a factual Reconnaissance Report with citations to exact file paths and lines, providing an audit-ready artifact without interpretation.

What is a Reconnaissance Report and how does it help with baseline verification?

A Reconnaissance Report is a formal document that compiles objective facts and verifiable evidence about a codebase. It helps with baseline verification by providing exact file path and line citations, ensuring downstream analysis relies on auditable, interpretation-free data.

How do I document the current state of a software project without adding subjective interpretation?

Document the current state of a software project without subjective interpretation by applying a facts-first survey. This method actively inspects code and documents to output a formal Reconnaissance Report, strictly reporting verifiable evidence with exact citations.

Does generating an evidence-driven report work for software project handoffs?

Generating an evidence-driven report works effectively for software project handoffs. It systematically investigates code and documents to compile verifiable evidence, producing an audit-ready Reconnaissance Report that ensures downstream teams receive verified, objective facts.

What is the best way to gather verifiable evidence from code and documents for downstream analysis?

The best way to gather verifiable evidence for downstream analysis is to conduct a deterministic workflow survey. This approach identifies objective facts across the codebase and documents, outputting a formal Reconnaissance Report with exact citations to support further analysis.