first-principles-review

1# First Principles Review
2 
3## Purpose
4 
5Use this as a lightweight decision review before another Aegis workflow makes a
6directional choice. It is a compositional skill, not a standalone workflow.
7 
8Do not replace `brainstorming`, `systematic-debugging`, `writing-plans`,
9`requesting-code-review`, or `verification-before-completion`. Use it to clean
10the decision surface those skills will act on.
11 
12When this review materially changes the direction, surface `Aegis Visibility`
13in natural prose: name the first principle, dropped assumption, smallest
14sufficient path, or owner / retirement falsifier that changed the decision.
15Keep it advisory and task-specific; do not turn the lens into approval
16authority or a generic skill trace.
17 
18## Use When
19 
20- The user asks for first principles, first-principles thinking, or Occam's
21  razor.
22- A design, plan, or fix has multiple plausible paths and unclear selection
23  criteria.
24- The task has ambiguous goals, competing constraints, or product/architecture
25  direction risk.
26- Debugging is drifting into repeated fixes, fallback growth, duplicate owners,
27  consumer-side patches, or "just add another branch" reasoning.
28- A review finds that the implementation may be locally correct but directionally
29  wrong.
30 
31## Do Not Use
32 
33- Simple Q&A, status checks, tiny wording/config edits, or clearly bounded
34  single-owner changes.
35- Mechanical execution of an approved plan unless a new directional conflict
36  appears.
37…