blueprint-prp-execute
Execute a PRP with validation loop, TDD, and quality gates. Use when asked to execute a PRP, run a planned feature from docs/prps/, or delegate a PRP to subagents.
How do I install this agent skill?
npx skills add https://github.com/laurigates/claude-plugins --skill blueprint-prp-executeIs this agent skill safe to install?
- Gen Agent Trust Hubwarn
The skill automates feature implementation workflows but contains a command injection vulnerability where user-supplied arguments are executed at load time. Additionally, it executes arbitrary commands defined in external requirement files, which poses a risk if those files are malicious.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
- Runlayerpass
1/2 files flagged
What does this agent skill do?
/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-createrefinement)
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 indocs/prps/(without .md extension)- Example:
feature-auth-oauth2→ loadsdocs/prps/feature-auth-oauth2.md
- Example:
Execution
Execute the complete PRP implementation workflow:
Step 1: Load and validate PRP
- Read PRP file:
docs/prps/{prp-name}.md - Extract confidence score from frontmatter
- If confidence < 7 → Error: "PRP confidence too low. Run
/blueprint:prp-create {prp-name}to refine" - 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
- If work-order chosen → Run
- Continue to Step 2 if executing now OR confidence 7-8
- Load all referenced curated rule entries (
.claude/rules/) for context - Parse Implementation Blueprint and create TodoWrite entries ordered by dependencies
Step 2: Establish baseline with validation gates
Run pre-implementation validation gates (see REFERENCE.md) to establish clean starting state:
- Linting gate:
[command from PRP]- Expected: PASS - Existing tests gate:
[command from PRP]- Expected: PASS
If gates fail:
- Document existing issues
- Decide: fix first or proceed with note
- Continue when ready
Step 3: Execute TDD implementation cycle
For each task in Implementation Blueprint:
-
RED phase: Write failing test matching PRP TDD Requirements
- Create test file if needed
- Run tests → Confirm FAILURE (test is meaningful)
-
GREEN phase: Implement minimal code to pass test
- Follow Codebase Intelligence patterns from PRP
- Apply patterns from curated rule references
- Watch for Known Gotchas
- Run tests → Confirm SUCCESS
-
REFACTOR phase: Improve code while keeping tests green
- Extract common patterns
- Improve naming, add type hints
- Follow project conventions
- Run tests → Confirm PASS
- Run validation gates frequently (not just at end)
-
Mark progress: Update TodoWrite:
✅ Task N: [Description]
Step 4: Run comprehensive final validation
Execute all validation gates from PRP (see REFERENCE.md):
- Linting:
[cmd]- Expected: PASS - Type checking:
[cmd]- Expected: PASS - Unit tests:
[cmd]- Expected: PASS (all tests) - Integration tests:
[cmd]- Expected: PASS (if applicable) - Coverage check:
[cmd]- Expected: Meets threshold - Security scan:
[cmd]- Expected: No high/critical issues (if applicable) - Performance tests:
[cmd]- Expected: Meets baseline (if defined)
Verify each success criterion from PRP.
Step 5: Document deferred items
Identify and track any deferred work:
- Review Implementation Blueprint - items not completed
- Categorize each deferred item:
- Phase 2 (Required): Must have GitHub issues created
- Nice-to-Have: Optional, no issue required
- Blocked: Cannot complete - document blocker, create issue
- Create GitHub issues for all Phase 2 and Blocked items (see REFERENCE.md)
- Update PRP with deferred items section linking to GitHub issues
- Do NOT proceed to Step 6 until all required issues are created
Step 6: Sync feature tracker (if enabled)
If feature tracker exists (docs/blueprint/feature-tracker.json):
- Identify which feature codes (e.g., FR2.1) were addressed from PRP
- Update feature tracker for each code:
- Status:
complete(all criteria met) orpartial(some criteria met) orin_progress - Files: List of modified/created files
- Tests: List of test files
- Commits: Commit hashes
- Notes: Implementation notes
- Status:
- Recalculate statistics: completion percentages, phase status
- Update TODO.md: Check boxes for completed features
- Report feature tracker changes
Step 7: Report results and next steps
Generate comprehensive execution summary report:
- Tasks completed: X/Y
- Tests added: N
- Files modified: [list]
- Validation results: Table of all gates (PASS/FAIL status)
- Success criteria: All verified
- Deferred items summary: Count and GitHub issue numbers
- Feature tracker updates: Features updated and percentages
- New gotchas discovered: [documented for future reference]
- Recommendations: Follow-up work or curated rule updates
Prompt user for next action:
- Commit changes (Recommended) → Run
/git:commit - Create work-order for follow-up → Run
/blueprint:work-order - Capture patterns as curated rules → Run
/blueprint:curate-docs - Continue to next PRP → Run
/blueprint:prp-execute [next] - Done for now → Exit
Agentic Optimizations
| Context | Command |
|---|---|
| Check PRP exists | test -f docs/prps/${1}.md && echo "EXISTS" || echo "MISSING" |
| Extract confidence | head -50 docs/prps/${1}.md | grep -m1 "^confidence:" | sed 's/^[^:]*:[[:space:]]*//' |
| List all PRPs | ls docs/prps/*.md 2>/dev/null | xargs basename -s .md |
| Check feature tracker | test -f docs/blueprint/feature-tracker.json && echo "YES" || echo "NO" |
| Fast validation | Run validation gates in parallel when possible |
For detailed validation gate definitions, deferred items workflow, error handling procedures, and agent team coordination, see REFERENCE.md.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/laurigates/claude-plugins/blueprint-prp-execute">View blueprint-prp-execute on skillZs</a>