Skip to main content
blueprint-prp-create Create a PRP (Product Requirement Prompt) with research, context, and validation gates. Use when planning a feature packet for subagent execution with TDD and confidence scoring.
Zur Installation springen Skills Marktplatz Entdecken und erkunden Sie KI-Skills, die von der Community erstellt wurden.
Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.
Prompt-Details anzeigen Ein direkter Befehl überspringt den Prüf-Prompt. Prüfen Sie die Quelle, bevor Sie ihn ausführen.
npx skills add https://github.com/laurigates/claude-plugins --skill blueprint-prp-createDer Befehl bleibt in einer Zeile. Scrollen Sie horizontal, um ihn vor dem Kopieren vollständig zu prüfen.
Sie bevorzugen eine lokale Kopie? Laden Sie die Dateien herunter, die SkillsMP derzeit vorliegen.
ZIP herunterladen Herunterladen... Mehr aus diesem Repository Install, configure and troubleshoot MCP servers. Use when adding/enabling servers, editing .mcp.json, fixing OAuth, or when a server runs stale code after an upstream fix.
FinOps snapshot — org billing, workflow stats, cache usage. Use when you want a high-level view of CI spending or workflow health before diving deeper.
GitHub Actions billing, workflow efficiency, and waste analysis at org or repo level. Use when investigating CI/CD costs, wasted runs, or optimizing triggers.
Verwandte Berufe SOC
Basierend auf der SOC-Berufsklassifikation
description Create a PRP (Product Requirement Prompt) with research, context, and validation gates. Use when planning a feature packet for subagent execution with TDD and confidence scoring. args [feature-name] argument-hint Feature name for the PRP (e.g., auth-oauth2, api-rate-limiting) allowed-tools Read, Write, Glob, Bash, WebFetch, WebSearch, Task, AskUserQuestion model opus created "2025-12-16T00:00:00.000Z" modified "2026-06-18T00:00:00.000Z" reviewed "2026-02-14T00:00:00.000Z" name blueprint-prp-create
/blueprint:prp-create
Create a comprehensive PRP (Product Requirement Prompt) - a self-contained packet with all context an AI agent needs to deliver production code on first attempt.
What is a PRP? PRD + Curated Codebase Intelligence + Implementation Blueprint + Validation Gates = everything needed for reliable implementation.
Usage : /blueprint:prp-create [feature-name]
Prerequisites :
Blueprint Development initialized (docs/blueprint/ exists)
Clear understanding of the feature to implement
When to Use This Skill
Use this skill when... Use alternative when... Creating new feature implementation packet Executing an existing PRP (use /blueprint:prp-execute) Want comprehensive research and documentation Quick prototyping without formal requirements Planning for AI agent or subagent execution Solo developer implementing without research Need to document implementation approach Implementing based on existing codebase patterns
Context
Blueprint initialized: !find . -path '*/docs/blueprint/*' -maxdepth 3 -name 'manifest.json' -type f
Last PRP ID: !find . -path '*/docs/blueprint/manifest.json' -maxdepth 3 -exec jq -r '.id_registry.last_prp // 0' {} +
Curated rules available: !find . -maxdepth 3 -path '*/.claude/rules/*' -type f -name "*.md"
Existing PRDs: !find . -path '*/docs/prds/*' -name "*.md" -type f
Parameters
Parse $ARGUMENTS:
feature-name (required): Kebab-case name for PRP (e.g., auth-oauth2, api-rate-limiting)
Used for filename and document ID generation
Execution
Execute the complete PRP creation workflow:
Step 1: Verify prerequisites and understand requirements
If Blueprint not initialized → Error: "Run /blueprint:init first"
Ask user to describe the feature: "What feature needs to be implemented?"
Capture: Goal, why it matters, success criteria
Ask if this implements an existing PRD: "Does this implement an existing PRD or is it standalone?"
If PRD chosen → Store PRD ID for linking
Determine feature type (API endpoint, database, UI, integration, etc.)
Step 2: Research codebase patterns Use Explore agent to find existing patterns:
Similar features already implemented (identify existing patterns to follow)
Relevant file locations and integration points
Testing patterns used for similar features
Architecture decisions that affect this feature
Store findings with specific file paths and line numbers.
Step 3: Research external documentation For relevant libraries/frameworks, gather:
Official documentation sections (capture URLs with specific sections)
Known issues and gotchas from Stack Overflow / GitHub discussions
Best practices from documentation
Common implementation patterns
Use WebSearch/WebFetch as needed. Create or update curated rule entries if needed (see REFERENCE.md ).
Step 4: Generate PRP document ID and structure Generate next PRP ID from manifest:
Extract id_registry.last_prp from manifest.json
Next ID = last_prp + 1 (format: PRP-NNN)
Create docs/prps/[feature-name].md with frontmatter and sections (see REFERENCE.md ).
Step 5: Draft PRP content with research findings
Goal & Why : One-sentence goal, business justification, target users, prioritySuccess Criteria : Specific, testable acceptance criteria with metricsContext :
Documentation references (URLs with specific sections)
Curated rule references (links to .claude/rules/ library/pattern entries)
Codebase Intelligence : File paths, code snippets with line numbers, patterns to followKnown Gotchas : Critical warnings with mitigations
Implementation Blueprint :
Architecture decision with rationale
Task breakdown (Required / Deferred / Nice-to-Have categories)
Order of implementation
TDD Requirements : Test strategy and critical test casesValidation Gates : Executable commands (linting, type-checking, tests, coverage) Critical : All tasks must be explicitly categorized (see REFERENCE.md ).
Step 6: Score confidence across dimensions Rate each dimension 1-10:
Dimension Criteria Context Completeness Are all file paths, code snippets, and references explicit? Implementation Clarity Is pseudocode clear enough for AI to follow? Gotchas Documented Are all known pitfalls documented with mitigations? Validation Coverage Are all validation gates with executable commands?
Calculate overall score as average of dimensions. Target: 7+ for execution, 9+ for subagent delegation.
If score < 7 → Return to Steps 2-3 to fill gaps.
Step 7: Review and validate completeness Update docs/blueprint/manifest.json ID registry with new PRP entry.
Step 8: Report PRP and prompt for next action
PRP ID and location
Feature summary and approach
Context collected (curated rules, patterns, documentation)
Linked documents (source PRD if applicable)
Confidence score with breakdown
Any gaps if score < 7
If confidence >= 7 , offer user choices:
Execute PRP now → /blueprint:prp-execute [feature-name]
Create work-order for subagent → /blueprint:work-order
Review and refine → Show file location and gaps
Done for now → Exit (save for later execution)
If confidence < 7 , offer user choices:
Research more context → Use Explore agent for gaps
Create curated rule entries → /blueprint:curate-docs
Execute anyway (risky) → Proceed with warning
Done for now → Save incomplete PRP
Agentic Optimizations Context Command Check blueprint init test -f docs/blueprint/manifest.json && echo "YES" || echo "NO"Next PRP ID jq -r '.id_registry.last_prp // 0' docs/blueprint/manifest.json | awk '{print $1+1}'List existing PRPs ls -1 docs/prps/ 2>/dev/null | wc -lSearch for patterns Use Explore agent instead of manual grep Fast research Use existing curated rules rather than fetching docs again
For PRP document structure, task categorization, review checklists, and curated-rule creation guidance, see REFERENCE.md .
