speckit-adlc-product-init

Scan codebases to identify implicit product decisions and draft PDRs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify implicit product decisions in an existing codebase and document them as Product Decision Records (PDRs), enabling coherent strategy alignment and stakeholder review.

Core Features & Use Cases

  • Scan codebases and documentation to surface signals such as target market, personas, monetization, pricing, and success metrics.
  • Generate initial PDR drafts stored at {REPO_ROOT}/.specify/drafts/pdr.md and mark them as "Discovered (Inferred)".
  • Auto-trigger clarification workflow to validate brownfield findings with stakeholders.
  • Support sub-system decomposition to organize PDRs by area when multiple modules exist.
  • Flag gaps and uncertainties for human review.

Quick Start

Process your brownfield repository to generate initial PDR drafts and automatically trigger the clarification phase.

Frequently Asked Questions about speckit-adlc-product-init

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

FAQPage Schema
How do I extract product decisions from an existing codebase?

Extract product decisions from an existing codebase by scanning code and documentation to surface implicit signals like target market, personas, and monetization. The inferred decisions are organized into Product Decision Records for stakeholder review.

What are Product Decision Records and when do I need them for brownfield projects?

Product Decision Records document inferred strategic choices in a brownfield project, capturing details like pricing and success metrics. You need them when you must align legacy code with current strategy and require stakeholder validation of implicit product decisions.

How do I generate PDR drafts from legacy code automatically?

Generate PDR drafts automatically by processing a brownfield repository to analyze project structure and code. The system outputs discovered product decisions to a draft markdown file and flags uncertainties for human review.

Can I organize inferred product decisions by sub-system in a large codebase?

Yes, you can organize inferred product decisions by sub-system. When sub-system decomposition is enabled, the analysis structures findings by specific module areas, ensuring coherent strategy alignment across complex, multi-module codebases.

How do I validate inferred product decisions discovered from code?

Validate inferred product decisions by triggering an automated clarification workflow. After scanning the codebase and generating initial drafts, the system auto-hands off to a clarification phase to review flagged gaps and validate findings with stakeholders.

What are the limitations of inferring product decisions from legacy code?

Inferring product decisions from legacy code carries limitations due to implicit logic and missing context. The system flags gaps and uncertainties for human review, meaning inferred PDRs require stakeholder validation before finalizing strategy.