Plan, audit, and anchor sprint work to a complete Product Requirements Document.
npx skills add https://github.com/YarikChekin/ralph-cc --skill prd-plan
Please help me install this Agent Skill. Skill: prd-plan Source: https://github.com/YarikChekin/ralph-cc/tree/main/skills/prd-plan Command: npx skills add https://github.com/YarikChekin/ralph-cc --skill prd-plan
PRD Plan helps teams create, extend, and audit a Product Requirements Document that guides sprint planning and ensures alignment before starting work.
Describe your project in a PRD and then run /new-sprint to generate your first sprint.
High-intent search queries and answers about installing and using this skill.
A complete product requirements document for sprint planning should include problem and vision statements, target users, features with acceptance criteria, scope, non-goals, data model, tech stack, and success criteria. This ensures stakeholders align on goals before development starts.
To audit an existing PRD for missing requirements, verify completeness against standard sections like problem/vision, user roles, features with acceptance criteria, scope, non-goals, data model, and success criteria. This identifies gaps and ensures alignment across teams before sprint execution.
To create a PRD from scratch for a new product feature, define the problem and vision, identify target users, list features with acceptance criteria, outline scope and non-goals, specify the data model and tech stack, and define success criteria. Save the final document reference to docs/PRD.md.
Generating a PRD references existing project metadata from RALPH.md to ensure alignment with details like Project.Name. While it helps anchor sprint work to existing context, you can also create a PRD from scratch for new projects without prior metadata.
The best way to align stakeholders before starting a new sprint is to audit and complete a PRD that covers problem/vision, user roles, features with acceptance criteria, and non-goals. This documentation satisfies completeness requirements and ensures shared understanding.
Yes, you can use this PRD planning approach to add a feature to an existing project. It supports extending current documentation by auditing the existing PRD, verifying scope and data model completeness, and anchoring new sprint work to the updated requirements.
YarikChekinScaffold the Ralph workflow by creating RALPH.md and starter templates.
zabuuqConvert incomplete PRD items into a buildable sprint checklist with spec references.
akvoDesign system architectures and document decisions with Architecture Decision Records.
ZateGenerate user stories and acceptance criteria using Given-When-Then templates.
