prp-plan

Create comprehensive feature implementation plan with codebase analysis and research. Also wires bidirectional back/forward references between existing plans (the update-references workflow). Use when the user wants to plan a feature, turn a PRD into an implementation plan, "link two plans", "add a back/forward reference", "connect related plans", or invokes the prp-plan skill.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

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

A richly structured planning skill with excellent workflow sequencing and validation checkpoints, undermined by missing bundle templates that its mandatory-read instructions depend on. The duplicate Kild-lane preamble across files also wastes tokens.

Suggestions

Ship the missing bundle files (templates/plan-template.md, templates/ux-diagram-format.md, templates/report-format.md, workflows/update-references.md) the body marks as mandatory reads, or inline the essentials and stop referencing non-existent paths.

De-duplicate the "Kild lane" preamble: state it once in SKILL.md and drop the verbatim copy from each references/ file to recover tokens.

For the Phase 6 plan-generation core, surface at least a skeletal structure inline so the skill remains actionable even before a template file is opened.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and assumes Claude's competence, but the "Kild lane" preamble is duplicated verbatim in SKILL.md and every reference file, and mandatory-read instructions repeat; some tightening is possible without losing meaning.	2 / 3
Actionability	Concrete where present (executable PRP-store bash resolver, exact checkpoint checklists, per-phase prompts, real command examples), but the plan-generation core repeatedly delegates to templates that are not present in the bundle (plan-template.md, ux-diagram-format.md, report-format.md), leaving key steps incompletely specified.	2 / 3
Workflow Clarity	A clearly sequenced Phase 0–6 pipeline with explicit per-phase CHECKPOINT checklists, a verification section with feedback expectations, and gated transitions (e.g. "ONLY AFTER Phase 2 is complete").	3 / 3
Progressive Disclosure	Organization is good — a Resources section maps to one-level-deep reference files that exist (references/agent-prompts.md, task-block-format.md, validation-commands.md) — but three referenced templates (templates/plan-template.md, templates/ux-diagram-format.md, templates/report-format.md) and workflows/update-references.md are cited as mandatory reads yet are missing from the bundle, breaking navigation.	2 / 3
	Total	9 / 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.

A strong, well-structured description that names concrete actions, supplies natural trigger terms a user would say, and pairs a clear what with an explicit when clause. It is concise without padding and clearly distinct from generic planning skills.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "Create comprehensive feature implementation plan with codebase analysis and research" and "wires bidirectional back/forward references between existing plans" — rather than vague abstractions.	3 / 3
Completeness	Explicitly answers both what (creates plans, wires references) and when via a clear "Use when the user wants to plan a feature, turn a PRD into an implementation plan..." clause with explicit triggers.	3 / 3
Trigger Term Quality	Covers natural user phrasings a person would actually say: "plan a feature", "turn a PRD into an implementation plan", "link two plans", "add a back/forward reference", "connect related plans", plus the skill name "prp-plan".	3 / 3
Distinctiveness Conflict Risk	Occupies a clear PRP/planning niche with distinct triggers ("link two plans", "connect related plans") unlikely to fire for unrelated skills; the dual planning/reference-wiring purpose slightly broadens scope but triggers stay distinguishable.	3 / 3
	Total	12 / 12 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: profiles/kild/skills/prp-plan/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.