Content
66%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.
The body delivers an exceptionally clear, well-checkpointed workflow with concrete commands and complete templates, and it externalizes domain depth into four real, one-level-deep reference files. Its main weaknesses are significant redundancy (triple-stated pushback rules, persona theatrics, duplicated Overview) and the inlining of the large plan template that belongs in a reference file.
Suggestions
State the pushback rule and /sdlc-write-code handoff once in a single Boundary section and reference it from Phases 2-4 instead of repeating it three times.
Remove the persona-activation theatrics ("CRITICAL SYSTEM OVERRIDE", commanded identity shift, session-lock rules) and the duplicative Overview section; they add tokens without adding instruction.
Move the Mandatory Refactoring Plan Template (~80 lines) into a reference file such as PLAN-TEMPLATE.md, keeping SKILL.md as an overview with a clearly signaled link, consistent with the other four references.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Noticeably verbose: persona theatrics ("CRITICAL SYSTEM OVERRIDE", "YOU ARE HEREBY COMMANDED TO STOP ACTING AS A GENERAL ASSISTANT"), an Overview that restates the persona section, and the pushback/handoff rule repeated three times (Core Directives, Boundary & Pushback Rules, Phase 4). Several padded sections that assume Claude needs role-play framing it does not. | 2 / 5 |
Actionability | Highly concrete: the exact diff command "git diff <fixed-point>...HEAD" (three-dot, against the merge-base), explicit sub-agent prompt instructions, verbatim report and plan templates with task tables, and exact pushback wording. Minor gap: it depends on environment-specific tool names ("invoke_subagent", "view_file", "write_to_file") that may not exist in the executing harness, keeping it below fully copy-paste ready. | 4 / 5 |
Workflow Clarity | Clear sequence with explicit validation and feedback loops: Phase 1's five steps include "Confirm the diff is non-empty before proceeding" and Step 5 "Verify the Verification"; missing inputs trigger asking the user; Phase 2 is skipped when no critical/required issues exist; Phase 3 is an explicit remediation loop updating plans from audit reports; templates embed VERIFY/APPROVAL checkpoints and severity-label checklists. | 5 / 5 |
Progressive Disclosure | A dedicated "Mandatory References" section describes all four reference files, each of which exists in references/ and is one level deep (no nested references verified). However, roughly 120 lines of templates are inlined in the body — the 80-line Mandatory Refactoring Plan Template is a strong candidate for its own reference file, which is a moderate organization gap rather than a minor one. | 4 / 5 |
Total | 15 / 20 Passed |