CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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".

Quality

89%

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

SKILL.md
Quality
Evals
Security

Quality

Content

90%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 lean, highly actionable instruction-only skill: the process is explicitly sequenced with a user-approval checkpoint, and the plan template is copy-paste ready. The main flaws are a self-contradictory output path ('./ai-context/plans/' vs './plans/'), a missing post-write verification step, and a large inline template that could be split out.

Suggestions

Fix the output-path inconsistency: the intro says the plan goes to './ai-context/plans/' while step 6 and the frontmatter description say './plans/' — pick one location and use it everywhere.

Add a brief step 7 to verify the written plan file against the user-approved breakdown (all phases present, user stories mapped, acceptance criteria listed) before finishing.

Consider moving the ~45-line plan template to references/plan-template.md and referencing it from step 6 to keep SKILL.md as a lean overview.

DimensionReasoningScore

Conciseness

Every section instructs rather than explains; no padding, no concepts Claude already knows, and the numbered steps, XML-tagged rule block, and template all earn their tokens.

5 / 5

Actionability

Concrete six-step process with explicit slice rules ('Each slice delivers a narrow but COMPLETE path through every layer') and a copy-paste-ready plan template with placeholder structure, acceptance-criteria checkboxes, and a named output file convention.

5 / 5

Workflow Clarity

A clear numbered sequence with a genuine feedback loop ('Iterate until the user approves the breakdown'), but there is no verification step after writing the plan file, and the output location is inconsistent: the intro says './ai-context/plans/' while step 6 and the frontmatter say './plans/'.

4 / 5

Progressive Disclosure

Well-organized sections with no nested references and no orphaned file references, and no bundle files exist to score against. However, at ~107 lines with a ~45-line inline template, the template could arguably live in a references/ file, so the under-50-line clean-structure exception does not fully apply.

4 / 5

Total

18

/

20

Passed

Description

83%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 a concrete capability and an explicit, multi-trigger 'Use when' clause in third person. Trigger coverage is good though not exhaustive of natural synonyms, and overlap with general planning skills is possible but limited.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/') but does not enumerate what the produced plan contains, leaving minor gaps in coverage.

4 / 5

Completeness

Explicitly answers both what ('Turn a PRD into a multi-phase implementation plan... saved as a local Markdown file in ./plans/') and when ('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

Good natural phrases users would say ('break down a PRD', 'create an implementation plan', 'plan phases from a PRD', 'tracer bullets'), though common synonyms like 'split a PRD into tasks' or 'implementation roadmap' are missing.

4 / 5

Distinctiveness Conflict Risk

PRD-specific triggers plus the distinctive 'tracer bullets' term establish a clear niche, but there is minor overlap risk with generic planning or roadmap-generation 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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

webiny/webiny-js

Path

.claude/skills/prd-to-plan/SKILL.md

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.