CtrlK
BlogDocsLog inGet started
Tessl Logo

prd-to-plan

Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/. Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets".

65

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./deprecated/prd-to-plan/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, concise skill body that lays out a clear sequenced process with a reusable plan template and an explicit user-approval feedback loop. Its main gap is the absence of a post-write validation step to confirm the plan file is correct.

Suggestions

Add an explicit verification step after writing the plan file (e.g., re-read it to confirm phases are vertical slices and acceptance criteria are present).

Specify how to handle the iteration loop concretely (e.g., track which phases the user asked to merge or split and update the numbered list before re-asking).

Consider moving the plan template into a referenced file if the skill grows, to keep SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence, using terse process steps and a compact template rather than explaining what a PRD or tracer bullet is; only minor phrasing could be trimmed.

4 / 5

Actionability

Concrete guidance is present via a full plan template, explicit file path/naming, and a structured quiz step; it is instruction-oriented so executable code is not expected, with only minor gaps in specifying how to iterate with the user.

4 / 5

Workflow Clarity

A clear six-step sequence is given with an explicit user-approval checkpoint ('Iterate until the user approves the breakdown'), though it lacks an explicit validation/verify-output step after writing the plan file.

4 / 5

Progressive Disclosure

The skill is a self-contained overview with a well-organized Process section and an inlined template; no bundle files exist so structure is internal, and it is appropriately organized with only minor gains possible from splitting the template out.

4 / 5

Total

16

/

20

Passed

Description

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

A strong description that clearly states the capability, output, and explicit trigger conditions in third person. It names concrete actions and natural user phrases, with only minor room to broaden trigger synonyms.

DimensionReasoningScore

Specificity

Lists several specific actions (break down a PRD, create a multi-phase implementation plan, plan phases, tracer-bullet vertical slices) and a concrete output (Markdown file in ./plans/), with only minor gaps in coverage of intermediate steps.

4 / 5

Completeness

Explicitly answers what it does (turn a PRD into a multi-phase implementation plan saved as a local Markdown file) and when to use it ('Use when user wants to break down a PRD, create an implementation plan, plan phases from a PRD, or mentions "tracer bullets"').

5 / 5

Trigger Term Quality

Includes natural user phrases ('break down a PRD', 'create an implementation plan', 'plan phases from a PRD') plus the explicit term 'tracer bullets'; a few common synonyms are missing but coverage is strong.

4 / 5

Distinctiveness Conflict Risk

The PRD-to-plan + tracer-bullets niche is fairly distinct with clear triggers; only minor overlap risk with general planning or codebase-exploration skills.

4 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
MrToxy/claude-skills
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.