菜单
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.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/laurigates/claude-plugins --skill blueprint-prp-create命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
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.
正在显示 SKILL.md
基于 SOC 职业分类
| 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 |
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:
docs/blueprint/ exists)| 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 |
find . -path '*/docs/blueprint/*' -maxdepth 3 -name 'manifest.json' -type ffind . -path '*/docs/blueprint/manifest.json' -maxdepth 3 -exec jq -r '.id_registry.last_prp // 0' {} +find . -maxdepth 3 -path '*/.claude/rules/*' -type f -name "*.md"find . -path '*/docs/prds/*' -name "*.md" -type fParse $ARGUMENTS:
feature-name (required): Kebab-case name for PRP (e.g., auth-oauth2, api-rate-limiting)
Execute the complete PRP creation workflow:
/blueprint:init first"Use Explore agent to find existing patterns:
Store findings with specific file paths and line numbers.
For relevant libraries/frameworks, gather:
Use WebSearch/WebFetch as needed. Create or update curated rule entries if needed (see REFERENCE.md).
Generate next PRP ID from manifest:
id_registry.last_prp from manifest.jsonPRP-NNN)Create docs/prps/[feature-name].md with frontmatter and sections (see REFERENCE.md).
Fill all required sections (see REFERENCE.md):
.claude/rules/ library/pattern entries)Critical: All tasks must be explicitly categorized (see REFERENCE.md).
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.
Verify checklist (see REFERENCE.md):
Update docs/blueprint/manifest.json ID registry with new PRP entry.
Display summary showing:
If confidence >= 7, offer user choices:
/blueprint:prp-execute [feature-name]/blueprint:work-orderIf confidence < 7, offer user choices:
/blueprint:curate-docs| 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 -l |
| Search 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.