design-rationale

Installation
SKILL.md

Design rationale

Leading words: code is not intent, coverage map, Direct Supported Inferred Speculative Unknown.

Companion to subsystem-walkthrough. That skill is runtime. This one is the forces that produced the shape.

Copy these steps into the todo list verbatim. Skip with skip: <reason>.

  1. Parse the target and the question. If vague, state your guess and proceed.
  2. Code-anchor: paths, symbols, git blame / git log --follow, PR numbers, gh pr view when gh exists.
  3. Coverage map of seven categories. Spawn one investigator per category that exists. Document the null; do not skip the search silently.
  4. Synthesize with references/epistemics.md. Keep confidence language intact.
  5. Present. If this investigation precedes a change, add Preserve / Change / Avoid / Risk.

Categories

Installs
11
GitHub Stars
1
First Seen
Sep 10, 2026