snarktank/ralph
Overview
This skill generates a clear, actionable Product Requirements Document (PRD) for a new feature. It guides the user through a short clarifying-question step, then produces a structured PRD suitable for handoff to developers or autonomous agents.
How this skill works
You provide a brief feature description or trigger phrase (e.g., "create a prd" or "plan this feature"). The skill asks 3–5 essential, lettered clarifying questions (problem, core actions, scope, success criteria) so you can respond compactly (e.g., "1A, 2C, 3B"). It then generates a markdown PRD with Introduction, Goals, User Stories with verifiable acceptance criteria, Functional Requirements, Non-Goals, Design/Technical considerations, Success Metrics, and Open Questions, and saves it to tasks/prd-[feature-name].md. The output is a planning/spec document only — no implementation is started.
When to use it
- Planning a new feature before design or development begins
- Starting a project and needing a concise spec for engineers or AI agents
- Converting a high-level idea into concrete user stories and acceptance criteria
- Handoff to junior developers or autonomous loops like Ralph
- When you need a reproducible PRD file saved in tasks/
Best practices
- Provide a one- or two-sentence feature summary to start; the skill will ask clarifying questions
- Answer clarifying questions using lettered options (e.g., "1A, 2C") for fastest iteration
- Be explicit about non-goals to keep scope manageable
- Ensure UI stories include the required browser verification acceptance criterion
- Review and iterate on generated PRD before turning it into implementation tasks
Example use cases
- You want a PRD for an email notifications feature and need measurable success metrics
- Converting a product manager's idea into implementable user stories for a junior dev
- Preparing a spec for an autonomous agent (Ralph) to execute until PRD items are complete
- Rapidly scoping a minimal viable version versus a full-featured implementation
- Creating consistent PRDs saved to tasks/ for tracking and automation
FAQ
The PRD is produced as a markdown (.md) file and saved to tasks/prd-[feature-name].md using a kebab-case filename based on the feature name.
How many clarifying questions will you ask?
Typically 3–5 essential, lettered questions focused on goal, target user, scope, and success criteria to avoid unnecessary back-and-forth.
