From developer
Generates Product Requirement Plans (PRPs) for feature implementation via systematic codebase analysis and external research. Use when requesting PRP, PRD, or detailed implementation plans.
npx claudepluginhub henkisdabro/wookstar-claude-plugins --plugin developerThis skill uses the workspace's default tool permissions.
Generates comprehensive Product Requirement Plans (PRPs) that enable AI agents to implement features in a single pass. Combines systematic codebase analysis with external research to create detailed, context-rich implementation blueprints.
Creates PRP (Product Requirement Prompt) combining PRD, codebase pattern research, external documentation, implementation blueprint, and validation gates for AI agent feature implementation.
Generates a structured Product Requirements Document (PRD) from feature descriptions. Analyzes codebase (package.json, configs, README), processes references, asks clarifying questions, saves to .plans/. Use for new feature planning.
Generates Product Requirements Documents (PRDs) for new features via phased approach: discovery, codebase exploration with agents, clarifying questions. Useful for feature planning or project starts.
Share bugs, ideas, or general feedback.
Generates comprehensive Product Requirement Plans (PRPs) that enable AI agents to implement features in a single pass. Combines systematic codebase analysis with external research to create detailed, context-rich implementation blueprints.
Context is Everything: The implementing agent only receives the PRP content, training data knowledge, codebase access, and WebSearch. Your PRP must be self-contained with all necessary context, specific references, and executable validation gates.
Goal: Understand existing patterns, conventions, and integration points.
Systematically analyse the codebase across five dimensions:
| Area | What to Capture |
|---|---|
| Similar features | File paths, line numbers, code snippets, adaptations needed |
| Architecture | Directory conventions, component organisation, state management, API patterns |
| Coding conventions | TypeScript usage, component patterns, styling, import ordering, naming |
| Test patterns | Framework, file naming, mock strategies, coverage expectations |
| Configuration | Dependencies, build setup, path aliases, TypeScript settings |
For detailed sub-steps, examples, and documentation templates, see references/codebase-analysis-guide.md.
Also refer to references/research_methodology.md for the full research process.
Goal: Find best practices, documentation, examples, and gotchas.
Research across four areas:
| Area | Key Actions |
|---|---|
| Library documentation | Find official docs for the SPECIFIC version from package.json; note version-specific gotchas |
| Implementation examples | Search GitHub, StackOverflow, official examples; prefer recent, production-grade code |
| Best practices | Search "[technology] best practices [current year]"; check OWASP for security |
| Performance and security | Bundle size implications, runtime patterns, vulnerabilities, accessibility |
Always document exact URLs, versions, and specific sections. See references/research_methodology.md for detailed guidance.
STOP AND THINK DEEPLY BEFORE WRITING THE PRP.
Analyse integration points, implementation ordering, validation strategy, and context completeness. Verify the PRP will enable one-pass implementation without questions.
For the full set of analysis questions and the quality checklist, see references/quality-assessment.md.
Use assets/prp_template.md as the base structure. Populate all sections:
npm run test && npm run build)Score the PRP for one-pass implementation success:
| Score | Meaning |
|---|---|
| 9-10 | Exceptionally detailed, all context included, clear path, executable gates |
| 7-8 | Very good, minor gaps, mostly clear implementation path |
| 5-6 | Adequate, some ambiguity, may require clarification |
| 3-4 | Incomplete research, missing context, unclear path |
| 1-2 | Insufficient for implementation |
If score is below 7: Go back and improve the PRP before delivering.
PRPs/[feature-name].md (kebab-case, create directory if needed)| Pitfall | Bad | Good |
|---|---|---|
| Vague references | "There's a similar component somewhere" | "See UserProfile at src/components/UserProfile.tsx:45-67" |
| Missing versions | "Use React Query" | "Use @tanstack/react-query v5.28.0" |
| Non-executable gates | "Run tests and make sure they pass" | npm run test && npm run build |
| Generic advice | "Follow React best practices" | "Use named exports (see src/components/Button.tsx:1)" |
| Incomplete research | Skipping codebase analysis | Thoroughly document existing patterns |
| Missing gotchas | Assuming smooth implementation | Document known issues and edge cases |
User: "Create a PRP for adding dark mode support to the application"
PRPs/dark-mode-support.md| Resource | Description |
|---|---|
| assets/prp_template.md | Base template for all PRPs |
| references/research_methodology.md | Detailed research guidance and best practices |
| references/codebase-analysis-guide.md | Detailed codebase analysis sub-steps and examples |
| references/quality-assessment.md | Ultra-thinking analysis questions and quality checklist |