skills.rest
Roudranil
RoudranilCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

product-management

Translate vague founder ideas into formal product definitions and PRDs.

Updated Apr 12, 2026
Search Tags:#documentation#specification#governance#prd#product-management#ideation-tracking
One-click install
npx skills add https://github.com/Roudranil/variance --skill product-management-roudranil
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: product-management
Source: https://github.com/Roudranil/variance/tree/main/.claude/skills/product-management
Command: npx skills add https://github.com/Roudranil/variance --skill product-management-roudranil

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translating vague founder ideas into concrete, actionable product definitions is slow and error-prone. This Skill standardizes the process, ensuring clear specs, edge-case consideration, and governance before any implementation.

Core Features & Use Cases

  • PRD creation & governance: Produce a formal Product Requirements Document and manage its versioned lifecycle.
  • Structured ideation & traceability: Maintain an Ideation Tracker, Ideation Diff, and Gaps & Questions to surface conflicts and decisions early.
  • Documentation-first workflow: Ensure all product decisions are captured before engineering work begins, with explicit dependencies and sequencing.

Quick Start

Draft the PRD at docs/01-product/prd.md with problem, goals, and a feature graph, then initialize the ideation tracker at docs/06-helpers/ideation-tracker.md and the gaps log at docs/06-helpers/gaps-and-questions.md and begin capturing questions.

Frequently Asked Questions about product-management

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

FAQPage Schema
How do I translate vague founder ideas into formal product specifications?▼

To translate vague founder ideas into formal product specifications, use a documentation-first workflow that standardizes PRD creation, ideation tracking, and gaps analysis to achieve system clarity before any engineering work begins.

What is a documentation-first workflow for PRD development?▼

A documentation-first workflow for PRD development ensures all product decisions are captured in structured, versioned documents before engineering work begins, establishing explicit dependencies and sequencing.

How do I track ideation and gaps analysis during product definition?▼

You can track ideation and gaps analysis during product definition by maintaining an Ideation Tracker and a Gaps and Questions log, which surface conflicts and decisions early in the process.

Does PRD governance require versioned lifecycle management for product specs?▼

Yes, PRD governance requires versioned lifecycle management to ensure product specs remain structured, traceable, and accurately reflect formal product definitions throughout development.

When should I not begin engineering work on a new product feature?▼

You should not begin engineering work until system clarity is achieved through formal product definition, meaning all PRD development, ideation tracking, and gaps analysis are fully documented.

Related Skills

Explore More Product & Management Skills→
chendongqichendongqi
110

product-ideation-pm

Generate divergent product ideas and draft product definition documents.

Community
Advanced
InNoobWeTrustInNoobWeTrust
4

requirements-driven-dev

Cascade product requirements from PRD to TRD to BDD with traceability matrices.

Community
Advanced
AnEntrypointAnEntrypoint
20

planning

Construct a Product Requirements Document in .prd JSON format.

Official
Advanced
akvoakvo
2

bmad-sm

Generate developer-ready user stories from PRD and architecture documents.

Official
Advanced