Create an 8-section markdown Product Requirements Document with SMART objectives.
npx skills add https://github.com/tarunccet/pm-skills --skill create-prd-tarunccet
Please help me install this Agent Skill. Skill: create-prd Source: https://github.com/tarunccet/pm-skills/tree/main/pm-execution/skills/create-prd Command: npx skills add https://github.com/tarunccet/pm-skills --skill create-prd-tarunccet
This Skill removes the friction of drafting clear, aligned Product Requirements Documents by providing a repeatable 8-section template and a guided workflow that surfaces missing inputs, assumptions, and measurable objectives.
Create a PRD for "Smart notification batching" targeting enterprise Slack users with the objective to reduce notification-driven churn by 15%.
High-intent search queries and answers about installing and using this skill.
To write a product requirements document, use a guided 8-section template to capture summary, contacts, background, SMART objectives, market segments, value propositions, solution details, and release planning. The workflow summarizes inputs, asks for missing details, and validates assumptions before generating a markdown file.
A stakeholder-ready PRD should include SMART key results, defined market segments, explicit value propositions, and solution details covering UX, technical assumptions, and AI considerations. It must conclude with structured release planning to ensure cross-functional alignment.
Yes, you can generate a PRD with a basic feature idea because the workflow performs context confirmation and gap detection. It summarizes your initial input, asks only for missing details, and validates assumptions before drafting the complete document.
The best way to structure release planning in a feature spec is to include it as the final section of an 8-part PRD template. This ensures release milestones align directly with the documented SMART objectives, technical assumptions, and solution details.
Yes, the PRD template supports AI product management by including a dedicated section for AI considerations within the solution details. This ensures technical assumptions and AI-specific requirements are documented alongside standard features and UX.
Measurable objectives in a product requirements document are defined using SMART key results within the objective section. This ensures product goals are specific, measurable, achievable, relevant, and time-bound for stakeholder tracking.
HerbertJulioTranslate product ideas into structured PRDs with user stories and GitHub issues.
dhar174Generate a structured Markdown PRD from a high-level Epic.
Ethical-AI-SyndicateSynthesize product vision statements, success metrics, and elevator pitches from stakeholder input.
intent-integrity-chainCreate structured feature specifications from natural language descriptions.
