prp-implement

Execute an implementation plan with rigorous validation loops. Use when the user wants to implement or execute a plan file, build a planned feature, or invokes /prp-implement.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%Weight 40%Scale 1-3

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

The body delivers highly actionable, well-sequenced guidance with strong validation checkpoints, but it is monolithic and somewhat long, keeping conciseness and progressive disclosure at the mid tier.

Suggestions

Move the full implementation-report template and/or the 'Handling Failures' reference section into a separate file (e.g. references/report-template.md) and link to it, reducing SKILL.md length and improving progressive disclosure.

Trim or consolidate the repeated 'Common patterns' command lists across Phases 3-4 into a single shared reference to reduce redundancy.

Keep the most critical validation-loop guidance inline but push language-variant command examples (JS/TS/Python/Rust/Go) into a secondary reference so the core workflow reads leaner.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and earns its tokens, but repeated 'Common patterns' lists and a full inlined report template add length that could be tightened; it sits at 'mostly efficient but could be tightened' rather than fully lean.	2 / 3
Actionability	Concrete, executable bash commands (package-manager detection, git state checks, type-check/lint/test/build invocations) and a copy-paste-ready report template with explicit placeholders make the guidance fully actionable.	3 / 3
Workflow Clarity	Phases 0-6 are clearly sequenced, each with an explicit PHASE_N_CHECKPOINT checklist, validation feedback loops ('fix, re-run, only proceed when passing'), and a dedicated 'Handling Failures' section for error recovery.	3 / 3
Progressive Disclosure	No references/scripts/assets bundle files exist and the SKILL.md is a monolithic ~550-line single file with all content inline; it is well-organized by sections but content such as the report template and failure handling could be split out into separate files for clearer navigation.	2 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

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

The description is strong: third-person, concise, and explicit about both capability and trigger conditions with natural user vocabulary. It clearly distinguishes the skill via its plan-file domain and named command.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions ('Execute an implementation plan', 'implement or execute a plan file', 'build a planned feature') tied to a specific domain, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both what ('Execute an implementation plan with rigorous validation loops') and when via a clear 'Use when...' clause, matching the top anchor with explicit triggers.	3 / 3
Trigger Term Quality	Includes natural user phrasing like 'implement or execute a plan file', 'build a planned feature', and the explicit '/prp-implement' invocation, giving good coverage of terms users would actually say.	3 / 3
Distinctiveness Conflict Risk	The plan-file framing plus the named '/prp-implement' command carve a clear niche tied to a specific skill family, making conflicts with unrelated skills unlikely despite the broad 'build a planned feature' phrasing.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (556 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

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

Reviewed: 11 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.