Content
85%Reviews 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-sequenced, lean instruction workflow with an explicit user-approval checkpoint before publishing and a concrete issue template; its only gap is that the actual issue-tracker publishing mechanism is delegated elsewhere rather than specified.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and directive — it assumes Claude knows what a PRD or issue tracker is and never pads with background; every section ('Gather context', 'Draft vertical slices', the issue template) earns its place, matching the level-3 'lean and efficient; assumes Claude's competence' anchor. | 3 / 3 |
Actionability | Guidance is concrete in places (a copy-paste issue body template, numbered quiz prompts, acceptance-criteria checklist), but the core publish step is abstract — 'publish a new issue to the issue tracker' with the mechanism delegated to /setup-matt-pocock-skills — leaving key execution details unspecified, which fits level-2 'some concrete guidance but incomplete; missing key details' rather than level-3. | 2 / 3 |
Workflow Clarity | Five clearly sequenced steps lead to an explicit validation checkpoint — 'Iterate until the user approves the breakdown' — before the batch publish action, with a feedback loop and checklist, matching the level-3 'clear sequence with explicit validation steps; feedback loops' anchor; the destructive/batch caveat is satisfied because approval gates publishing. | 3 / 3 |
Progressive Disclosure | No bundle files exist and the single-file body is well-organized under clear headers with inline-tagged blocks (<vertical-slice-rules>, <issue-template>); there are no nested/deep references, so navigation is easy, matching level-3 'well-organized sections' for a self-contained instruction skill. | 3 / 3 |
Total | 11 / 12 Passed |