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 well-engineered orchestration skill: the step sequence is unambiguous, validation gates (branch confirmation, Phase 1.8 approval, STOP conditions) are explicit, and every override of a sibling skill's behavior is stated with the exact flag to use. The main cost is redundancy — Common Mistakes, Red flags, and Important restate the same three rules, inflating tokens without adding guidance.
Suggestions
Merge "Common Mistakes" and "Red flags" into a single section: their rows cover the same three rules (suppress intermediate handoffs, skip brainstorm on specced tickets, trust the brief), and each duplicate row costs tokens on every load.
Consolidate the "Important" section into the merged mistakes section, keeping only the two rules not already stated elsewhere (never write production code; always end Step 0 on the feature branch or STOP).
State the --no-handoff override mechanism once in a short note before Step 3 instead of fully re-explaining it in both Step 3 and Step 4 — Step 4 can then just say "override the terminal handoff as in Step 3".
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient, but three overlapping closing sections ("Common Mistakes", "Red flags", "Important") each restate the same rules about suppressing intermediate handoffs, honoring Phase 1.8, and staying on the feature branch, and Steps 3 and 4 repeat the OVERRIDE explanation. This fits anchor 3 ("could be tightened") better than anchor 4, where over-explanation would be only minor. | 3 / 5 |
Actionability | Guidance is mostly executable: a concrete bash worktree block with a fallback for an existing branch, an explicit ticket-key regex, exact override flags ("--no-handoff"), and the exact spawn command `devflow:phase-handoff --phase lock-tests --next-phase impl`. Minor gaps keep it at anchor 4 rather than 5 — placeholders like `slug="<short-kebab-summary>"` and `repo_root` are not copy-paste ready. | 4 / 5 |
Workflow Clarity | Steps 0-6 with a mermaid flowchart give a clear sequence, and validation is explicit: "Confirm: `git branch --show-current` == `$branch`. If not, STOP", Phase 1.5 "verify each fails for the right reason", the Phase 1.8 user-approval gate ("Do NOT proceed past Phase 1.8 without explicit approval"), and a STOP-if-worktree-fails rule. This matches the anchor-5 pattern of explicit checkpoints with feedback loops. | 5 / 5 |
Progressive Disclosure | No bundle files exist (no references/, scripts/, or assets/), and the single SKILL.md is well-sectioned with one-level, clearly-signaled references to sibling devflow skills — never nested. It is anchor 4 rather than 5 only because the duplicated content across the three closing sections could be consolidated, a minor organization gap. | 4 / 5 |
Total | 16 / 20 Passed |