Content
82%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-structured, actionable skill body that cleanly separates planning from execution and leans on concrete shep commands. The main gap is the missing templates/workstream-plan.md file referenced for Step 4.
Suggestions
Add the missing templates/workstream-plan.md file (referenced in Step 4) or replace the reference with an inline template so the guidance is self-contained.
Trim motivational prose like 'The plan is cheap. Rework across six half-merged branches is not.' to tighten token efficiency.
Add an explicit validate/fix/retry loop for the merge step (e.g., what to do when a rebase surfaces conflicts after a parent merge) to push workflow clarity to the top anchor.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is largely lean and assumes Claude's competence, with a small amount of motivational editorializing ('The plan is cheap. Rework across six half-merged branches is not.') that could be trimmed. | 4 / 5 |
Actionability | Provides copy-paste-ready bash invocations with real flags ('shep feat new ... --repo ... --attach ... --push --pr') and situation-to-command tables that cover the common cases. | 5 / 5 |
Workflow Clarity | Two hard-separated phases with numbered steps and an explicit approval gate plus a post-merge 're-check shep feat ls' checkpoint; falls just short of a 5 due to the absence of an explicit validate->fix->retry error-recovery loop. | 4 / 5 |
Progressive Disclosure | Well-signaled, one-level-deep references to references/partitioning.md and references/cli-reference.md (both present), but templates/workstream-plan.md is referenced in Step 4 yet does not exist in the bundle. | 4 / 5 |
Total | 17 / 20 Passed |