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

72%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/prp-implement/SKILL.md

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 is a highly actionable, clearly sequenced multi-phase workflow with strong validation feedback loops, but it carries some redundant failure-handling text and keeps large report/output templates inline rather than offloading them to reference files.

Suggestions

Remove or condense the 'Handling Failures' section since its type-check/test/lint/build/integration recovery steps already appear inline in Phases 3 and 4.

Move the Phase 5.2 report template and Phase 6 output template into a reference file (e.g. references/report-template.md) and link to it, improving progressive disclosure and trimming the main skill.

Consider extracting the package-manager/base-branch detection tables into a shared reference if other PRP skills duplicate them, to reduce cross-skill drift.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient concrete commands, tables, and checkpoints without explaining concepts Claude already knows, but the 'Handling Failures' section largely duplicates the validate/fix/retry guidance already in Phases 3 and 4, so it could be tightened.	2 / 3
Actionability	It provides copy-paste-ready bash (e.g., the PRP store resolver, git detection commands), exact runner/lockfile tables, and clearly defined {runner}/{base-branch} placeholders, matching the fully-executable score-3 anchor.	3 / 3
Workflow Clarity	Phases 0-6 are explicitly sequenced with PHASE_CHECKPOINT checklists and validate->fix->retry feedback loops for type-check, tests, lint, and build, exactly matching the clear-sequence-with-explicit-validation score-3 anchor.	3 / 3
Progressive Disclosure	The file is well-organized into headed phases, but it is a monolithic ~550-line document with no external references, and the large report/output markdown templates in Phases 5-6 are inline content that could plausibly be split into reference files.	2 / 3
	Total	10 / 12 Passed

Description

67%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 cleanly answers both what the skill does and when to use it with an explicit trigger clause, but its action list and trigger-term coverage are somewhat narrow and the 'build a planned feature' phrasing risks overlap with generic implementation skills.

Suggestions

Broaden the action list with distinct concrete verbs (e.g., 'run validation gates, write tests, archive the plan, generate an implementation report') to lift specificity to a comprehensive score-3 list.

Add more natural trigger variations users would actually say (e.g., 'run a plan', 'execute a PRP', 'turn a plan into code') to improve trigger-term coverage.

Tighten the 'when' clause around plan-file/PRP execution specifically and drop or qualify 'build a planned feature' to reduce conflict with generic coding skills.

Dimension	Reasoning	Score
Specificity	It names the domain and a few actions ('Execute an implementation plan with rigorous validation loops', 'implement or execute a plan file, build a planned feature'), but these are variations of one action rather than a comprehensive list of multiple distinct concrete actions, so it falls short of the score-3 anchor.	2 / 3
Completeness	It clearly states what ('Execute an implementation plan with rigorous validation loops') and gives an explicit 'Use when...' clause for when to invoke it, satisfying the score-3 anchor for both what and when.	3 / 3
Trigger Term Quality	Terms like 'implement', 'execute a plan file', and 'build a planned feature' are natural, but coverage is limited and missing common variations a user might say, matching the 'some relevant keywords but missing common variations' anchor rather than broad score-3 coverage.	2 / 3
Distinctiveness Conflict Risk	The PRP/plan-file framing and '$prp-implement' invocation give it a niche, but 'build a planned feature' is generic enough to overlap with general coding skills, so it is not a clearly conflict-free score-3.	2 / 3
	Total	9 / 12 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
skill_md_line_count	SKILL.md is long (557 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: Wirasm/prp
Path: .agents/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.