Content
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured process skill with concrete actionability, explicit validation checkpoints, and clear workflow sequencing. Its main weakness is conciseness: the approval/wait directive and HARD-GATE are repeated across multiple sections and could be consolidated.
Suggestions
Consolidate the three HARD-GATE blocks into a single gated checkpoint referenced once, since the 'STOP and wait for explicit approval' directive is already reinforced by the Checklist and Process Flow diagram.
Dedupe the 'do not invoke writing-plans / any other skill until confirmed' instruction, which currently appears in both the Checklist and the 'After the Design' section.
Tighten the Dialogue and Key Principles sections, which restate guidance (e.g., one-question-at-a-time, 2-3 approaches) already covered earlier in the Checklist.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body assumes Claude's competence (no concept lecturing) but pads via repetition: the HARD-GATE appears three times and the 'STOP and wait for explicit approval' directive is restated across the Checklist, Process Flow, Dialogue, and After-the-Design sections, so it 'could be tightened' rather than having every token earn its place. | 2 / 3 |
Actionability | Concrete, executable guidance throughout — an exact detection command ('git worktree list --porcelain | grep -A2 "$(pwd)"'), a concrete file path ('docs/plans/YYYY-MM-DD-<topic>-design.md'), and a branch-naming rule ('feature/ prefix, kebab-case') — matching the 'fully executable...copy-paste ready' anchor; absence of code is fine for this instruction-only skill. | 3 / 3 |
Workflow Clarity | A clear 10-step numbered sequence with explicit validation checkpoints (three HARD-GATE approval gates), a revise-and-re-present feedback loop, a visual process-flow diagram, and dedicated re-entry handling — matching the 'clear sequence with explicit validation steps; feedback loops for error recovery' anchor. | 3 / 3 |
Progressive Disclosure | A single self-contained file with no bundle references (verified: no references/scripts/assets directories exist) and clean section headings providing easy navigation; nothing needs externalizing, so per the simple-skills note the well-organized structure merits a high score rather than the 'content that should be separate is inline' level below. | 3 / 3 |
Total | 11 / 12 Passed |