Write PRDs with frontmatter and five required sections.
npx skills add https://github.com/mechemsi/claude-template --skill writing-prd-mechemsi
Please help me install this Agent Skill. Skill: writing-prd Source: https://github.com/mechemsi/claude-template/tree/main/skills/writing-prd Command: npx skills add https://github.com/mechemsi/claude-template --skill writing-prd-mechemsi
The PRD process clarifies the problem, audience, and success criteria before diving into technical design, reducing misaligned efforts and wasted work.
Draft a PRD by outlining the problem, users, success criteria, scope, and risks, and save it under claudedocs/prds/ using the YYYY-MM-DD-short-name.md convention.
High-intent search queries and answers about installing and using this skill.
To write a PRD for unclear scope, document the problem, users, success criteria, scope, and risks to align stakeholders before technical design. This structured approach prevents wasted work on misaligned efforts.
Required sections in a product requirements document for cross-team initiatives include Problem, Users, Success Criteria, Scope, and Risks. Frontmatter must contain title, status, date, and related fields to enforce consistency.
You need a PRD before planning a major behavior change when success metrics or scope are unclear across teams. Documenting decisions upfront clarifies the audience and success criteria, reducing misaligned technical efforts.
The best way to structure product management handoffs to plans is by completing a PRD with defined scope and success criteria, then saving it under the claudedocs/prds/ directory using the YYYY-MM-DD-short-name.md naming convention.
Yes, this PRD template works for stakeholder alignment on cross-team projects by enforcing upfront documentation of decisions, scope, and risks. It guides cross-team planning by clarifying the problem and audience before implementation.
Defining product requirements before technical design reduces wasted work by clarifying the problem, audience, and success criteria upfront. This PRD process ensures all stakeholders share a consistent understanding of the scope before implementation begins.
sinositatoGather problem, user, scope, and success criteria into a markdown context file.
Ronin15Generate a structured Markdown changelog from SDL3 HammerEngine git history.
s1366560Prioritize features with RICE scoring and analyze customer interview transcripts.
shawnpangTranslate ambiguous product ideas into an 8-section PRD with success metrics.
