recipe-front-plan

Create frontend work plan from design document and obtain plan approval

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/recipe-front-plan/SKILL.md

Quality

Content

88%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 an executable, well-sequenced orchestration recipe with concrete subagent invocations and explicit validation/approval checkpoints. Its only weakness is minor over-inline content and a single external reference rather than a clear in-bundle progressive-disclosure structure.

Dimension	Reasoning	Score
Conciseness	The body is dense and task-focused with minimal padding and assumes Claude's knowledge of subagent orchestration; only minor restatements could be trimmed.	4 / 5
Actionability	Concrete subagent_type values, exact field mappings, a verbatim document-reviewer prompt, and mechanical extraction instructions make the guidance copy-paste ready.	5 / 5
Workflow Clarity	A clear five-step sequence is paired with an explicit Review Resolution Gate, a stop-and-obtain-approval checkpoint, and a feedback loop that re-invokes work-planner on requested changes.	5 / 5
Progressive Disclosure	Content is well organized into sections and the only reference points to an external skill's review-resolution.md; some orchestrator-definition material is inline rather than split out, leaving minor organization gaps.	4 / 5
	Total	18 / 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 the skill's purpose and approval step clearly, but omits explicit trigger guidance and natural user phrasing. Adding a "Use when…" clause with concrete trigger terms would raise completeness and trigger-term quality.

Suggestions

Append an explicit "Use when…" trigger clause naming situations that call for frontend work-plan creation (e.g., starting a frontend implementation phase from an approved design doc).

Add natural synonyms users might say such as "frontend plan", "implementation plan", "work breakdown", or "plan approval" to improve trigger term coverage.

Expand the action list slightly (e.g., selecting a design doc, generating test skeletons) to make capability coverage more comprehensive.

Dimension	Reasoning	Score
Specificity	Names the frontend-planning domain and two concrete actions ("Create frontend work plan from design document" and "obtain plan approval"), but coverage is not comprehensive.	3 / 5
Completeness	The "what" is clear (create plan, obtain approval) but no explicit "when" trigger guidance is present, capping completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Domain nouns like "frontend work plan", "design document", and "plan approval" are relevant but it lacks natural user phrasing or a "Use when…" trigger clause with synonyms.	3 / 5
Distinctiveness Conflict Risk	The frontend-planning-from-design-doc niche is mostly distinct with only minor overlap risk against other planning skills.	4 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: shinpr/claude-code-workflows
Path: skills/recipe-front-plan/SKILL.md
Commit: 83cf695

Reviewed: about 22 hours ago

Table of Contents

Discovery Implementation Validation

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.