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 /prp-plan.

Quality

88%

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

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.

A well-structured, highly actionable multi-phase planning workflow with strong sequencing and validation checkpoints. Its main weakness is progressive disclosure: several 'mandatory read' references point to missing templates/ and workflows/ files, so the offloaded content cannot actually be loaded.

Suggestions

Add the missing templates/ files (plan-template.md, ux-diagram-format.md, report-format.md) and workflows/update-references.md, or remove the 'mandatory read' references and inline the minimal needed content.

Trim the directory-discovery src/ alternative list and deduplicate the verification section against <success_criteria> to recover token budget.

Consider consolidating the repeated 'Read X now (mandatory)' phrasing into a single Resources convention to reduce repetition while keeping the signaling.

Dimension	Reasoning	Score
Conciseness	Mostly efficient procedural guidance with tables and code, but the directory-discovery list enumerating src/ alternatives (app/, lib/, packages/, cmd/, internal/, pkg/) re-explains project layouts Claude already knows, and the verification section restates success_criteria, so it could be tightened.	2 / 3
Actionability	Provides copy-paste-ready executable guidance — a concrete bash PRP_DIR resolver, exact subagent names to launch, a discovery-table schema, and specific phase outputs — matching the fully-executable anchor.	3 / 3
Workflow Clarity	Clear Phase 0–6 sequence with explicit PHASE_X_CHECKPOINT checklists, a mode-select router, an ambiguity GATE ("STOP and ASK"), and a final verification section with feedback-loop validation, matching the clear-sequence-with-explicit-validation anchor.	3 / 3
Progressive Disclosure	References are well-signaled and one level deep with a Resources index, but 4 of 7 referenced bundle paths (templates/plan-template.md, templates/ux-diagram-format.md, templates/report-format.md, workflows/update-references.md) point to files/directories that do not exist, breaking navigation against the actual bundle structure.	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.

A strong third-person description that states concrete capabilities and gives explicit, natural trigger phrases covering both the planning and reference-wiring modes. It cleanly satisfies all four dimensions with no vagueness or over-claims.

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" — matching the anchor for naming several specific concrete actions.	3 / 3
Completeness	Explicitly answers both what (create plan / wire references) and when via a clear "Use when the user wants to plan a feature..." clause, satisfying the anchor requiring both what AND when with explicit triggers.	3 / 3
Trigger Term Quality	Covers natural phrases a user would say — "plan a feature", "turn a PRD into an implementation plan", "link two plans", "connect related plans", plus the /prp-plan invocation — giving good coverage of natural trigger terms.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (PRP-style implementation planning and plan cross-referencing) with distinct triggers unlikely to fire for unrelated skills, matching the clear-niche anchor.	3 / 3
	Total	12 / 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
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-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.