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

80

Quality

100%

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

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, lean instruction skill: a clear sequenced process with a feedback checkpoint, concrete rules, and a copy-paste plan template. Its one real weakness is an inconsistent output path that should be reconciled.

Suggestions

Reconcile the output directory: the intro says './ai-context/plans/' while step 6 and the template example say './plans/'. Pick one and use it consistently so Claude writes the file to the location the user expects.

The intro paragraph largely restates the frontmatter description; consider trimming it to a one-line purpose statement to avoid token redundancy.

Step 2 ('Explore the codebase') could name one or two specific things to look for first (e.g. existing route handlers, schema definitions) so exploration is directed rather than open-ended.

DimensionReasoningScore

Conciseness

Lean throughout — it does not explain what a PRD or tracer bullet is beyond a parenthetical, and the rules and template are tight instruction rather than padded context; not a 2 because there is no unnecessary concept explanation and every section earns its tokens. The only minor redundancy is the intro line lightly restating the description, which does not rise to verbosity.

3 / 3

Actionability

Provides concrete, copy-paste-ready guidance: an explicit decision checklist, a bounded <vertical-slice-rules> block, specific quiz questions, and a full <plan-template>; not a 2 because the template and rules are directly executable rather than pseudocode or vague direction. One concrete flaw: the output path contradicts itself ('./ai-context/plans/' in the intro vs './plans/' in step 6 and the template).

3 / 3

Workflow Clarity

A clearly sequenced 1–6 process with an explicit human-in-the-loop feedback loop ('Iterate until the user approves the breakdown') and an upfront context check; not a 2 because the checkpoint is explicit and the sequence is unambiguous. No destructive/batch operation is present, so the strict validation cap does not apply.

3 / 3

Progressive Disclosure

Self-contained skill with no bundle files, organized into clearly labeled sections and bounded blocks (<vertical-slice-rules>, <plan-template>); per the simple-skills note, a self-contained skill with well-organized sections scores 3. No references/, scripts/, or assets/ directories exist, so there are no file references to verify and nothing that would benefit from being split out.

3 / 3

Total

12

/

12

Passed

Description

100%

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 concisely states concrete capabilities and pairs them with an explicit, multi-variant 'Use when' trigger clause. It is distinguishable from generic planning skills and does not over-claim.

DimensionReasoningScore

Specificity

Names multiple concrete actions in sequence — 'Turn a PRD into a multi-phase implementation plan using tracer-bullet vertical slices, saved as a local Markdown file in ./plans/' — matching the 'lists multiple specific concrete actions' anchor; not a 2 because it goes beyond a single domain+action to several distinct actions.

3 / 3

Completeness

Explicitly answers both 'what' (turn PRD into multi-phase plan saved as Markdown) and 'when' via a clear 'Use when...' clause; not a 2 because the trigger guidance is explicit, not merely implied.

3 / 3

Trigger Term Quality

Covers natural phrases a user would actually say — 'break down a PRD', 'create an implementation plan', 'plan phases from a PRD', 'tracer bullets' — with good variation; not a 2 because it provides multiple natural phrasings rather than a single keyword.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear niche (PRD-to-plan via tracer bullets) with distinct triggers unlikely to fire for unrelated skills; not a 2 because the combination of 'PRD', 'implementation plan', and 'tracer bullets' is specific and not overlapping with generic planning skills.

3 / 3

Total

12

/

12

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
webiny/webiny-js
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.