prp-generator

Name: prp-generator
Author: henkisdabro

30installs9forks

How to install prp-generator?

henkisdabro/wookstar-claude-plugins/prp-generator

$npx -y skills add henkisdabro/wookstar-claude-plugins --skill prp-generator

Installs into the current project.

Summary

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, a

Files · 1

View on GitHub

SKILL.md

1	# PRP Generator
2
3	## Overview
4
5	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.
6
7	## When to Use
8
9	- User requests a PRP, PRD, or detailed implementation plan
10	- User asks to "plan out" or "design" a complex feature
11	- Beginning significant feature development that benefits from structured planning
12	- User provides a feature description file and asks for implementation guidance
13
14	## Core Principle
15
16	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.
17
18	## Workflow
19
20	### Phase 1: Understand the Feature
21
22	1. Read the feature request - if a file path is given, read it completely; if verbal, clarify requirements
23	2. Clarify ambiguities - use AskUserQuestion for unclear requirements, confirm tech stack, verify integration points
24	3. Identify the core problem being solved and acceptance criteria
25
26	### Phase 2: Codebase Analysis (Mandatory)
27
28	Goal: Understand existing patterns, conventions, and integration points.
29
30	Systematically analyse the codebase across five dimensions:
31
32	\| Area \| What to Capture \|
33	\|------\|----------------\|
34	\| Similar features \| File paths, line numbers, code snippets, adaptations needed \|
35	\| Architecture \| Directory conventions, component organisation, state management, API patterns \|
36	\| Coding conventions \| TypeScript usage, component patterns, styling, import ordering, naming \|
37	\| Test patterns \| Framework, file naming, mock strategies, coverage expectations \|
38	\| Configuration \| Dependencies, build setup, path aliases, TypeScript settings \|
39
40	For detailed sub-steps, examples, and documentation templates, see [references/codebase-analysis-guide.md](references/codebase-analysis-guide.md).
41
42	Also refer to [references/research_methodology.md](references/research_methodology.md) for the full research process.
43
44	### Phase 3: External Research (Mandatory)
45
46	Goal: Find best practices, documentation, examples, and gotchas.
47
48	Research across four areas:
49
50	\| Area \| Key Actions \|
51	\|------\|------------\|
52	\| Library documentation \| Find official docs for the SPECIFIC version from package.json; note version-specific gotchas \|
53	\| Implementation examples \| Search GitHub, StackOverflow, official examples; prefer recent, production-grade code \|
54	\| Best practices \| Search "[technology] best practices [current year]"; check OWASP for security \|
55	\| Performance and security \| Bundle size implications, runtime patterns, vulnerabilities, accessibility \|
56
57	Always document exact URLs, versions, and specific sections. See [references/research_methodology.md](references/research_methodology.md) for detailed guidance.
58
59	### Phase 4: Ultra-Thinking (Critical)
60
61	STOP AND THINK DEEPLY BEFORE WRITING THE PRP.
62
63	Analyse integration points, implementation ordering, validation strategy, and context completeness. Verify the PRP will enable one-pass implementation without questions.
64
65	For the full set of analysis questions and the quality checklist, see [references/quality-assessment.md](references/quality-assessment.md).
66
67	### Phase 5: Generate the PRP
68
69	Use [assets/prp_template.md](assets/prp_template.md) as the base structure. Populate all sections:
70
71	1. Metadata - feature name, timeline, confidence score (1-10), date
72	2. Executive Summary - 2-3 sentences with core value proposition
73	3. Research Findings - codebase analysis (file:line refs) and external research (URLs, versions)
74	4. Technical Specification - architecture, components, data models, API endpoints
75	5. Implementation Blueprint - prerequisites, step-by-step with pseudocode, file changes, error handling, edge cases
76	6. Testing Strategy - unit, integration, and manual testing approaches
77	7. Validation Gates - must be EXECUTABLE commands (e.g. `npm run test && npm run build`)
78	8. Success Criteria - clear, measurable checklist
79
80	### Phase 6: Quality Scoring
81
82	Score the PRP for one-pass implementation success:
83
84	\| Score \| Meaning \|
85	\|-------\|---------\|
86	\| 9-10 \| Exceptionally detailed, all context included, clear path, executable gates \|
87	\| 7-8 \| Very good, minor gaps, mostly clear implementation path \|
88	\| 5-6 \| Adequate, some ambiguity, may require clarifi

