Generate structured Product Requirements Documents with problem statements and acceptance criteria.
npx skills add https://github.com/nielpattin/.dotfiles --skill prd-nielpattin
Please help me install this Agent Skill. Skill: prd Source: https://github.com/nielpattin/.dotfiles/tree/main/.pi/agent/skills/prd Command: npx skills add https://github.com/nielpattin/.dotfiles --skill prd-nielpattin
This Skill streamlines the creation of Product Requirements Documents (PRDs), ensuring clarity on what needs to be built and why, before development begins.
Create a PRD for the new user login feature.
High-intent search queries and answers about installing and using this skill.
To write a product requirements document, define the problem statement, the end state, acceptance criteria, and technical context to clarify what to build and why before development begins.
A PRD for migrations or refactors should include a clear problem statement, the desired end state, technical context, and acceptance criteria to ensure alignment on objectives before coding starts.
Yes, you can generate a PRD using a roadmap feature ID. The system supports roadmap integration to pre-populate product requirement details based on the provided feature identifier.
Yes, PRD creation includes dependency validation that checks if prerequisite features are completed before proceeding, ensuring foundational requirements are met before planning new functionality.
The best way to define acceptance criteria for feature planning is to structure them within a PRD, explicitly outlining the end state and technical context alongside the initial problem statement.
arthun01Generate a structured roadmap document from product_map.md and vision.md.
KwaminaWhyteGenerate a structured PRD with goals, user stories, and technical requirements.
lukasPWRConvert a Product Requirements Document into a development roadmap with milestones and dependencies.
jvalinskyRefactor Objective-C code comments into Apple HeaderDoc standards.
