Create structured PRD templates capturing goals, constraints, risks, and metrics.
npx skills add https://github.com/ajoslin/dot --skill prd-ajoslin
Please help me install this Agent Skill. Skill: prd Source: https://github.com/ajoslin/dot/tree/main/config/opencode/skills/prd Command: npx skills add https://github.com/ajoslin/dot --skill prd-ajoslin
Teams often launch features without a clear, shared understanding of goals, scope, and constraints, leading to rework and misalignment.
Use the PRD framework to draft a feature's guiding document before any implementation work.
High-intent search queries and answers about installing and using this skill.
A product requirements document (PRD) captures the why, what, and how of a feature before implementation to align stakeholders on goals, scope, and constraints. It prevents rework by establishing a shared understanding across teams.
To write a PRD for multi-team initiatives, apply a structured framework that outlines goals, constraints, risks, and success metrics. Use documentation scaffolding and planning prompts to guide stakeholder reviews and ensure alignment.
You need a PRD framework when launching features with unclear scope or those spanning multiple teams. It establishes a shared understanding of goals and constraints before implementation, directly preventing rework and misalignment.
Yes, a lightweight PRD template provides structured documentation scaffolding for stakeholder reviews. It captures essential goals, constraints, and metrics without excessive overhead, enabling fast planning and clear alignment.
The best way to document risks and success metrics in a PRD is using a structured template that explicitly prompts for these elements. This ensures goals, constraints, and metrics are defined before implementation begins.
Yes, the PRD skill generates a structured output including a docs/prd/<feature-slug>/PRD.md template. This provides an end-to-end demo path and documentation scaffolding for stakeholder reviews.
kevinlinGenerate a structured PRD with problem statements, goals, user stories, and acceptance criteria.
psd401Translate product ideas into structured PRDs and user stories.
0xHoneyJarConvert PRD and SDD documents into sprint-ready implementation roadmaps.
marcmontecalvoValidates product requirement documents against project standards and compliance checklists.
