From toby-essentials
Generates structured Product Requirements Documents (PRDs) by gathering project context from files and commits, asking 3-5 clarifying questions with lettered options, and producing sections like user stories, functional requirements, non-goals, and success metrics.
npx claudepluginhub tobyilee/toby-plugins --plugin toby-essentialsThis skill uses the workspace's default tool permissions.
Generate clear, actionable Product Requirements Documents suitable for implementation by developers or AI agents.
Generates Product Requirements Documents (PRDs) for features via clarifying questions on goals, users, and scope. Structures into user stories, requirements; saves to tasks/prd-[feature].md.
Generates structured PRDs with problem, context, solution, user stories, acceptance criteria, metrics, risks, and out-of-scope items. Iteratively gathers info via questions, reviews docs/issues/templates.
Generates Product Requirements Documents (PRDs) with user stories, success metrics, scope, technical considerations, and risks for product features.
Share bugs, ideas, or general feedback.
Generate clear, actionable Product Requirements Documents suitable for implementation by developers or AI agents.
Create structured PRDs through a collaborative process: gather context, ask clarifying questions, then produce a comprehensive requirements document. The PRD serves as the bridge between an idea and implementation.
Important: Do NOT start implementing. Only create the PRD.
Before asking questions, explore the project:
Ask 3-5 essential questions where the initial prompt is ambiguous. Focus on:
Format questions with lettered options for quick response:
1. What is the primary goal of this feature?
A. Improve user onboarding experience
B. Increase user retention
C. Reduce support burden
D. Other: [please specify]
2. What is the scope?
A. Minimal viable version
B. Full-featured implementation
C. Just the backend/API
D. Just the UI
This enables responses like "1A, 2C, 3B" for rapid iteration. Indent the options under each question.
Produce the PRD with these sections (scale each section to its complexity):
For detailed section templates and formatting guidance, consult references/section-templates.md.
Save the PRD to tasks/prd-[feature-name].md (kebab-case).
Before saving, verify:
The PRD reader may be a junior developer or AI agent:
Each story follows this structure:
### US-001: [Title]
**Description:** As a [user], I want [feature] so that [benefit].
**Acceptance Criteria:**
- [ ] Specific verifiable criterion
- [ ] Another criterion
- [ ] Typecheck/lint passes
- [ ] **[UI stories only]** Verify in browser
Acceptance criteria must be verifiable. "Works correctly" is bad. "Button shows confirmation dialog before deleting" is good.
references/section-templates.md - Detailed section templates with formatting guidanceexamples/task-priority-prd.md - Complete example PRD for reference