recipe-implement

Orchestrate the complete implementation lifecycle from requirements to deployment

Quality

27%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/recipe-implement/SKILL.md

Quality

Discovery

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This description is a vague, high-level statement that reads more like a marketing slogan than a functional skill description. It lacks concrete actions, natural trigger terms, explicit usage guidance, and any distinguishing characteristics that would help Claude select it appropriately from a pool of skills.

Suggestions

Replace the abstract phrase 'orchestrate the complete implementation lifecycle' with specific concrete actions, e.g., 'Break down feature requirements into tasks, generate implementation plans, scaffold code, write tests, and configure deployment pipelines.'

Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to plan a feature implementation, create a project plan, or needs end-to-end guidance from design to deployment.'

Narrow the scope to a distinct niche to reduce conflict risk — currently it overlaps with nearly every development skill. Specify what kind of projects, languages, or workflows this skill targets.

Dimension	Reasoning	Score
Specificity	The description uses vague, abstract language like 'orchestrate the complete implementation lifecycle' without listing any concrete actions. Terms like 'requirements' and 'deployment' are broad categories, not specific capabilities.	1 / 3
Completeness	The description only vaguely addresses 'what' (orchestrate implementation lifecycle) and completely lacks any 'when' clause or explicit trigger guidance. There is no 'Use when...' or equivalent.	1 / 3
Trigger Term Quality	The terms used ('implementation lifecycle', 'orchestrate') are not natural keywords a user would say. Users would more likely say things like 'build a feature', 'deploy my app', or 'implement this'. The description reads like a marketing tagline rather than containing practical trigger terms.	1 / 3
Distinctiveness Conflict Risk	This description is extremely generic and could conflict with virtually any development-related skill. 'Requirements to deployment' encompasses nearly all software engineering tasks, making it impossible to distinguish from coding, testing, CI/CD, project management, or other skills.	1 / 3
	Total	4 / 12 Passed

Implementation

55%

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

This skill defines a comprehensive orchestration workflow with strong workflow clarity — clear sequencing, decision tables, validation checkpoints, and error recovery loops. However, it suffers from heavy dependency on external references that are not provided in the bundle, making it incomplete in isolation. The content is moderately concise but could be tightened by reducing repetitive references and consolidating overlapping sections.

Suggestions

Include the referenced subagents-orchestration-guide and sub-agents.md as bundle files, or inline the critical flow definitions needed to make this skill self-contained enough to execute.

Add concrete examples of sub-agent invocation prompts (e.g., an actual Agent tool call with a filled-in prompt) so the orchestration is copy-paste actionable rather than abstract.

Split the detailed per-task execution cycle and post-implementation verification into separate referenced files to improve progressive disclosure and reduce the monolithic structure.

Consolidate the overlapping pre-execution checklist and execution decision flow sections to reduce redundancy and improve conciseness.

Dimension	Reasoning	Score
Conciseness	The skill is moderately efficient but contains repetitive references to 'subagents-orchestration-guide skill' and some redundant structural elements (e.g., the pre-execution checklist partially overlaps with the execution decision flow). Several sections could be tightened, though most content is domain-specific and not explaining things Claude already knows.	2 / 3
Actionability	The skill provides structured decision tables, specific subagent types, and clear step sequences, but relies heavily on external references (subagents-orchestration-guide, various sub-agent skills) without providing their content. Key details like actual prompt templates for sub-agents, concrete file path examples, and executable commands are mostly absent — the guidance is specific in structure but incomplete in isolation.	2 / 3
Workflow Clarity	The multi-step workflows are clearly sequenced with explicit validation checkpoints: the 4-step task execution cycle has clear pass/fail branching, the post-implementation verification has a fix-and-rerun loop, the implementation readiness check has a decision table with explicit stop/continue gates, and stopping points are clearly marked throughout. Feedback loops for error recovery are well-defined.	3 / 3
Progressive Disclosure	The skill heavily references external files and skills (subagents-orchestration-guide, sub-agents.md, various sub-agent skills, recipe-prepare-implementation) but no bundle files are provided, making it impossible to follow the references. The SKILL.md itself is a monolithic wall of detailed orchestration logic that could benefit from splitting into separate reference files for the task execution cycle, verification flow, and cleanup procedures.	1 / 3
	Total	8 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: shinpr/claude-code-workflows
Commit: 68ecb4a

Reviewed: about 11 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.