Grounding Before Coding

by riekelte67b7af9ac74No license5 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 3 weeks ago

Use when starting any non-trivial change, investigating a bug, or working in unfamiliar code - before the first line is written. Also use for pure investigation with no change planned yet - "dig into this", "figure out why", "sometimes the export is empty", intermittent errors after a deploy. Encodes the ground-first discipline: map the real code and data, quote evidence, never guess conventions. Use whenever a change or a conclusion is about to be built from belief instead of from the tree, even under time pressure.

Instructions onlySoftware Development
  1. e67b7af9ac74Currentcommit e67b7afPublished Oct 8, 2026

Source and attribution

Source:riekelt/principal-engineerinplugins/principal-engineer/skills/grounding-before-codingat commite67b7af

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal