Generate comprehensive Product Requirement Plans (PRPs) for feature implementation with thorough codebase analysis and external research. Use when the user requests a PRP, PRD, or detailed implementation plan for a new feature. Conducts systematic research, identifies patterns, and creates executable validation gates for one-pass implementation success.
/plugin marketplace add henkisdabro/wookstar-claude-code-plugins/plugin install developer@wookstar-claude-code-pluginsThis skill inherits all available tools. When active, it can use any tool Claude has access to.
assets/prp_template.mdreferences/research_methodology.mdThis skill generates comprehensive Product Requirement Plans (PRPs) that enable AI agents to implement features in a single pass with high success rates. The skill combines systematic codebase analysis with external research to create detailed, context-rich implementation blueprints.
Invoke this skill when:
Context is Everything: The AI agent implementing your PRP only receives:
Therefore, your PRP must be self-contained with all necessary context, specific references, and executable validation gates.
Read the Feature Request
Clarify Ambiguities
Goal: Understand existing patterns, conventions, and integration points
Refer to references/research_methodology.md for detailed guidance, but the core steps are:
Search for Similar Features
Use Grep to search for:
- Similar component names
- Similar functionality keywords
- Similar UI patterns
- Similar API endpoints
Document findings with:
Identify Architectural Patterns
Example findings:
Pattern: Feature-based directory structure
Location: src/features/
Application: Create src/features/[new-feature]/
Document Coding Conventions
Example:
Convention: Named exports for all components
Example: export function UserProfile() { ... }
Found in: src/components/*.tsx
Study Test Patterns
Document:
Framework: Vitest + @testing-library/react
Pattern: Co-located tests with *.test.tsx
Example: src/components/Button/Button.test.tsx
Mock Strategy: Use vi.fn() for functions, MSW for HTTP
Check Project Configuration
package.json for dependencies and scriptstsconfig.json for TypeScript settingsDocument:
Build Tool: Vite 5.x
Path Aliases: '@/' → 'src/', '@components/' → 'src/components/'
TypeScript: Strict mode enabled
Goal: Find best practices, documentation, examples, and gotchas
Refer to references/research_methodology.md for detailed guidance, but the core steps are:
Search for Library Documentation
Example output:
Library: @tanstack/react-query
Version: 5.28.0 (from package.json)
Docs: https://tanstack.com/query/latest/docs/react/overview
Key Sections:
- Queries: https://tanstack.com/query/latest/docs/react/guides/queries
- Mutations: https://tanstack.com/query/latest/docs/react/guides/mutations
Gotchas:
- Query keys must be arrays
- Automatic refetching on window focus
- Default staleTime is 0
Find Implementation Examples
Document:
Example: Form validation with React Hook Form + Zod
Source: https://github.com/react-hook-form/react-hook-form/tree/master/examples/V7/zodResolver
Relevance: Shows exact integration pattern needed
Key Takeaway: Use zodResolver from @hookform/resolvers
Research Best Practices
Document:
Practice: Input sanitization for user content
Why: Prevent XSS attacks
How: Use DOMPurify before rendering HTML
Reference: https://owasp.org/www-community/attacks/xss/
Warning: NEVER use dangerouslySetInnerHTML without sanitization
Performance & Security Research
Document specific URLs and recommendations
STOP AND THINK DEEPLY BEFORE WRITING THE PRP
This is the most important phase. Spend significant time analyzing:
Integration Analysis
Implementation Path Planning
Validation Strategy
Context Completeness Check Ask yourself:
Quality Assessment
Use the template from assets/prp_template.md as the base structure, and populate it with:
Metadata Section
Executive Summary
Research Findings
Technical Specification
Implementation Blueprint
Testing Strategy
Validation Gates Must be EXECUTABLE commands:
# Type checking
npm run type-check
# Linting
npm run lint
# Tests
npm run test
# Build
npm run build
Success Criteria
Score the PRP on a scale of 1-10 for one-pass implementation success:
Scoring Criteria:
If score is below 7: Go back and improve the PRP before delivering it.
Determine Feature Name
Save the PRP
Save to: PRPs/[feature-name].md
If PRPs directory doesn't exist, create it:
mkdir -p PRPs
Deliver Summary to User Provide:
Before delivering the PRP, verify:
Vague References
Missing Version Information
Non-Executable Validation Gates
Generic Best Practices
Incomplete Research
Missing Gotchas
User Request:
"Create a PRP for adding dark mode support to the application"
Your Response:
PRPs/dark-mode-support.mdassets/prp_template.md - Base template for all PRPsreferences/research_methodology.md - Detailed research guidance and best practicesThis 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 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 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.