← ClaudeAtlas

product-principleslisted

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.
Florellaoccipital551/claude-code-discover · ★ 0 · AI & Automation · score 75
Install: claude install-skill Florellaoccipital551/claude-code-discover
# Product Management Principles ## Core Philosophy 1. **Hypothesis Until Proven**: Every assumption is a hypothesis until validated with evidence. Treat unvalidated ideas as hypotheses, not facts 2. **Value Traceability**: From hypothesis to validation to user story to PRD to implementation to test — maintain traceability across the entire chain 3. **Feedback Accumulation**: Every outcome (including failures) is a learning asset. Never delete invalidated hypotheses — they inform future decisions 4. **Validated Enough, Not Perfect**: Don't wait for perfect validation. Use cost x risk x reversibility to determine sufficient confidence 5. **Artifacts Over Notes**: Intermediate analysis (market research, competitive landscape, brainstorming) is conducted within the conversation and synthesized into the designated artifact. Each recipe defines its output locations ## Opportunity Solution Tree (OST) Hierarchy All product work follows this hierarchy: ``` 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 | Gran