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

82%

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

81%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 tightly written, well-sequenced workflow skill with strong validation checkpoints, feedback loops, and a clear terminal gate. Its main weakness is density that leaves minor conciseness and progressive-disclosure trim opportunities rather than any structural deficit.

Dimension	Reasoning	Score
Conciseness	The body assumes Claude's competence with no concept-explanation padding and every line is directive, but the dense qualification of edge cases ('when X', 'unless Y', 'otherwise Z') offers minor trim opportunities, keeping it just below a 5.	4 / 5
Actionability	Provides an executable store-resolver bash snippet, specific paths ($PRP_DIR/plans/, templates/implementation-report.md), explicit dispositions (FIXED, NOT A FINDING, TRACKED FOLLOW-UP, DECLINED), and concrete handoff invocations; minor gaps remain in copy-paste-ready coverage for the correction modes.	4 / 5
Workflow Clarity	A clear six-step sequence (Establish context through Verify and hand off) with explicit validation checkpoints ('After each coherent task, ask: How do I prove this actually works?'), feedback loops (validate -> fix -> rerun), BLOCKED states, and a terminal 'VALIDATION: GREEN/FAILED' gate.	5 / 5
Progressive Disclosure	Well-organized into numbered sections with a single clearly-signaled one-level-deep reference (templates/implementation-report.md in Resources) and no nested references; held at 4 because the dense inline process content could arguably be split further and no bundle files exist to verify structure.	4 / 5
	Total	17 / 20 Passed

Description

83%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, explicit description that clearly states both what the skill does and when to use it, with concrete trigger phrases. It is slightly held back by jargon-heavy trigger terms and minor overlap risk with closely related sibling skills.

Dimension	Reasoning	Score
Specificity	Names concrete actions ('Implements and validates existing PRP plans', 'corrects reviewed or failing-CI pull requests') tied to concrete objects, with several specific actions across three modes; falls short of 5 because the actions remain somewhat high-level rather than enumerating many discrete operations.	4 / 5
Completeness	Clearly answers both 'what' ('Implements and validates existing PRP plans and corrects reviewed or failing-CI pull requests') and 'when' via an explicit 'Always use when...' clause enumerating concrete trigger phrases, matching the 5 anchor.	5 / 5
Trigger Term Quality	Explicit triggers cover multiple scenarios ('executing an implementation plan', 'correcting a PR from a PRP review report or CI failure', '/prp-implement'), but the phrasing leans on PRP/CI jargon rather than broad natural synonyms users would say, missing a few common variations.	4 / 5
Distinctiveness Conflict Risk	Carves a clear niche (implementing existing plans and correcting PRs) with distinct triggers including the /prp-implement invocation, but has minor overlap risk with sibling PRP skills (prp-plan, prp-commit, prp-pr, prp-review).	4 / 5
	Total	17 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: Wirasm/prp
Path: .claude/skills/prp-implement/SKILL.md
Commit: 9724799

Reviewed: ~13 hours 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.