product-principles
Skill7 starsChanged 3 months agoMITView on GitHub
Defines 4 Risks confidence thresholds, OST hierarchy levels, Knowledge Pyramid tiers, and state design requirements. Use when evaluating user stories, setting confidence scores, referencing OST levels, scoping MVP, or determining validation sufficiency.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- doodledood/manifest-devtheir own version, first seen Nov 15, 2026
- openkursar/hello-halotheir own version, first seen Nov 1, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- openkursar/hello-halo★ 1.9ksame name
- doodledood/manifest-dev★ 78same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository15 other files it gives its agents.
- blueprint-standardsSkill
- business-contextSkill
- design-perspectiveSkill
- hypothesis-disciplineSkill
- prd-standardsSkill
- prototype-guideSkill
- recipe-blueprintSkill
- recipe-defineSkill
- recipe-discoverSkill
- recipe-personaSkill
- recipe-prototype-promptSkill
- recipe-refine-visualsSkill
- recipe-reflectSkill
- recipe-validateSkill
- recipe-visionSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 5 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Hypothesis Until Proven: Every assumption is a hypothesis until validated with evidence.
- Distinctive: line 12
Proportionate Validation: Use cost x risk x reversibility to determine sufficient confidence
- Distinctive: line 13
Proportionate Artifacts: Keep durable decisions in repo artifacts when a downstream consumer will reuse them.
- Distinctive: line 17
Use this hierarchy to distinguish outcomes, opportunities, solutions, assumptions, and experiments when those distinctions affect the …
- Distinctive: line 107
3+ Solutions Test: Use the ability to identify meaningfully different Solutions as a diagnostic for whether an Opportunity is framed too …
- Very specific: line 111
MVP Scoping: When transitioning validated hypotheses to PRD, use references/mvp-definition.md for prioritization (MoSCoW/RICE) and scope …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Product Management Principles
Core Philosophy
- Hypothesis Until Proven: Every assumption is a hypothesis until validated with evidence. Treat unvalidated ideas as hypotheses, not facts
- Value Traceability: Preserve the links needed to connect a decision or implementation back to its supporting outcome and evidence
- Proportionate Validation: Use cost x risk x reversibility to determine sufficient confidence
- Proportionate Artifacts: Keep durable decisions in repo artifacts when a downstream consumer will reuse them; no-change and reuse are valid outcomes
Opportunity Solution Tree (OST) Hierarchy
Use this hierarchy to distinguish outcomes, opportunities, solutions, assumptions, and experiments when those distinctions affect the current decision:
Outcome
├── Product Outcome (team-controllable product goals)
│ NSM connects Product Outcome ↔ Business Outcome
└── Business Outcome (business results Product Outcome contributes to)
Product Outcome
└── Opportunity (user problems, needs, desires)
└── Solution (approaches to address the opportunity = feature candidates)
└── Assumption (premises underlying the solution = hypotheses)
└── Experiment (methods to validate the hypothesis)Level Definitions
| Level | Granularity | Artifact | Description |
| Business Outcome | Largest | docs/product/vision.md | Business results the product contributes to |
| Product Outcome | Large | docs/product/vision.md | Team-controllable product goals |
| Opportunity | Large | docs/discovery/opportunities/ | User problems, needs, desires |
| Solution | Medium | PRD (docs/prd/) | Feature candidates addressing an Opportunity |
| Assumption | Small | docs/discovery/hypotheses/ | Premises underlying a Solution |
| User Story | Smallest | Within PRD | Minimum unit of value with sufficient evidence for its material risks |
4 Risks (Authoritative Definition)
A user story is the minimum unit of value. Consider all four risks and gather enough evidence for the dimensions that can change the delivery decision:
- Value — Will users use/buy this? Does it solve their problem?
- Usability — Can users figure out how to use it? Does the UX work?
- Feasibility — Can we build it technically? Is the effort realistic?
- Viability — Does it work as a business? Can we explain why we're building it?
Confidence Meter (Authoritative Definition)
Track confidence per risk dimension (0-10):
| Score | Meaning | Typical Evidence |
| 0-2 | Gut feeling / no evidence | Assumption only |
| 3-4 | Structured evaluation | Expert review, competitive analysis, scoring |
| 5-7 | Data-backed | Analytics, surveys, interview patterns |
| 8-10 | Tested and confirmed | Prototype validation, A/B test, beta results |
Threshold by Cost x Risk x Reversibility
| Condition | Confidence Needed | Evidence Level |
| Low-cost, reversible (feature flag, gradual rollout) | 3-4 | Structured evaluation |
| Medium cost | 5-7 | Data |
| High-cost, irreversible (platform change, pricing change) | 8+ | Test results |
PRDs show current confidence and remaining risks at the smallest scope that changes a delivery decision. Keep shared evidence and decisions at feature scope.
Knowledge Pyramid (Authoritative Definition)
Knowledge is organized in three tiers to manage context as hypotheses accumulate:
| Tier | Scope | Location | Loading |
| Tier 1 | Distilled product principles | docs/product/learnings.md | When durable learning can change the current decision |
| Tier 2 | Opportunity-level learnings | Each Opportunity file's "Tier 2 Learnings" section | When working on that Opportunity |
| Tier 3 | Individual hypothesis files | docs/discovery/hypotheses/ | On demand |
Tier 1 learnings are corroborated patterns that remain useful across the contexts where they will guide decisions.
Distillation criteria (enforced by knowledge-distiller):
- Independent corroboration: Independent evidence supports the learning across its intended decision scope
- Context coverage: Supporting contexts match the scope where the learning will guide decisions
- Contradiction handling: Conflicting evidence is retained with the conditions that explain its decision effect
- Freshness: Revalidate when source age or changed conditions can alter a current decision
State Design (Authoritative Definition)
For each user-facing interaction, define the states that can occur and affect its acceptance. The categories below are a reference set, not a required checklist:
| State | Description |
| Loading | Data is being fetched/processed — show progress indicator |
| Empty | No data exists yet — guide user to first action |
| Error | Something went wrong — explain what happened, offer recovery |
| Partial | Some data available, some not — show available, indicate missing |
| Success | Normal state with data — primary design focus |
PRDs and prototypes cover the states needed to define or validate the current interaction. Record an exclusion only when its absence could obscure the acceptance or validation decision.
Key Principles for Daily Decisions
- 3+ Solutions Test: Use the ability to identify meaningfully different Solutions as a diagnostic for whether an Opportunity is framed too narrowly. A failed diagnostic is a framing signal, not an obligation to manufacture alternatives. See
references/opportunity-template.mdfor Opportunity file structure - Business Outcome Traceability: Preserve the connection to business outcomes while using NSM to balance metric pressure
- Design is a Perspective, Not a Phase: Design thinking applies across all processes — discovery, validation, definition, delivery, and reflection
- Cycle, Not Phases: Discovery → Validation → Definition → Delivery → Reflection is a continuous cycle. Start from anywhere
- MVP Scoping: When transitioning validated hypotheses to PRD, use
references/mvp-definition.mdfor prioritization (MoSCoW/RICE) and scope reduction techniques
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

