跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
搜索与研究

prp-generator

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. Do NOT use for client discovery, requirements gathering, or scope definition - those need a separate clarification pass before the PRP step.

henkisdabro · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

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

技能说明


name: prp-generator description: 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. Do NOT use for client discovery, requirements gathering, or scope definition - those need a separate clarification pass before the PRP step.

PRP Generator

Overview

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.

When to Use

  • User requests a PRP, PRD, or detailed implementation plan
  • User asks to "plan out" or "design" a complex feature
  • Beginning significant feature development that benefits from structured planning
  • User provides a feature description file and asks for implementation guidance

Core Principle

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.

Workflow

Phase 1: Understand the Feature

  1. Read the feature request - if a file path is given, read it completely; if verbal, clarify requirements
  2. Clarify ambiguities - use AskUserQuestion for unclear requirements, confirm tech stack, verify integration points
  3. Identify the core problem being solved and acceptance criteria

Phase 2: Codebase Analysis (Mandatory)

Goal: Understand existing patterns, conventions, and integration points.

Systematically analyse the codebase across five dimensions:

AreaWhat to Capture
Similar featuresFile paths, line numbers, code snippets, adaptations needed
ArchitectureDirectory conventions, component organisation, state management, API patterns
Coding conventionsTypeScript usage, component patterns, styling, import ordering, naming
Test patternsFramework, file naming, mock strategies, coverage expectations
ConfigurationDependencies, 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.

Phase 3: External Research (Mandatory)

Goal: Find best practices, documentation, examples, and gotchas.

Research across four areas:

AreaKey Actions
Library documentationFind official docs for the SPECIFIC version from package.json; note version-specific gotchas
Implementation examplesSearch GitHub, StackOverflow, official examples; prefer recent, production-grade code
Best practicesSearch "[technology] best practices [current year]"; check OWASP for security
Performance and securityBundle size implications, runtime patterns, vulnerabilities, accessibility

Always document exact URLs, versions, and specific sections. See references/research_methodology.md for detailed guidance.

Phase 4: Ultra-Thinking (Critical)

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.

Phase 5: Generate the PRP

Use assets/prp_template.md as the base structure. Populate all sections:

  1. Metadata - feature name, timeline, confidence score (1-10), date
  2. Executive Summary - 2-3 sentences with core value proposition
  3. Research Findings - codebase analysis (file:line refs) and external research (URLs, versions)
  4. Technical Specification - architecture, components, data models, API endpoints
  5. Implementation Blueprint - prerequisites, step-by-step with pseudocode, file changes, error handling, edge cases
  6. Testing Strategy - unit, integration, and manual testing approaches
  7. Validation Gates - must be EXECUTABLE commands (e.g. npm run test && npm run build)
  8. Success Criteria - clear, measurable checklist

Phase 6: Quality Scoring

Score the PRP for one-pass implementation success:

ScoreMeaning
9-10Exceptionally detailed, all context included, clear path, executable gates
7-8Very good, minor gaps, mostly clear implementation path
5-6Adequate, some ambiguity, may require clarification
3-4Incomplete research, missing context, unclear path
1-2Insufficient for implementation

If score is below 7: Go back and improve the PRP before delivering.

Phase 7: Save and Deliver

  1. Save the PRP to PRPs/[feature-name].md (kebab-case, create directory if needed)
  2. Deliver summary to user with: brief feature summary, file location, confidence score with rationale, and next steps

Common Pitfalls

PitfallBadGood
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 researchSkipping codebase analysisThoroughly document existing patterns
阅读完整来源 ↗