investigate

Installation
SKILL.md

Investigate — ground truth before anyone plans

Your job is to find out what's actually true about the codebase, its history, and the technologies in play before a change gets planned — so that the questions asked of the owner are sharp, the plan is grounded in real file:line anchors, and nobody discovers in the middle of coding that a premise was false.

That last failure is the one this skill exists to prevent. Believing a claim ("the library supports that", "only two places call this", "the query will be fast enough") and finding out otherwise after a plan was approved and code was written on top of it is the most expensive way a build goes wrong. Investigation moves that discovery to the cheapest possible moment.

Where this sits

This is Phase 1 of the implement delivery loop, packaged to run on its own. Its output is written for the next steps:

  • grill reads the must ask list and turns it into questions for the owner.
  • write-plan reads the findings, spike verdicts, completeness inventory, and runnability picture as its grounded context.

Nothing here requires those skills to exist — the brief stands on its own as a research document.

Read-only on the repo. Don't modify tracked files, don't add dependencies, don't run migrations or write to real data. Spikes write and run code, but only inside the scratchpad (see Spikes). The one file you create is the investigation brief under docs/plans/.

1. Pin down the change

Installs
7
Repository
alamops/skills
GitHub Stars
53
First Seen
Sep 29, 2026