PRD Generator

Generate engineer-focused PRDs by describing your feature or requirement. The Skill produces structured documents with executive summary, goals, user stories, and functional requirements aligned to your project, saved to docs/prds/ with kebab-case filenames for easy reuse.

A complete PRD includes executive summary, problem statement, primary goals, actionable user stories, and ISO-aligned functional requirements. This Skill structures all sections concisely so engineers have clear specifications without excessive documentation overhead.

Yes. Reference your existing PRD and request regeneration or updates when scope or insights shift. The Skill applies the same engineer-focused structure to revised documents, maintaining consistency across iterations.

Request each PRD by feature name with brief context. The Skill generates concise, predefined-section documents by default, eliminating drafting time. Store outputs in docs/prds/ with kebab-case naming for quick discovery and batch reuse.

The Skill is designed for engineer-focused output but accepts high-level feature descriptions. It translates problem statements and goals into structured requirements with functional specifications suitable for engineering handoff, reducing translation friction.

Store PRDs in docs/prds/ using kebab-case filenames matching feature names—for example, docs/prds/expense-category-auto-tagging.md. This standardized structure enables team discovery and reuse across planning cycles.