product-init

Scan codebases and documentation to generate product decision record drafts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool helps teams reverse-engineer implicit product decisions from an existing codebase and documentation, generating structured PDRs for review and alignment.

Core Features & Use Cases

  • Scans repository structure and documentation to surface signals about target market, monetization, scope, and workflow choices.
  • Generates draft PDRs at {REPO_ROOT}/.specify/drafts/pdr.md and flags uncertainties for clarification.
  • Automatically triggers the clarify phase to validate findings and refine decisions.

Quick Start

Run product-init on your brownfield repository to surface and draft product decision records.

Frequently Asked Questions about product-init

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

FAQPage Schema
How do I document implicit product decisions in a brownfield codebase?

To document implicit product decisions in a brownfield codebase, you can scan the existing repository structure and documentation to generate structured Product Decision Records that flag uncertainties for team review.

What is a Product Decision Record and when do I need to generate one?

A Product Decision Record is a structured document capturing implicit choices about scope and workflows. You need to generate one when reverse-engineering undocumented product context from multi-subsystem brownfield projects for alignment.

How to reverse-engineer product specs from existing documentation and code?

Reverse-engineer product specs by scanning existing codebases and documentation to surface signals about monetization and target market, producing a ready-to-review draft at the repository root for subsequent implementation phases.

Does product-init work with multi-subsystem brownfield projects?

Yes, product-init is specifically designed for brownfield projects with multi-subsystem structures, scanning them to produce per-PDR metadata and confidence levels for uncovered product decisions.

What happens after generating a draft PDR for an existing repository?

After generating a draft PDR at the repository root, the tool automatically triggers a clarify phase to validate findings, refine decisions, and prepare the draft for the subsequent implementation process.

Can I extract monetization and target market signals from an existing codebase?

Yes, you can extract monetization and target market signals by scanning existing repository documentation and code structure, surfacing these implicit workflow choices within the generated Product Decision Records.