investigation

Create dated investigation folders with README documentation in scratch/.

3|Updated Dec 25, 2025
One-click install
npx skills add https://github.com/peabody124/reproducible_agent_environment --skill investigation-peabody124
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: investigation
Source: https://github.com/peabody124/reproducible_agent_environment/tree/main/skills/investigation
Command: npx skills add https://github.com/peabody124/reproducible_agent_environment --skill investigation-peabody124

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Skill scaffolds a structured investigation workspace in scratch/ for empirical research and documentation. It helps when you want to trace code paths, map data flows, document system architecture, investigate bugs, explore feasibility, or compare design options. Creates dated folder with README. NOT for simple code questions or single-file searches.

Core Features & Use Cases

  • Tracing: trace from X to Y, follow data flow, or identify what touches a component.
  • System Architecture Archaeology: create comprehensive architectural documentation with dated records.
  • Bug Investigation: reproduce issues, track root causes, and document findings.
  • Technical Exploration: test feasibility and gather experimental evidence.
  • Design Research: compare options and capture decisions with structured notes.
  • Note: Creates a dated folder in scratch/ with a README to capture task context and findings.

Quick Start

Create a folder in scratch/ with the format {YYYY-MM-DD}-{descriptive-name}: mkdir scratch/$(python -c "import datetime; print(datetime.date.today().isoformat())")-{descriptive-name} Create a README.md in this folder with: task description, background context, task checklist. Update with findings as you progress. Create scripts and data files as needed for empirical work. For complex investigations, split into sub-documents as patterns emerge.

Frequently Asked Questions about investigation

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

FAQPage Schema
How do I structure a code investigation to trace data flow and document findings?

Structure a code investigation by creating a dated folder in scratch/ with a README.md to capture task context, trace data flow, and document system architecture findings. This workspace supports adding scripts and data files as empirical research progresses.

What is the best way to document system architecture archaeology with dated records?

Document system architecture archaeology by generating a dated folder under scratch/ containing a README.md. This records comprehensive architectural context and findings, allowing you to map data flows and trace component interactions with structured notes.

How do I reproduce a bug and track its root cause with structured notes?

Reproduce a bug and track its root cause by initiating a structured bug investigation workspace in scratch/. The created README.md tracks the issue context, while scripts and sub-documents capture reproduction steps and root cause analysis findings.

Can I use this investigation workspace for simple single-file code searches?

This investigation workspace is not designed for simple single-file code searches or simple code questions. It scaffolds structured empirical research and traceability for complex tasks like mapping data flows, feasibility studies, and debugging investigations.

How do I create a dated folder for technical exploration and feasibility studies?

Create a dated folder for technical exploration by using the YYYY-MM-DD format combined with a descriptive name in scratch/. This workspace captures feasibility test context and experimental evidence in a README.md, supporting progressive documentation.

Does this approach support comparing design options with structured notes?

Yes, this approach supports comparing design options by capturing decisions with structured notes in a dedicated scratch/ folder. It allows you to document architectural tradeoffs, gather experimental evidence, and split research into sub-documents as patterns emerge.