القائمة
Draft product requirements documents with market research, user stories, and acceptance criteria. Uses web search to ground recommendations in current market data and competitive context.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Evaluate, prioritize, and organize feature ideas from Jira, Aha!, or Monday. Use when sorting a backlog, preparing for planning, or reviewing incoming requests.
Generate a sprint retrospective from sprint data and team activity. Pulls completed work from Jira and code contributions from GitHub to build a structured retro with wins, misses, and action items.
| name | prd-writer |
| description | Draft product requirements documents with market research, user stories, and acceptance criteria. Uses web search to ground recommendations in current market data and competitive context. |
| license | MIT |
| metadata | {"author":"pmcode","version":"1.0","category":"planning","connectors":"tavily"} |
| allowed-tools | Bash(git:*) Read |
When the user asks to write a PRD, follow these steps:
Clarify scope: Ask the user for the feature or product name, the problem it solves, and the target audience. If they provide a one-liner, ask follow-up questions to fill gaps before drafting.
Research: Use web search to gather current context:
Draft the PRD with these sections:
Review and iterate: Present the draft and ask the user to flag sections that need revision. Offer to expand any section, add diagrams (as Mermaid markup), or adjust the level of detail.
Export: Save the final PRD as a markdown file in the workspace. Offer to create a summary version suitable for a Jira epic description or a stakeholder email.
