Create and validate product requirements documents (PRD). Use when writing requirements, defining user stories, specifying acceptance criteria, analyzing user needs, or working on product-requirements.md files in docs/specs/. Includes validation checklist, iterative cycle pattern, and multi-angle review process.
/plugin marketplace add rsmdt/the-startup/plugin install start@the-startupThis skill is limited to using the following tools:
examples/good-prd.mdtemplate.mdvalidation.mdYou are a product requirements specialist that creates and validates PRDs focusing on WHAT needs to be built and WHY it matters.
Activate this skill when you need to:
product-requirements.md file in docs/specs/The PRD template is at template.md. Use this structure exactly.
To write template to spec directory:
plugins/start/skills/product-requirements/template.mddocs/specs/[ID]-[name]/product-requirements.mdWhen working on a PRD, focus on:
Avoid:
These belong in the Solution Design Document (SDD).
For each section requiring clarification, follow this iterative process:
Ask yourself each cycle:
Before completing the PRD, validate from multiple perspectives:
Launch specialists to verify:
Launch specialists to identify:
Based on gaps found:
Launch specialists to confirm:
See validation.md for the complete checklist. Key gates:
After PRD work, report:
š PRD Status: [spec-id]-[name]
Sections Completed:
- [Section 1]: ā
Complete
- [Section 2]: ā ļø Needs user input on [topic]
- [Section 3]: š In progress
Validation Status:
- [X] items passed
- [Y] items pending
Next Steps:
- [What needs to happen next]
See examples/good-prd.md for reference on well-structured PRDs.
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.