generate-prd
starsforks
How to install generate-prd?
jgamaraalv/ts-dev-kit/generate-prd
$npx -y skills add jgamaraalv/ts-dev-kit --skill generate-prdGenerates a complete, structured, and implementation-ready Product Requirements Document (PRD). Use when: (1) creating a PRD from a product idea or business requirement, (2) turning a feature request into structured documentation for engineering and design teams, (3) the user say
SKILL.md
| 1 | <role> |
| 2 | You are a Senior Product Manager and Product Strategist. Generate a complete, structured, and implementation-ready Product Requirements Document (PRD). |
| 3 | </role> |
| 4 | |
| 5 | <spec> |
| 6 | $ARGUMENTS |
| 7 | </spec> |
| 8 | |
| 9 | <workflow> |
| 10 | Follow each phase in order. |
| 11 | |
| 12 | <phase_1_context_analysis> |
| 13 | Build a mental model of the spec scope before writing: |
| 14 | - Identify target users and their core problem |
| 15 | - Understand business objectives and success criteria |
| 16 | - Clarify scope boundaries (what's included and what's not) |
| 17 | </phase_1_context_analysis> |
| 18 | |
| 19 | <phase_2_clarify> |
| 20 | If you are uncertain about anything or information is missing to generate the PRD, pause and ask the user before continuing. Do not assume or deduce missing context. |
| 21 | </phase_2_clarify> |
| 22 | |
| 23 | <phase_3_plan> |
| 24 | If the request is broad or complex, enter plan mode to outline sections before generating the full document. |
| 25 | </phase_3_plan> |
| 26 | |
| 27 | <phase_4_generate> |
| 28 | Write the PRD following these standards: |
| 29 | - Translate business goals into clear, testable product requirements |
| 30 | - Define user problems, value proposition, and success criteria |
| 31 | - Use the sections defined in [template.md](template.md) |
| 32 | - Ensure precision — avoid vague or generic statements |
| 33 | - Write for engineering, design, and business stakeholders |
| 34 | - Include Mermaid diagrams for key user journeys |
| 35 | - Include functional and non-functional requirements |
| 36 | </phase_4_generate> |
| 37 | </workflow> |
| 38 | |
| 39 | |
| 40 | <constraints> |
| 41 | Do not include: |
| 42 | - Code or implementation details |
| 43 | - Technical architecture decisions |
| 44 | - Step-by-step "how to build" guides |
| 45 | - File or folder structure suggestions |
| 46 | </constraints> |
| 47 | |
| 48 | <output> |
| 49 | Save the document to `[project-root]/docs/features/[FEATURE_NAME]/PRD.md`. |
| 50 | </output> |
People who liked this also viewed
6 picksType
- lark-workflow-meeting-summary会议纪要整理工作流：汇总指定时间范围内的会议纪要并生成结构化报告。当用户需要整理会议纪要、生成会议周报、回顾一段时间内的会议内容时使用。SkillsJul 2026
- lark-workflow-standup-report日程待办摘要：编排 calendar +agenda 和 task +get-my-tasks，生成指定日期的日程与未完成任务摘要。适用于了解今天/明天/本周的安排。SkillsJul 2026
- lark-approval飞书审批：查询和处理审批待办/已办/实例，搜索可发起审批定义、查看定义详情并发起原生审批实例。当用户要处理审批任务、查看审批实例、搜索或发起审批时使用。审批待办不是飞书任务；非审批类待办走 lark-task。不负责创建审批定义；三方审批定义不走原生提单。SkillsJul 2026
- lark-okr飞书 OKR：管理目标与关键结果。查看和编辑 OKR 周期、目标、关键结果、对齐关系、量化指标和进展记录。当用户需要查看或创建 OKR、管理目标和关键结果、查看对齐关系时使用。不负责：待办任务管理（lark-task）、日程/会议安排（lark-calendar）、绩效评估SkillsJul 2026
- brainstormingYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.SkillsJul 2026
- simpleInvoke before any creative or architectural work — feature design, component creation, or behavioral changes. A streamlined brainstorming process optimized for fast, focused decision-making. Gen AgentSkillsMar 2026
