CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

recipe-plan

Create work plan from design document and obtain plan approval

Quality

73%

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 ./skills/recipe-plan/SKILL.md
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 body is a tightly written orchestration recipe with concrete agent invocations, a clearly sequenced five-step process, and strong validation gates including approval checkpoints and correction feedback loops. Its main weaknesses are mild redundancy and reliance on external skills for operational detail, which slightly limit self-contained actionability.

DimensionReasoningScore

Conciseness

The body is dense, procedural, and free of concept explanations, assuming Claude's competence throughout ("Invoke acceptance-test-generator with `design_docs: [selected Design Doc path]`"). Minor trimming is possible (Scope Boundaries is cross-referenced twice, and the "Explicit User Instruction" preamble is boilerplate), keeping it just below a 5.

4 / 5

Actionability

Invocations are concrete and executable: exact subagent_type values, named fields, and a verbatim reviewer prompt ("doc_type: WorkPlan target: docs/plans/[plan-name].md..."). It falls short of 5 because key operational details are delegated to external skills (e.g. "Follow subagents-orchestration-guide HC-06") without being self-contained.

4 / 5

Workflow Clarity

The five-step sequence is explicit with validation checkpoints and feedback loops: "Stop and obtain approval for plan content before completion", the mandatory Review Resolution Gate through "correction re-review... and convergence", and "If the user requests changes, re-invoke work-planner... and re-run Step 4". This matches the anchor for clear sequence with explicit validation and error-recovery loops.

5 / 5

Progressive Disclosure

No bundle files exist, and the body is well-organized into clear sections (Scope Boundaries, Execution Process, Response at Completion) with one clearly signaled external pointer ("read `references/review-resolution.md` from the loaded subagents-orchestration-guide skill"). It is not a 5 because the skill exceeds 50 lines and the cross-skill reference adds navigation indirection.

4 / 5

Total

17

/

20

Passed

Description

53%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 concise and states a clear, specific purpose with two concrete actions, but it entirely lacks any trigger guidance for when the skill should be used. Adding an explicit "Use when..." clause with natural trigger phrases would substantially improve completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause such as "Use when the user asks to plan implementation from a design document, create a work plan, or move from design to implementation."

Add natural trigger-term variations users would say, e.g. "work plan", "planning phase", "implementation plan", "plan approval", "design doc".

Optionally enumerate the concrete sub-actions (generate test skeletons, review the plan) to lift specificity from 1-2 actions toward comprehensive coverage.

DimensionReasoningScore

Specificity

The description names the domain ("design document") and two concrete actions ("Create work plan", "obtain plan approval"), matching the 1-2 concrete actions anchor. It is not score 4 because it does not list several specific actions with only minor gaps.

3 / 5

Completeness

The "what" is clear (create a work plan from a design document and get it approved), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"work plan", "design document", and "plan approval" are natural domain phrases a user might say, but there are no synonyms or variations (e.g. "planning phase", "implementation plan"), so keyword coverage is partial rather than good.

3 / 5

Distinctiveness Conflict Risk

The design-doc-to-approved-plan pipeline carves a specific niche with mostly distinct triggers, though it could still mildly overlap with generic planning or document skills, so it is not a clear 5.

4 / 5

Total

13

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

15

/

16

Passed

Repository

shinpr/claude-code-workflows

Path

skills/recipe-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.