Back to Skills

prp-generator

verified

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.

View on GitHub

Marketplace

wookstar-claude-plugins

henkisdabro/wookstar-claude-plugins

Plugin

developer

development

Repository

henkisdabro/wookstar-claude-plugins
16stars

plugins/developer/skills/prp-generator/SKILL.md

Last Verified

January 20, 2026

Install Skill

Select agents to install to:

Scope:
npx add-skill https://github.com/henkisdabro/wookstar-claude-plugins/blob/main/plugins/developer/skills/prp-generator/SKILL.md -a claude-code --skill prp-generator

Installation paths:

Claude
.claude/skills/prp-generator/
Powered by add-skill CLI

Instructions

# PRP Generator

## Overview

This 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.

## When to Use This Skill

Invoke this skill when:
- User requests a PRP or PRD (Product Requirement Plan/Document)
- User wants a detailed implementation plan for a new feature
- User asks to "plan out" or "design" a complex feature
- Beginning a significant feature development that would benefit from structured planning
- User provides a feature description file and asks for implementation guidance

## Core Principle

**Context is Everything**: The AI agent implementing your PRP only receives:
1. The PRP content you create
2. Training data knowledge
3. Access to the codebase
4. WebSearch capabilities

Therefore, your PRP must be self-contained with all necessary context, specific references, and executable validation gates.

## Workflow

### Phase 1: Understanding the Feature

1. **Read the Feature Request**
   - If user provides a feature file path, read it completely
   - If user provides verbal description, clarify requirements by asking:
     - What is the user trying to accomplish?
     - What are the acceptance criteria?
     - Are there any specific constraints or requirements?
   - Identify the core problem being solved

2. **Clarify Ambiguities**
   - Use AskUserQuestion tool for any unclear requirements
   - Confirm technology stack assumptions
   - Verify integration points
   - Ask about specific patterns to follow if not obvious

### Phase 2: Codebase Analysis (Mandatory)

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

Refer to `references/research_methodology.md` for detailed guidance, but the core steps are:

1. **Search for Similar Features**
   ```
   Use Grep to search for:
   - Similar component names
   -

Validation Details

Front Matter
Required Fields
Valid Name Format
Valid Description
Has Sections
Allowed Tools
Instruction Length:
11653 chars