Content
92%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 is a well-crafted extension skill: it assumes the base skill, inlines only operational deltas, and backs every fragile operation (worktree recovery, chapter marking, terminal titling) with executable code, validation, and failure fallbacks. Its only weakness is mild comment verbosity in the bash block.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and operational with no concept explanations Claude already knows — every section is a concrete addition ('Step 0 — Re-establish the feature worktree', 'Invoke devflow:phase-handoff with arguments --phase plan --next-phase lock-tests'). Minor over-explanation remains in inline rationale comments ('(`[ -d ]` alone would skip recovery for a stale non-worktree dir or a detached/wrong-branch checkout.)', '(not awk $2) so worktree paths containing spaces survive') that could be trimmed slightly, so it sits just below the lean-everywhere anchor. | 4 / 5 |
Actionability | Fully executable, copy-paste-ready guidance: a complete bash worktree-recovery script with placeholders sourced from the handoff block, a concrete regex ('[A-Z]+-[0-9]+'), a literal mark_chapter payload, an exact printf escape sequence, and exact invocation arguments ('--phase plan --next-phase lock-tests'). Not level 4 territory because no key execution detail is missing — even the spawned-session title format is specified. | 5 / 5 |
Workflow Clarity | Sequencing is explicit and event-anchored ('do this before anything else', 'Before: First action of the skill', 'After: Plan saved to disk'), with a hard validation checkpoint and error path in the script: the branch-validity guard plus '[ "$on" = "$feature_branch" ] || { echo "WORKTREE RECOVERY FAILED..."; exit 1; }'. It also includes recovery fallbacks (reusing an existing checkout when worktree add fails) and graceful degradation (skip mark_chapter silently if unavailable), matching the feedback-loop anchor. | 5 / 5 |
Progressive Disclosure | The skill is itself a thin delta layer: it delegates the entire base workflow to 'superpowers:writing-plans' and 'devflow:phase-handoff' and inlines only the additions, which is exactly the appropriate split. What remains inline (~55 lines) is operational content that must be present, organized under clear headers, with no nested references — no references/, scripts/, or assets/ exist in the bundle, and nothing inlined belongs in a separate file. | 5 / 5 |
Total | 19 / 20 Passed |