blueprint-prp-execute

/blueprint:prp-execute

Execute a PRP (Product Requirement Prompt) with systematic implementation, validation gates, TDD workflow, and quality assurance.

Usage: /blueprint:prp-execute [prp-name]

Prerequisites:

• PRP exists in docs/prps/[prp-name].md
• Confidence score >= 7 (if lower, suggest /blueprint:prp-create refinement)

For detailed report templates, deferred items workflow, feature tracker sync, and error handling patterns, see REFERENCE.md.

When to Use This Skill

Use this skill when...	Use alternative when...
Ready to implement a planned feature from a PRP	PRP is not yet ready (confidence < 7)
Want to execute with full validation and TDD workflow	Implementing ad-hoc features without documentation
Need feature tracker and GitHub issue tracking	Working on isolated bug fixes
Want automatic progress reporting and deferred items tracking	Quick prototyping without formal tracking

Context

• PRP file path: !find . -maxdepth 1 -name \'docs/prps/${1:-unknown}.md\'
• PRP confidence score: !find . -path '*/docs/prps/*' -maxdepth 3 -name "${1:-unknown}.md" -exec grep -m1 "^confidence:" {} +
• Feature tracker enabled: !find . -path '*/docs/blueprint/*' -maxdepth 3 -name 'feature-tracker.json' -type f
• Current branch: !git rev-parse --abbrev-ref HEAD
• Uncommitted changes: !git status --porcelain

Parameters

Parse $ARGUMENTS:

• prp-name (required): Name of PRP file in docs/prps/ (without .md extension)
  • Example: feature-auth-oauth2 → loads docs/prps/feature-auth-oauth2.md

Execution

Execute the complete PRP implementation workflow:

Step 1: Load and validate PRP

1. Read PRP file: docs/prps/{prp-name}.md
2. Extract confidence score from frontmatter
3. If confidence < 7 → Error: "PRP confidence too low. Run /blueprint:prp-create {prp-name} to refine"
4. If confidence >= 9 → Offer delegation: "This PRP has high confidence. Execute now (current session) or create work-order for delegation?"
   • If work-order chosen → Run /blueprint:work-order --from-prp {prp-name} and exit
   • If delegation to multiple subagents chosen → Create focused work-orders per module from Implementation Blueprint and exit
5. Continue to Step 2 if executing now OR confidence 7-8
6. Load all referenced curated rule entries (.claude/rules/) for context
7. Parse the Implementation Blueprint into an ordered task checklist (dependencies first); track it with TodoWrite when the session has the task tools, otherwise carry it as a checklist in the response (see .claude/rules/agentic-permissions.md § Task-tool availability)