sno-ai/sno-station-skills / plugins/sno-station-standalone/skills/first-principles-review
first-principles-review
VerifiedMANUAL-ONLY: challenge a product idea, design, PRD, or architecture from first principles. Use only when the user names this skill. Research first, then write a local review and PRD handoff.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 5.9 KB |
| agents/openai.yaml | config | 353 B |
| references/report-contract.md | markdown | 3.2 KB |
| scripts/extract-prd-handoff.pyexecutable | script | 1.1 KB |
| scripts/selftest/fixtures/expected-handoff.json | config | 1.9 KB |
| scripts/selftest/fixtures/scenarios/inherited-constraint-test-first.md | markdown | 2.1 KB |
| scripts/selftest/fixtures/scenarios/raw-idea-reframe.md | markdown | 2.1 KB |
| scripts/selftest/fixtures/scenarios/sound-design-proceed.md | markdown | 2.0 KB |
| scripts/selftest/fixtures/target-prd.md | markdown | 347 B |
| scripts/selftest/fixtures/valid-report.md | markdown | 3.9 KB |
| scripts/selftest/run-extractor-test.shexecutable | script | 1.9 KB |
| scripts/selftest/run-scenarios.shexecutable | script | 3.2 KB |
| scripts/selftest/run-selftest.shexecutable | script | 4.9 KB |
| scripts/selftest/verify-manual-only.shexecutable | script | 2.8 KB |
| scripts/selftest/verify-workflow-policy.shexecutable | script | 1.8 KB |
| scripts/validate-report.pyexecutable | script | 9.6 KB |
references/report-contract.md
View on GitHub# Report Contract
Write one Markdown report with exactly one `PRD Handoff` section and exactly one JSON block.
Use the sections below in this order. Every section needs substantive content. The report must
contain no `?` character; put surviving choices under
`Owner Decisions` as declarative open decisions, then ask them one at a time in chat.
````markdown
# First-Principles Review: <subject>
## Scope and Boundary
<input, hash when applicable, output boundary, bounded and non-exhaustive statement>
## Research Receipt
<sources read, finding from each, and verified/inference/unknown status>
## True Outcome
<implementation-independent user or system outcome>
## Constraint and Assumption Analysis
<each claim classified as hard constraint, owner preference, or inherited assumption>
## Premise Ledger
<each load-bearing premise, evidence state, challenge applied, and result>
## Alternatives
<only materially distinct alternatives and why each differs>
## Primary Recommendation
**Disposition:** PROCEED|REFRAME|SIMPLIFY|REPLACE|SPLIT|TEST-FIRST|STOP
<one primary direction and comparison with the current proposal>
## Falsifiers
<observable evidence that would overturn the recommendation>
## Owner Decisions
<declarative list of unresolved product choices, or `None.`>
## PRD Handoff
```json
<handoff object>
```
````
The handoff object has exactly these required top-level fields. Extra fields are allowed when
they add evidence rather than a second interpretation.
```json
{
"true_problem": "non-empty implementation-independent outcome",
"constraints": [
{
"claim": "non-empty",
"classification": "hard constraint | owner preference | inherited assumption",
"evidence": "non-empty source or explicit unknown",
"state": "evidence-backed | unproven | inherited | falsified"
}
],
"premises": [
{
"claim": "non-empty load-bearing premise",
"state": "evidence-backed | unproven | inherited | falsified",
"challenge": "non-empty challenge applied",
"result": "non-empty result"
}
],
"selected_direction": {
"disposition": "PROCEED | REFRAME | SIMPLIFY | REPLACE | SPLIT | TEST-FIRST | STOP",
"recommendation": "non-empty",
"falsifiers": ["one or more observable overturning conditions"],
"split_outcomes": ["at least two independently buildable outcomes when disposition is SPLIT"]
},
"rejected_alternatives": [
{"name": "non-empty", "reason": "non-empty"}
],
"experiments": ["next evidence-producing action"],
"acceptance_implications": ["requirement or acceptance consequence"],
"open_owner_decisions": ["declarative decision statement"],
"research_receipt": [
{"source": "non-empty", "finding": "non-empty", "status": "verified | inference | unknown"}
],
"calibration": {
"verified_facts": ["fact"],
"inferences": ["inference"],
"unknowns": ["unknown"]
}
}
```
`rejected_alternatives`, `open_owner_decisions`, the three calibration arrays, and
`selected_direction.split_outcomes` may be empty. `split_outcomes` must contain at least two
items for `SPLIT` and must be empty otherwise. All other arrays must be non-empty. A report with
no research or no challenged premise is invalid.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| brainstormingobra/superpowersYou MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation). | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| brand-guidelinesanthropics/skillsApplies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| frontend-designanthropics/skillsGuidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| mcp-builderanthropics/skillsGuide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK). | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |