shape

Generate four PRD documents with standardized frontmatter and open-question sections.

2|1|Updated Oct 8, 2009
One-click install
npx skills add https://github.com/riethmayer/dotfiles --skill shape-riethmayer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shape
Source: https://github.com/riethmayer/dotfiles/tree/main/stow/agents/.agents/skills/shape
Command: npx skills add https://github.com/riethmayer/dotfiles --skill shape-riethmayer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shape project work into a walkable PRD package — transforming vague ideas into a concrete, review-ready structure.

Core Features & Use Cases

  • Generate four documentation files: 00-press-release.md, 01-overview.md, 02-capabilities.md, and 03-scenarios.md, each with standardized frontmatter and open-question sections.
  • Enforce a tracer-first approach to surface the smallest end-to-end path before durable architecture.
  • Facilitate collaboration by providing a structured PRD workflow that invites stakeholder feedback via open questions and iterative shaping.

Quick Start

Run the shape workflow to generate the four PRD documents in the current project and begin iterative shaping with the user.

Frequently Asked Questions about shape

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

FAQPage Schema
How do I turn a product idea into a structured PRD for stakeholder review?

A PRD workflow shapes vague ideas into a review-ready package by generating four sequential markdown files: press release, overview, capabilities, and scenarios, each including frontmatter and open-question sections for stakeholder feedback.

What is the best way to scope a new feature using a tracer-first approach?

A tracer-first PRD approach surfaces the smallest end-to-end path before durable architecture, producing structured capabilities and scenarios documents that guide iterative feature scoping and stakeholder review.

How do I document product scenarios and capabilities for project planning?

Documenting capabilities and scenarios requires generating standardized markdown files with frontmatter that structure project scope, define feature boundaries, and include open-question sections to invite collaborative stakeholder feedback.

Can I use this PRD workflow to plan and scope capabilities without prior documentation?

This PRD workflow plans and scopes capabilities from scratch by transforming vague ideas into a concrete, review-ready structure, generating overview, capabilities, and scenarios documents without requiring prior documentation.

What are the limitations of using a fixed four-file PRD template for product management?

The fixed four-file PRD template enforces a strict press-release, overview, capabilities, and scenarios abstraction, limiting flexibility for projects requiring alternative documentation formats, fewer structural constraints, or non-standard planning workflows.