Grounding before coding
REQUIRED BACKGROUND:
the
principal-engineering
skill.
Overview
Before writing a spec, a fix, or a first line: map the real code and data. Quote
file:line
and run the query behind every number you rely on. The cost of grounding is minutes; the cost of building on a wrong belief is the whole change plus the incident it causes.
The discipline
Read the implementations, not the names.
A method called
validate
that does not validate is common enough to be the default assumption. Verify what a thing does before building on what it is called.
Quote your evidence.
Every load-bearing claim in your plan gets a
file:line
, an exact query result, or a command output. When you cannot back a claim, say so out loud instead of assuming it.
Never guess conventions.
How this repo names things, wires dependencies, handles errors, or runs tests is discoverable in minutes. Guessing conventions is how changes arrive that are correct in isolation and wrong in the codebase.
Trust code, not status.
A document's or ticket's self-reported state is not evidence of execution state; adjudicate with the code and the history (
git log -S
grounding-before-coding
安装
npx skills add https://github.com/riekelt/principal-engineer --skill grounding-before-coding