Menu
Plan features interactively. Asks clarifying questions, then generates a detailed PRD document.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
A strict editorial reviewer that checks writing principles inspired by George Orwell's "Politics and the English Language" rules and Matthew Butterick's Practical Typography. Use this skill whenever the user says "red pen", "check my prose", "edit this for clarity", "typography check", "tighten this up", "review this draft for style", or wants a rigorous line-edit focused on cutting flab, killing dead metaphors, fixing passive voice, and correcting typographic errors like straight quotes, wrong dashes, and double spaces. Also use when the user asks you to be a "tough editor", "strict editor", or "copy editor", or wants feedback on prose quality rather than content or structure.
Converts a PRD markdown file into GitHub Issues (parent + sub-issues) for ralph-github-start-loop to execute. Use when user wants to push PRD stories to GitHub Issues.
Converts a PRD or plan markdown file into prd.json format for ralph-json-start-loop to execute autonomously. Use when user wants to convert a PRD or plan to JSON stories.
Runs the Ralph autonomous loop. Executes stories from prds/*.json using git worktrees.
Reviews PR comments from GitHub (Copilot, reviewers), evaluates against actual code, replies with reasoning, and resolves threads. Triggers on "review pr comments", "address pr feedback", "fix pr comments", or "review copilot suggestions".
Guides creation of OpenGraph and Twitter share images using next/og ImageResponse. Covers layout patterns, custom fonts, avatars, title case, and Satori rules. Use when building OG images, Twitter cards, or social previews.
| name | create-prd |
| description | Plan features interactively. Asks clarifying questions, then generates a detailed PRD document. |
Generate a Product Requirements Document through interactive planning.
Read the user's feature request. If unclear, ask for a brief description.
Ask 3-5 clarifying questions to understand scope and requirements.
Format with lettered options:
1. Who is the primary user?
A) Logged-in users only
B) All visitors
C) Admin users
2. Should this persist across sessions?
A) Yes, save to database
B) No, session only
User can respond with combinations like "1A, 2B".
After answers, create a detailed PRD with these sections:
# PRD: [Feature Name]
## Introduction
Brief overview of the feature and why it's needed.
## Goals
- Primary goal
- Secondary goals
## User Stories
### [Story Title]
**Description:** As a [user], I want [action] so that [benefit].
**Acceptance Criteria:**
- [ ] Specific, verifiable criterion
- [ ] Another criterion
- [ ] Typecheck passes
- [ ] (UI changes) Verify in browser
## Functional Requirements
1. Requirement one
2. Requirement two
## Non-Goals
What this feature explicitly won't do.
## Design Considerations
UI/UX notes, mockup descriptions.
## Technical Considerations
Architecture notes, dependencies, potential challenges.
## Success Metrics
How to measure if this feature is successful.
## Open Questions
Any unresolved decisions.
Save to prds/[feature-name].md (create prds/ directory if needed).
PRD saved to prds/[feature-name].md
Next: Run /create-prd-json to convert to executable format.