prp-implement

Implements and validates existing PRP plans and corrects reviewed or failing-CI pull requests. Always use when executing an implementation plan, implementing an issue that already has a local or published plan, correcting a PR from a PRP review report or CI failure, when another PRP workflow reaches its implementation or correction step, or when the user invokes $prp-implement.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

73%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, validation-heavy orchestration skill with strong workflow clarity and concrete, executable guidance. Its weaknesses are some generic engineering-principle padding and a referenced template file that does not exist in the bundle.

Suggestions

Add the missing templates/implementation-report.md bundle file (the body instructs Claude to read it and 'follow that structure exactly'), or inline the report structure so the reference is not required.

Trim Section 2's implementation-principles bullets to the non-obvious, PRP-specific guidance and drop restatements of KISS/YAGNI/DRY that Claude already applies.

Consider tightening the dense prose paragraphs in Steps 1 and 5 into shorter imperative lines so each token carries operational rather than hedging weight.

Dimension	Reasoning	Score
Conciseness	The body is mostly tight operational guidance, but Section 2's implementation-principles bullet list (KISS/YAGNI, 'generated code as cheap and maintenance as expensive', DRY) restates generic engineering wisdom Claude already knows and could be trimmed.	3 / 5
Actionability	Provides a copy-paste bash store resolver, concrete report paths, and specific skill invocations with arguments ($prp-commit, $prp-pr --base, $prp-prd-update implemented) covering initial, correction, CI, and evidence-only cases, with only minor gaps.	4 / 5
Workflow Clarity	A clear six-step sequence with an entire validation section, explicit feedback loops ('When verification fails... fix the proven cause and rerun the affected proof'), and BLOCKED gates for recovery, matching the anchor 5 checklist pattern.	5 / 5
Progressive Disclosure	Well-organized into numbered sections with a clearly signaled one-level reference to templates/implementation-report.md, but that referenced file is absent from the bundle, a moderate navigation gap.	4 / 5
	Total	16 / 20 Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that crisply states what the skill does and gives exhaustive, natural trigger guidance. Specificity is the only slightly soft dimension, as the action verbs remain one level more abstract than fully mechanical tasks.

Dimension	Reasoning	Score
Specificity	Names the PRP/PR domain and several concrete actions ('Implements and validates existing PRP plans and corrects reviewed or failing-CI pull requests'), but the verbs are somewhat higher-level than anchor 5's mechanical action list, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both what ('Implements and validates existing PRP plans and corrects... pull requests') and when ('Always use when...') with concrete trigger phrases, matching the anchor 5 example.	5 / 5
Trigger Term Quality	Comprehensive natural trigger coverage with synonyms and the invocation token: 'executing an implementation plan', 'implementing an issue that already has a local or published plan', 'correcting a PR from a PRP review report or CI failure', and 'invokes $prp-implement'.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear PRP-workflow niche with distinct triggers ($prp-implement, PRP review report, CI failure) and minimal overlap risk with unrelated skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Wirasm/prp
Path: .agents/skills/prp-implement/SKILL.md
Commit: 2cced43

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.