workflow-tdd-plan-plan
Unified TDD workflow skill combining 6-phase TDD planning with Red-Green-Refactor task chain generation, and 4-phase TDD verification with compliance reporting. Triggers on "workflow-tdd-plan", "workflow-tdd-verify".
60
52%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/workflow-tdd-plan/SKILL.mdQuality
Discovery
57%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 identifies a clear niche (TDD workflow planning and verification) with distinct trigger commands, making it unlikely to conflict with other skills. However, it relies on technical jargon and command-style triggers rather than natural language, and lacks an explicit 'Use when...' clause that would help Claude know when to select this skill based on user intent.
Suggestions
Add an explicit 'Use when...' clause describing user scenarios, e.g., 'Use when the user wants to plan a test-driven development workflow, generate TDD task chains, or verify TDD compliance in their codebase.'
Include more natural trigger terms users would actually say, such as 'test-driven development', 'write tests first', 'TDD planning', 'verify test coverage', or 'red-green-refactor cycle'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (TDD workflow) and mentions some actions like '6-phase TDD planning', 'Red-Green-Refactor task chain generation', '4-phase TDD verification', and 'compliance reporting', but these are somewhat jargon-heavy and not fully concrete in terms of what specific actions are performed on what artifacts. | 2 / 3 |
Completeness | The 'what' is partially addressed (TDD planning, task chain generation, verification, compliance reporting), and while it mentions trigger commands, it lacks an explicit 'Use when...' clause describing the situations or user needs that should activate this skill. | 2 / 3 |
Trigger Term Quality | Includes 'workflow-tdd-plan' and 'workflow-tdd-verify' as trigger terms, plus natural terms like 'TDD', 'Red-Green-Refactor', and 'compliance reporting'. However, the primary triggers are command-style slugs rather than natural language a user would say (e.g., 'test-driven development', 'write tests first', 'TDD plan'). | 2 / 3 |
Distinctiveness Conflict Risk | The description is quite specific to a unified TDD workflow combining planning and verification phases, with distinct command-based triggers ('workflow-tdd-plan', 'workflow-tdd-verify') that are unlikely to conflict with other skills. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
47%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill has excellent workflow clarity with well-defined phase sequencing, conditional logic, validation gates, and error recovery tables. However, it is severely over-engineered and verbose — the same 6-phase sequence is described in at least 4 different ways (architecture diagram, execution flow, data flow, coordinator checklist), and inline TodoWrite JSON state examples consume significant tokens without adding proportional value. The content would benefit greatly from consolidating redundant sections and moving detailed examples into the phase reference files.
Suggestions
Consolidate the architecture diagram, execution flow, data flow, and coordinator checklist into a single concise workflow section — currently the same phase sequence is repeated 4+ times.
Move the detailed TodoWrite JSON state transition examples into a separate reference file (e.g., phases/todowrite-patterns.md) and keep only a brief summary in SKILL.md.
Remove the pseudocode JavaScript blocks for mode detection and preference collection — these are trivial routing logic that Claude can infer from the workflow description.
Move the error handling tables and TDD warning patterns to a separate reference file, keeping only a brief error handling policy statement in the main skill.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose at ~500+ lines with massive redundancy. The architecture diagram, data flow, TodoWrite patterns, and coordinator checklists repeat the same phase sequence multiple times. Pseudocode JavaScript for mode detection and preference collection explains trivial concepts. The TodoWrite JSON examples showing state transitions across phases are excessively detailed for an orchestrator skill. | 1 / 3 |
Actionability | Provides concrete phase references (Read('phases/01-session-discovery.md')), structured input/output formats, and specific file paths. However, the JavaScript code blocks are pseudocode (not executable), the actual phase logic is deferred to external files not provided, and many instructions describe what should happen rather than giving executable commands Claude can run. | 2 / 3 |
Workflow Clarity | The multi-step workflow is clearly sequenced with explicit phase ordering, conditional branching (Phase 4 based on conflictRisk), validation checkpoints (Phase 6 TDD structure validation), a user decision gate, and detailed error handling with recovery actions. The coordinator checklists provide step-by-step verification of data flow between phases. | 3 / 3 |
Progressive Disclosure | References 7 phase files via Read() with a clear phase reference table, which is good structure. However, no bundle files are provided so the references cannot be verified, and the SKILL.md itself is monolithic — it inlines enormous amounts of detail (TodoWrite state examples, error tables, warning patterns, full data flow diagrams) that should live in the phase files or separate reference docs. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (528 lines); consider splitting into references/ and linking | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 9 / 11 Passed | |
- Repository
- catlog22/Claude-Code-Workflow
- Commit
227244f
- 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.