Content
85%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 high-quality instruction-only skill body: a clear five-layer framework, an 8-step workflow with explicit validation gates, concrete defaults and thresholds, and proper offloading of framework detail to a real, one-level-deep reference. The main improvement opportunities are de-duplicating the strategy-missing guidance and adding a brief worked example to make the output format fully concrete.
Suggestions
State the 'strategy must exist first' requirement once (Step 1 or Required inputs) and reference it elsewhere instead of repeating it three times.
Add a short worked example (one sample initiative brief or one filled-in 'Not now' entry with reason and re-entry trigger) to anchor the output format.
Trim rhetorical framing lines (e.g., the layer intro 'A roadmap is only as good as its weakest one') where the surrounding checklists already carry the point.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Dense, opinionated guidance ("Engineers: 60-70% of time on roadmap initiatives", "If the math says the plan needs 100% of the team, the plan is wrong. Cut.") with no re-explanation of concepts Claude already knows. Not 5: the "strategy missing" point is repeated in Required inputs, the framework intro, and Step 1, and a few rhetorical asides could be trimmed. | 4 / 5 |
Actionability | Concrete, executable instruction-guidance throughout: exact backlog-catalog fields (Name/Theme/Source/Size/Owner/Status), default capacity percentages by role, cadence rules ("month-by-month for one quarter, quarter-by-quarter beyond"), and a fixed output-section checklist. Not 5: no worked example (e.g., a sample initiative brief or a filled-in "Not now" entry) to anchor the most common case. | 4 / 5 |
Workflow Clarity | Eight clearly sequenced steps with two explicit go/no-go gates ("If the strategy is missing or vague, stop"; "If the team says the plan is impossible, the plan is impossible. Adjust."), embedded warning flags (no-theme items, multiple unmet dependencies), and a failure-patterns section for error recovery. Checkpoints are explicit rather than implicit, matching the 5 anchor. | 5 / 5 |
Progressive Disclosure | The body is a well-organized overview with one clearly signaled, one-level-deep reference: references/prioritization-frameworks.md exists, is linked twice with a description, and properly absorbs the deep framework detail (RICE math, MoSCoW buckets) that would otherwise bloat the main file. Matches the 5 anchor (clear overview, well-signaled references, appropriate split). | 5 / 5 |
Total | 18 / 20 Passed |