workflow-plan

Chain-loaded workflow planning. 6-phase with mode routing and conflict detection.

Quality

65%

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 ./.claude/workflow-skills/workflow-plan/SKILL.md

Quality

Content

83%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 concise and highly actionable with ready-to-run commands, but it delegates the actual 6-phase workflow sequence and its validation checkpoints to an external directory without surfacing them. Structure is clean with a clearly signaled reference, though that reference is minimally annotated.

Suggestions

List the 6 phases in order inline (or in a referenced file) so the sequence is visible without leaving SKILL.md.

Add explicit validation/verification checkpoints between phases, especially before destructive or replan steps.

Annotate the `phases/` reference with what each phase file contains so navigation is one level deep and self-describing.

Dimension	Reasoning	Score
Conciseness	The body is extremely lean with no padding or explanation of concepts Claude already knows; every line delivers an executable command or a needed variable, matching the 'lean and efficient; every token earns its place' anchor.	5 / 5
Actionability	It provides copy-paste-ready `chain_loader` commands covering the common cases (full pipeline, verify-only, replan), fitting the 'fully executable; copy-paste ready' anchor.	5 / 5
Workflow Clarity	The actual 6-phase sequence is only referenced via a directory path rather than laid out, and validation checkpoints for this batch/destructive-capable pipeline are implicit only; per the guidelines a missing validation loop in such workflows caps clarity at 3.	3 / 5
Progressive Disclosure	The body is well organized into a header, command list, and variables, with a clearly signaled one-level reference to the phases directory; it is not a 5 because the phases reference is a terse path with no explanation of what each phase contains.	4 / 5
	Total	17 / 20 Passed

Description

46%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 names specific capabilities, but it omits any explicit trigger guidance and leans on technical jargon over natural user phrasing. It is distinct enough to avoid most conflicts but incomplete on the 'when to use' axis.

Suggestions

Add an explicit 'Use when ...' clause naming natural user phrases (e.g., 'Use when planning a multi-phase workflow, routing between modes, or detecting plan conflicts').

Replace or supplement jargon like 'chain-loaded' with everyday terms users would actually say.

Briefly enumerate the concrete actions the skill performs rather than only naming features.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Chain-loaded workflow planning') and several concrete capabilities ('6-phase', 'mode routing', 'conflict detection'), but these are feature statements rather than enumerated actions, matching the anchor that lists 1-2 concrete capabilities without comprehensive coverage.	3 / 5
Completeness	A clear 'what' is present but there is no 'when' / 'Use when...' trigger guidance, which per the judging guidelines caps completeness at 3; it does not rise to 4 because the trigger context is entirely absent rather than weakly implied.	3 / 5
Trigger Term Quality	The dominant terms ('chain-loaded', 'mode routing') are technical jargon rather than phrases a user would naturally say; only 'workflow planning' is moderately natural, fitting the anchor of one or two generic keywords missing common user phrasings.	2 / 5
Distinctiveness Conflict Risk	The pairing of 'chain-loaded' execution with 'conflict detection' carves a fairly distinct niche with only minor overlap risk against generic planning skills, fitting the 'mostly distinct' anchor; it is not a 5 because 'workflow planning' alone is broad.	4 / 5
	Total	12 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: catlog22/Claude-Code-Workflow
Path: .claude/workflow-skills/workflow-plan/SKILL.md
Commit: 07491b0

Reviewed: 3 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.