Content
56%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 strong on safety engineering — validation and fail-safe fallbacks for every risky step are exemplary — and its git commands are concrete and mostly executable. Its weaknesses are redundancy (the same permission and preservation rules restated many times), an incoherent sentence fragment at the top of the rotation section, and a monolithic layout that inlines a long script and rule sets that belong in bundle files.
Suggestions
Consolidate the repeated authorization rules into a single stated rule set in the Activation guard; the current text restates 'no permission needed in a task-owned worktree' and 'never stash/discard/overwrite' in at least four separate sections.
Fix the broken sentence opening the post-merge rotation script block ('immutable `ship_merge_head_oid` captured before the guarded merge...') and move the ~70-line bash script into a scripts/ file with a short inline summary of its fail-safe conditions.
Reorder the body so the general Steps workflow precedes the specialized post-merge /ship rotation path, or split the rotation path into its own referenced section, so a reader encounters the common case first.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body restates the same authorization rules repeatedly — "needs no extra permission" / "without asking" / "do not pause to ask" appears across the Activation guard, Steve's standing instruction, Preserve branch ownership, the Post-merge rotation intro, and Steps; "never stash, discard, or overwrite" and the Builder.io/Fusion carve-out each appear three-plus times. This matches anchor 2 ("noticeably verbose; several unnecessary... padded sections") — the content is policy-dense, not concept-explaining, so it stays above 1, but the redundancy is well beyond anchor 3's 'some' tightening. | 2 / 5 |
Actionability | Concrete executable commands are provided throughout — the pre-flight fetch/gh pr list/git log triple, the branch-naming resolution via `gh api user --jq .login`, and a ~70-line fail-safe bash rotation script with per-step error handling. Not 5 because the script embeds unresolved placeholders (`<persisted-ship_merge_head_oid>`, `<github-username>/changes-N`), the naming rule is split from the script that uses it, and some guidance remains abstract ("choose a safe branch", "the freshest base that preserves all current work"). | 4 / 5 |
Workflow Clarity | Validation checkpoints are unusually strong for a risky operation: the pre-flight section mandates comparing the merge-commit SHA with wait-and-re-fetch recovery, and the rotation script validates ancestry, local/remote unpublished commits, and dirty publishable paths with explicit keep-the-source-branch fallbacks on every failure. This avoids the destructive-operation cap. Below 5 because the section sequence is muddled — Steps arrives after Post-merge rotation, the rotation section opens with a broken mid-sentence fragment ("immutable `ship_merge_head_oid` captured before the guarded merge..."), and the guard rules are scattered rather than assembled into one ordered checklist. | 4 / 5 |
Progressive Disclosure | Section headers exist and are sensible (Activation guard, Pre-flight, Post-merge rotation, Steps, Branch naming, After creation, Important), but everything lives inline in one ~200-line file: the ~70-line rotation script, the naming rules, and the ownership policy each read as content that belongs in a scripts/ file or a separate reference, and the only pointer to outside material (`Follow babysit-pr`) is a bare inline mention, not a clearly signaled reference. This matches anchor 3 (structure present, but content that should be separate is inline). | 3 / 5 |
Total | 13 / 20 Passed |