Content
73%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A solid, well-sequenced planning workflow with copy-paste-ready templates for requirements (EARS) and tasks, and explicit confirmation gates between phases. The main weaknesses are the triple-stated use/skip decision guidance (token waste) and a Design phase that is less concretely scaffolded than the others.
Suggestions
Consolidate the three overlapping decision sections ('Activation Contract', 'When to use this skill', 'Decision rule') into a single use/skip section — the repeated trigger guidance is the largest source of wasted tokens.
Add a short design.md template or annotated example (parallel to the EARS pattern and task format) so the Design phase is as actionable as Requirements and Tasks.
Fold the 'Common mistakes / gotchas' entries into the phase guidance they relate to, trimming items that merely restate the confirmation rule stated elsewhere.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The use/skip decision guidance is stated three separate times ('Activation Contract' with 'Use this first when'/'Do NOT use for', 'When to use this skill', and 'Decision rule' with 'Use the full workflow when'/'Skip the full workflow when'), which is noticeable redundancy; the rest of the body is tight bullets with no over-explanation of concepts Claude already knows. This fits anchor 3 (mostly efficient but could be tightened) rather than 4, where trimming would be only minor. | 3 / 5 |
Actionability | Concrete scaffolds are provided: exact artifact paths ('specs/<spec_name>/requirements.md', 'design.md', 'tasks.md'), a copy-paste EARS pattern template with a worked example ('When the user submits the form, the booking system shall validate required fields...'), and a task-format template ('- [ ] 1. Task title ... _Requirement: 1'). Anchor 4 fits: mostly executable guidance with minor gaps — the Design phase ('Describe architecture and module boundaries', 'Explain technology choices and trade-offs') has no comparable template or example. | 4 / 5 |
Workflow Clarity | The four phases (Requirements -> Design -> Tasks -> Execution) are explicitly sequenced with user-confirmation checkpoints between each: 'Get confirmation before moving to the next phase', 'Require confirmation between requirements, design, and task breakdown', and 'Only start implementation after the user confirms the task plan', plus an entry 'Minimal checklist'. This matches anchor 5 (clear sequence with explicit validation steps and a checklist); anchor 4 falls short because all inter-phase checkpoints are present, and no destructive/batch-operation cap applies to a planning workflow. | 5 / 5 |
Progressive Disclosure | No bundle files exist, and the single-file body is well organized with clear sections; sibling-skill references ('../ui-design/SKILL.md', '../postgresql-development-cloudbase/SKILL.md') are clearly signaled and one level deep. Anchor 4 fits (good structure, minor organization gaps) rather than 5, since the redundant decision sections and 'Common mistakes' list leave minor organization gaps and there is no overview/reference split to evaluate. | 4 / 5 |
Total | 16 / 20 Passed |