product-philosophy-designer

Articulate a product thesis, principles, non-goals, and differentiation statements.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/saranskumar/anti-slop --skill product-philosophy-designer
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-philosophy-designer
Source: https://github.com/saranskumar/anti-slop/tree/main/archive/skills-legacy/product-philosophy-designer
Command: npx skills add https://github.com/saranskumar/anti-slop --skill product-philosophy-designer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often lack a coherent product direction, causing misaligned decisions and inconsistent UX and architecture.

Core Features & Use Cases

  • One-line product thesis: a crisp, actionable statement guiding design and engineering.
  • 3-5 practical product principles: concrete constraints that keep the product differentiated and focused.
  • Non-goals & strategic implications: a clear list of what not to do and the architectural/UX tradeoffs.
  • Differentiation & alignment: a statement to help stakeholders prioritize initiatives and roadmaps.

Quick Start

Provide a concise product thesis and 3-5 actionable principles to align the team.

Frequently Asked Questions about product-philosophy-designer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define a clear product vision and principles for early product planning?▼

To define a clear product vision, you articulate a coherent product philosophy that produces a one-line thesis, 3-5 practical principles, non-goals, and a differentiation statement to align planning and execution.

What is a product thesis and how does it guide UX and architecture decisions?▼

A product thesis is a crisp, actionable statement that articulates your core product philosophy. It guides UX and architecture by establishing practical constraints, non-goals, and tradeoffs that align stakeholder initiatives.

How do I create product non-goals to keep my feature roadmap focused?▼

You create product non-goals by articulating a coherent product philosophy during strategic sessions. This process defines what not to do, establishing practical constraints that keep the product differentiated and focused.

Can I use product philosophy articulation for strategic alignment across stakeholders?▼

Yes, you can use product philosophy articulation for strategic alignment. It generates a differentiation statement and practical principles that help stakeholders prioritize initiatives and roadmaps during feature discussions.

What is the best way to document product strategy implications for engineering teams?▼

The best way to document product strategy implications is to articulate a coherent philosophy that outputs a product thesis, practical principles, and non-goals, explicitly stating the architectural and UX tradeoffs for engineering.

Why does my product strategy lack differentiation and consistent UX direction?▼

Your product strategy lacks differentiation due to missing a coherent product philosophy. Articulating a one-line thesis and 3-5 practical principles aligns planning and execution, resolving inconsistent UX and architecture.