CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

recipe-front-plan

Create frontend 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 ./dev-workflows-frontend/skills/recipe-front-plan/SKILL.md

The canonical home for this skill is recipe-front-plan in shinpr/claude-code-workflows

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: fully parameterized subagent invocations, a mandatory review-resolution gate with convergence conditions, and an approval feedback loop. Its only weaknesses are mild redundancy in gate language and reliance on cross-skill references (HC-06, review-resolution.md) whose contents live outside this file.

DimensionReasoningScore

Conciseness

The body is directive throughout ('Invoke work-planner using Agent tool: `subagent_type`: "dev-workflows-frontend:work-planner"') and delegates concepts to named skills instead of re-explaining them. Not 5 because gate and protocol statements are restated in a few places ('Stop and obtain approval', the Review Resolution Gate mentions); not 3 since there is no genuine over-explanation of known concepts.

4 / 5

Actionability

Gives exact subagent_type values, exact field lists, a verbatim reviewer prompt ('doc_type: WorkPlan target: docs/plans/[plan-name].md...') and a literal completion-response template. Not 5 because execution depends on external skill content (e.g. 'Follow subagents-orchestration-guide HC-06', 'read references/review-resolution.md from the loaded subagents-orchestration-guide skill') and unresolved placeholders like '[plan-name].md', leaving minor gaps.

4 / 5

Workflow Clarity

Steps 1-5 are clearly sequenced with explicit validation checkpoints (Review Resolution Gate through 'correction re-review ... and convergence') and feedback loops ('If the user requests changes, re-invoke work-planner ... and re-run Step 4'; 'Return to the requirements gate only when...'). This matches the anchor calling for explicit validation, error-recovery loops, and an approval checklist.

5 / 5

Progressive Disclosure

The skill is a well-sectioned overview that appropriately splits detail into named specialist skills rather than inlining it; its single file reference ('references/review-resolution.md' from subagents-orchestration-guide) is one level deep and clearly signaled. Not 5 because that reference points into another skill's bundle rather than a local, well-signaled reference set, which is a minor organization gap.

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 states a clear, appropriately scoped 'what' in third person with two concrete actions, but it omits any 'when to use' trigger guidance and lacks natural term variations. It is serviceable yet below the quality of the reference examples, which pair capability lists with explicit 'Use when...' clauses.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to plan frontend implementation from an approved design document or requests a frontend work plan for approval.'

Broaden natural keyword coverage with synonyms users would actually say, such as 'frontend planning', 'implementation plan', 'UI spec', or 'break down the design doc into tasks'.

Reflect the full capability set concisely (test skeleton generation, plan review, and approval loop) so the description matches the workflow the skill actually runs.

DimensionReasoningScore

Specificity

Names the domain ('frontend work plan') and two concrete actions ('Create ... from design document', 'obtain plan approval'), matching the 1-2 concrete actions anchor; it is not 4 because the body's other capabilities (test skeleton generation, plan review) are absent, which is more than a minor coverage gap.

3 / 5

Completeness

The 'what' is clear (create a frontend work plan from a design document and obtain approval), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

'frontend', 'work plan', 'design document', and 'plan approval' are relevant natural keywords, but common variations and synonyms ('planning', 'UI', 'implementation plan') are missing. Not 4 because the missing terms go beyond 'a few'; not 2 because the present terms are domain-specific rather than generic.

3 / 5

Distinctiveness Conflict Risk

'frontend work plan from design document' carves a mostly distinct niche with only minor overlap risk against closely related planning skills. Not 5 because no explicit trigger phrases sharpen the boundary further, and sibling planning-phase skills could plausibly overlap.

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

dev-workflows-frontend/skills/recipe-front-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.