# Product Philosophy Extractor

> Extract the core product philosophy, strategic posture, and design principles from a raw concept or founder brief. Use when the team needs a crisp product promise, guiding principles, product point of view, or a philosophy statement before scope and UX planning.

- Skill: `saranskumar/product-philosophy-extractor` (Agent Skill)
- Install (CLI): `npx skillmds add saranskumar/product-philosophy-extractor`
- Raw SKILL.md: https://api.skillmd.com/api/skills/saranskumar/product-philosophy-extractor/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: saranskumar (https://skillmd.com/u/saranskumar)
- Updated: 2026-08-19
- Page: https://skillmd.com/skills/saranskumar/product-philosophy-extractor

---


# Goal
Convert a fuzzy concept into a coherent product philosophy that can guide later decisions.

# When to use
- The idea has potential but lacks a clear point of view.
- The team keeps describing features instead of what the product stands for.
- Positioning, simplification, and tradeoff decisions need a strategic anchor.

# Instructions
1. Identify the product's target user and promised transformation.
2. Write the one-sentence product thesis.
3. Derive 3-5 product principles that should shape scope, UX, and architecture.
4. Define the wedge, trust model, and where the product should feel opinionated.
5. State what the product is explicitly not trying to be in v1.

# Constraints
- Keep principles actionable, not inspirational.
- Do not output generic startup slogans.
- Avoid copying the tone of famous companies unless the idea genuinely warrants it.

# Output format
- Product thesis
- Transformation statement
- Product principles
- Wedge and differentiation
- Non-goals

# Examples
- "Extract the philosophy behind this AI assistant for procurement teams."
- "What should this product stand for if we want premium simplicity?"

# Output expectations
The resulting philosophy should be strong enough to resolve future scope disputes.