CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

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, actionable planning workflow with strong validation checkpoints and a clear progressive-disclosure spine. It is slightly redundant across the reasoning and verification sections and ships references to three template/workflow files that are not present in the bundle.

Suggestions

Tighten the overlap between §4 (invariant/primitive reasoning), §7, and the §8 verification checklist so each point appears once; the checklist can reference §4 instead of restating it.

Add the missing bundle files referenced by the body (templates/plan-template.md, templates/report-format.md, workflows/update-references.md) or remove the references, since three of seven pointed-to paths currently resolve to nothing.

Inline a minimal plan-template skeleton (or move it into an existing references file) so the decisive artifact format is reachable without the absent template.

DimensionReasoningScore

Conciseness

The body is dense, directive, and assumes Claude's intelligence (e.g. 'Plan only. Do not implement, commit, or open a PR.'), with no padding explaining known concepts, but invariant/primitive reasoning recurs across §4, §7, and the §8 checklist and could be tightened. Fits 'efficient; minor instances of over-explanation that could be trimmed' rather than fully lean.

4 / 5

Actionability

Provides copy-paste executable bash (the PRP store resolver), named delegation agents, exact metadata format ('<!-- prp-plan-id: <plan-id> -->'), and a concrete file:line evidence spec, but defers the decisive plan artifact structure to templates that are not in the bundle, leaving a minor gap.

4 / 5

Workflow Clarity

A clear numbered §1–§8 sequence includes an explicit design gate (§6 stop-and-ask conditions), a 14-item verification checklist (§8), and an error feedback loop for issue publication ('If publication or verification fails, preserve the local plan but report the publication blocker'), matching the anchor for explicit validation steps with checklists and recovery loops.

5 / 5

Progressive Disclosure

The body is a well-signaled overview pointing one level deep to references and templates with a Resources section, and the four references/*.md files exist in the bundle. However templates/plan-template.md, templates/report-format.md, and workflows/update-references.md are referenced but missing from the bundle, a navigation defect beyond a truly minor gap but not severe enough to drop to the 3 anchor.

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 concrete, comprehensive, and explicitly answers both what the skill does and when to use it with natural trigger phrases and the slash command. It is written in third person and avoids vague fluff. No changes needed.

DimensionReasoningScore

Specificity

Lists multiple concrete actions across distinct input domains — 'Creates an implementation-ready plan for a feature, bug fix, refactor, or chore from a PRD, issue, document, or description' and 'Publishes issue-derived plans back to their source issue' — with comprehensive coverage of plan types, inputs, and methods.

5 / 5

Completeness

Explicitly answers both 'what' (creates implementation-ready plans, publishes issue-derived plans back to source issue) and 'when' via a concrete 'Use when...' clause listing multiple trigger phrases.

5 / 5

Trigger Term Quality

Includes comprehensive natural user phrases — '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' — plus the /prp-plan slash invocation, covering synonyms and the command form.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (PRP planning workflow) with distinct triggers including the /prp-plan invocation and plan-specific phrases, minimizing overlap with generic planning or implementation skills.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
Wirasm/prp
Reviewed

Table of Contents

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.