Translate user input into structured Product Requirements Documents with testing and acceptance criteria.
npx skills add https://github.com/zzafergok/skills --skill prd-zzafergok
Please help me install this Agent Skill. Skill: prd Source: https://github.com/zzafergok/skills/tree/main/06-product-strategy/prd Command: npx skills add https://github.com/zzafergok/skills --skill prd-zzafergok
Product teams struggle to convert vague ideas into a precise, actionable specification that engineers can implement. PRDs often lack a consistent structure, leading to scope ambiguity, misalignment with stakeholders, and delayed delivery.
Provide a concise PRD for a feature by supplying the problem statement, target users, and success metrics.
High-intent search queries and answers about installing and using this skill.
To write a product requirements document engineers can implement, you must apply a structured PRD schema covering Executive Summary, User Experience, Technical Specifications, and Risks & Roadmap to eliminate scope ambiguity and ensure technical alignment.
A PRD for AI-powered features should include standard sections like Executive Summary and User Experience, plus specific AI System Requirements and Technical Specifications to define model behavior, testing, and explicit acceptance criteria.
To convert a vague feature idea into a technical specification for roadmap planning, use a discovery-driven drafting process that forces clarifying questions before writing, ensuring stakeholder alignment and precise technical specifications.
Yes, to generate a production-grade PRD, you need to provide a concise problem statement, target users, and success metrics. This input drives the discovery process and ensures the final specification meets stakeholder expectations.
The best way to align stakeholders before writing a technical specification is to use a template-driven PRD schema with formal discovery, ensuring all functional requirements, risks, and roadmap constraints are documented and shared.
sinositatoGather problem, user, scope, and success criteria into a markdown context file.
eng-ccTranslate vague product ideas into comprehensive PRDs with a strict schema.
ramybarsoumConvert technical designs into phased implementation plans with acceptance criteria.
Fire-ants-never-dieGenerate JSON planning documents with product vision, features, user flows, and requirements.
