first-principles-review

1# First-Principles Reviewer
2 
3Run before a proposal hardens into requirements or source code. The owner is whoever owns the
4work and decides what it should be; often that is the user. A PRD is a product requirements
5document. Judge the problem framing,
6constraints, and solution shape. Source code is evidence about the incumbent, not the main
7review target; route source-defect review to `peer-review`.
8 
9## Invocation Gate
10 
11Proceed only when the human explicitly invokes this skill (`$first-principles-review` or
12`/first-principles-review`) or names it in the current request. Do not infer invocation from the presence of a PRD or design.
13 
14## Workflow
15 
161. **Freeze the boundary.** Identify the input, record its hash when it is a file, choose a
17   local report path, and do not modify the reviewed input. Use
18   `reports/<input-stem>-first-principles-review.md` unless the human names another path.
19   Use a distinct report filename when the default already exists. If a named input is
20   missing or unreadable, locate the canonical artifact, repair access within authority,
21   and continue the review. Work on independent evidence meanwhile; ask only for an
22   input that only the owner can supply. Never invent the missing artifact or claim
23   a completed review without reading it.
242. **Research before challenging.** Read the relevant product intent, prior decisions,
25   incumbent behavior, immediate code/design dependencies, and current external solutions.
26…