speckit-adlc-product-specify

Guide teams through interactive PRD exploration and produce structured Product Decision Records.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides teams to perform interactive PRD exploration and produce structured Product Decision Records to capture decisions, trade-offs, and rationale.

Core Features & Use Cases

  • Interactive exploration: facilitates discussion to surface assumptions, constraints, and options before committing to documentation.
  • Per-area decision tracing: decomposes large ideas into feature areas and creates area-scoped PDRs.
  • Output alignment: ensures PDRs align with constitution principles and can feed downstream PRDs.
  • Collaboration-ready: supports team reviews with traceable decisions and versioned outputs.

Quick Start

Provide your product idea context to begin interactive PRD exploration and generate PDRs.

Frequently Asked Questions about speckit-adlc-product-specify

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

FAQPage Schema
What is a Product Decision Record and when do I need it for product discovery?

A Product Decision Record (PDR) captures decisions, trade-offs, and rationale during product discovery. You need it to trace assumptions and constraints before committing to a full PRD, ensuring alignment with constitution principles.

How do I decompose a greenfield product idea into feature areas for PRD exploration?

To decompose a greenfield idea for PRD exploration, provide your product context to initiate interactive exploration. The system breaks down large ideas into discrete feature areas and generates area-scoped PDRs for stakeholder iteration.

What's the best way to capture stakeholder decisions and trade-offs during product discovery?

The best way to capture stakeholder decisions is through interactive PRD exploration that surfaces options and constraints. This produces structured, versioned PDRs that document trade-offs and enable team reviews with cross-area traceability.

Can I generate a PRD from a Product Decision Record?

Yes, you can generate a downstream PRD from a Product Decision Record. PDRs are structured to align with constitution principles and feed directly into PRD generation, maintaining traceability across feature areas.

Does this approach work for complex product strategies or only greenfield ideas?

This approach works for both greenfield ideas and complex product strategies. It applies interactive exploration to decompose inputs into feature areas, iterating decisions with stakeholders and documenting them in structured PDR format.

Why should I use interactive PRD exploration instead of writing a PRD directly?

Interactive PRD exploration surfaces assumptions, constraints, and options before documentation. It creates traceable, versioned PDRs that align with constitution principles, preventing undocumented trade-offs and misaligned downstream PRDs.