prp-plan

Creates an implementation-ready plan for a feature, bug fix, refactor, or chore from a PRD, issue, document, or description using codebase evidence, first-principles reasoning, and conditional root-cause analysis, research, or spikes. Publishes issue-derived plans back to their source issue. Use when the user asks to "plan this feature", "plan this bug fix", "plan issue X", "create an implementation plan", "turn this PRD into a plan", investigate how a change should be built, link related plans, or invokes $prp-plan.

Quality

90%

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.

The content is a well-structured, evidence-driven workflow with explicit gates, validation, and feedback loops, supported by real reference files. Its main weaknesses are a few tightenable passages and bundle references (templates/, workflows/) whose target files are not present.

Suggestions

Tighten the longest sentences in steps 1 and 8 (tracker reconciliation and publication/verification) into shorter clauses to improve scannability.

Either include the referenced templates/plan-template.md, templates/report-format.md, and workflows/update-references.md in the bundle or note their absence so navigation is not broken.

Consider inlining a minimal task-format example or a one-line spike-prompt excerpt so the core guidance is executable without opening a reference file.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and assumes Claude's competence, but a few long sentences (e.g., the tracker-reconciliation and publication instructions) could be tightened without losing meaning. It sits noticeably above the efficient-but-tightenable anchor.	4 / 5
Actionability	It provides a fully executable store-resolver bash block and concrete agent-delegation and validation expectations, though much specific guidance is delegated to reference files rather than inlined. Minor gaps keep it just below copy-paste-everything.	4 / 5
Workflow Clarity	An explicit Mode router feeds an 8-step sequence with a design gate (step 6) and a verification checklist (step 8), including feedback loops for publication failure and re-validation. Checkpoints are explicit throughout.	5 / 5
Progressive Disclosure	The body is a clear overview with a well-signaled, one-level-deep Resources section pointing to verified reference files; however, templates/ and workflows/ paths are referenced but not present in the bundle, leaving a minor navigation gap.	4 / 5
	Total	17 / 20 Passed

Description

100%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.

The description is specific, trigger-rich, complete, and clearly distinct: it states concrete capabilities and pairs them with explicit natural-language triggers and the $prp-plan invocation. It cleanly hits the top anchor on every dimension.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions—creating an implementation-ready plan, performing conditional root-cause analysis, research, spikes, and publishing issue-derived plans back to the source issue—covering the workflow comprehensively.	5 / 5
Completeness	It explicitly answers both what the skill does ('Creates an implementation-ready plan...') and when to use it ('Use when the user asks to...'), with concrete trigger phrases.	5 / 5
Trigger Term Quality	It enumerates natural user phrasings ('plan this feature', 'plan this bug fix', 'plan issue X', 'turn this PRD into a plan', 'link related plans') plus the $prp-plan invocation, giving broad synonym coverage.	5 / 5
Distinctiveness Conflict Risk	The planning-only niche (no implementation, no PR), PRD/issue inputs, spike delegation, and $prp-plan invocation make it clearly distinct from implementation or debugging skills with minimal overlap risk.	5 / 5
	Total	20 / 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-plan/SKILL.md
Commit: 9724799

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