People who liked this also viewed

6 picks

Type

prp-generator

30installs9forks

View on GitHub

How to install prp-generator?

henkisdabro/wookstar-claude-plugins/prp-generator

$npx -y skills add henkisdabro/wookstar-claude-plugins --skill prp-generator

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# PRP Generator
2
3	## Overview
4
5	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.
6
7	## When to Use
8
9	- User requests a PRP, PRD, or detailed implementation plan
10	- User asks to "plan out" or "design" a complex feature
11	- Beginning significant feature development that benefits from structured planning
12	- User provides a feature description file and asks for implementation guidance
13
14	## Core Principle
15
16	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.
17
18	## Workflow
19
20	### Phase 1: Understand the Feature
21
22	1. Read the feature request - if a file path is given, read it completely; if verbal, clarify requirements
23	2. Clarify ambiguities - use AskUserQuestion for unclear requirements, confirm tech stack, verify integration points
24	3. Identify the core problem being solved and acceptance criteria
25
26	### Phase 2: Codebase Analysis (Mandatory)
27
28	Goal: Understand existing patterns, conventions, and integration points.
29
30	Systematically analyse the codebase across five dimensions:
31
32	\| Area \| What to Capture \|
33	\|------\|----------------\|
34	\| Similar features \| File paths, line numbers, code snippets, adaptations needed \|
35	\| Architecture \| Directory conventions, component organisation, state management, API patterns \|
36	\| Coding conventions \| TypeScript usage, component patterns, styling, import ordering, naming \|
37	\| Test patterns \| Framework, file naming, mock strategies, coverage expectations \|
38	\| Configuration \| Dependencies, build setup, path aliases, TypeScript settings \|
39
40	For detailed sub-steps, examples, and documentation templates, see [references/codebase-analysis-guide.md](references/codebase-analysis-guide.md).
41
42	Also refer to [references/research_methodology.md](references/research_methodology.md) for the full research process.
43
44	### Phase 3: External Research (Mandatory)
45
46	Goal: Find best practices, documentation, examples, and gotchas.
47
48	Research across four areas:
49
50	\| Area \| Key Actions \|
51	\|------\|------------\|
52	\| Library documentation \| Find official docs for the SPECIFIC version from package.json; note version-specific gotchas \|
53	\| Implementation examples \| Search GitHub, StackOverflow, official examples; prefer recent, production-grade code \|
54	\| Best practices \| Search "[technology] best practices [current year]"; check OWASP for security \|
55	\| Performance and security \| Bundle size implications, runtime patterns, vulnerabilities, accessibility \|
56
57	Always document exact URLs, versions, and specific sections. See [references/research_methodology.md](references/research_methodology.md) for detailed guidance.
58
59	### Phase 4: Ultra-Thinking (Critical)
60
61	STOP AND THINK DEEPLY BEFORE WRITING THE PRP.
62
63	Analyse integration points, implementation ordering, validation strategy, and context completeness. Verify the PRP will enable one-pass implementation without questions.
64
65	For the full set of analysis questions and the quality checklist, see [references/quality-assessment.md](references/quality-assessment.md).
66
67	### Phase 5: Generate the PRP
68
69	Use [assets/prp_template.md](assets/prp_template.md) as the base structure. Populate all sections:
70
71	1. Metadata - feature name, timeline, confidence score (1-10), date
72	2. Executive Summary - 2-3 sentences with core value proposition
73	3. Research Findings - codebase analysis (file:line refs) and external research (URLs, versions)
74	4. Technical Specification - architecture, components, data models, API endpoints
75	5. Implementation Blueprint - prerequisites, step-by-step with pseudocode, file changes, error handling, edge cases
76	6. Testing Strategy - unit, integration, and manual testing approaches
77	7. Validation Gates - must be EXECUTABLE commands (e.g. `npm run test && npm run build`)
78	8. Success Criteria - clear, measurable checklist
79
80	### Phase 6: Quality Scoring
81
82	Score the PRP for one-pass implementation success:
83
84	\| Score \| Meaning \|
85	\|-------\|---------\|
86	\| 9-10 \| Exceptionally detailed, all context included, clear path, executable gates \|
87	\| 7-8 \| Very good, minor gaps, mostly clear implementation path \|
88	\| 5-6 \| Adequate, some ambiguity, may require clarifi

People who liked this also viewed

6 picks

Type