product-specify

Coordinate product strategy exploration and generate Product Decision Records.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/chaimt/GarminShabbatMode --skill product-specify
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: product-specify
Source: https://github.com/chaimt/GarminShabbatMode/tree/main/.cursor/skills/product-specify
Command: npx skills add https://github.com/chaimt/GarminShabbatMode --skill product-specify

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams struggle to transform nebulous product ideas into documented decisions without a structured, interactive exploration process. This skill provides an guided workflow to decompose ideas, surface trade-offs, and produce Product Decision Records (PDRs) that tie to constitution principles.

Core Features & Use Cases

  • Interactive feature-area decomposition and decision framing across domains.
  • Guided product exploration with a structured decision framework.
  • Generates PDRs aligned to constitution principles.
  • Cross-area linking and cross-cutting considerations.
  • Use cases include new product ideas, major pivots, and documenting decisions for governance.

Quick Start

Describe your product idea to start an interactive exploration and generate PDRs.

Frequently Asked Questions about product-specify

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

FAQPage Schema
How do I write a Product Decision Record for a new feature area?

To write a Product Decision Record (PDR), start by describing your product idea to initiate an interactive exploration. The workflow decomposes the idea into feature areas, surfaces trade-offs, and generates PDRs aligned to project constitution principles.

What is the best way to structure product discovery for cross-functional teams?

Structured product discovery uses a phase-based workflow to coordinate strategy exploration across cross-functional teams. It guides interactive feature-area decomposition and cross-cutting considerations to transform nebulous ideas into documented decisions.

How do I document major product pivots for governance?

Document major product pivots for governance by running a guided product exploration session. This generates formal Product Decision Records (PDRs) that capture the structured decisions and trade-offs aligned with your project constitution.

Can I use interactive PRDs to decompose complex product domains?

Yes, interactive PRDs support complex domain decomposition. The workflow applies interactive exploration prompts to break down new product initiatives into manageable feature areas and link cross-cutting considerations across domains.

Does this product discovery workflow require any specific frameworks or dependencies?

No specific frameworks or dependencies are required to run this product discovery workflow. You simply need to describe your product idea to start the interactive exploration and generate the aligned decision records.

When do I need a Product Decision Record instead of a standard PRD?

You need a Product Decision Record (PDR) instead of a standard PRD when you require formal decision documentation for governance. PDRs tie directly to constitution principles and provide structured trade-off analysis for major pivots or new initiatives.