to-issues
Break a plan, spec, or PRD into independently-grabbable issues on the project issue tracker using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
77
96%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly communicates what the skill does, when to use it, and occupies a distinct niche. It uses concrete terminology (PRD, tracer-bullet vertical slices, issue tracker) alongside natural user language (tickets, break down work). The explicit 'Use when' clause with multiple trigger phrases ensures good discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'Break a plan, spec, or PRD into independently-grabbable issues', 'using tracer-bullet vertical slices'. It names the input types (plan, spec, PRD) and the output (issues on the project issue tracker) with a specific methodology. | 3 / 3 |
Completeness | Clearly answers both 'what' (break plans/specs/PRDs into vertical-slice issues on the issue tracker) and 'when' (explicit 'Use when' clause covering converting plans to issues, creating tickets, breaking down work). | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'plan', 'spec', 'PRD', 'issues', 'implementation tickets', 'break down work', 'issue tracker', 'convert a plan into issues'. Good coverage of common variations. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: converting planning documents into issue tracker tickets using vertical slices. The combination of input types (plan/spec/PRD), output (issues/tickets), and methodology (tracer-bullet slices) makes it unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, well-crafted skill that provides clear, actionable guidance for breaking plans into issue tracker tickets. The workflow is well-sequenced with an explicit user feedback loop before publishing, and the issue template is concrete and ready to use. The only weakness is the reference to external setup/vocabulary without clear pointers to where those materials live.
Suggestions
Clarify where the 'triage label vocabulary' and issue tracker configuration are defined — either inline the reference path or explain what '/setup-matt-pocock-skills' provides so the skill is more self-contained.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. It assumes Claude's competence throughout — no unnecessary explanations of what issues are, what vertical slices mean conceptually, or how issue trackers work. Every section earns its place with actionable guidance. | 3 / 3 |
Actionability | The skill provides a concrete issue body template, specific fields to present during the quiz step, clear criteria for HITL vs AFK classification, and explicit rules for vertical slices. While there's no executable code, this is an instruction-only skill where the guidance is highly specific and actionable — the template is copy-paste ready. | 3 / 3 |
Workflow Clarity | The 5-step process is clearly sequenced with logical progression: gather context → explore codebase → draft slices → quiz user (explicit feedback loop with iteration) → publish in dependency order. The human-in-the-loop validation at step 4 serves as a strong checkpoint before the publishing step, and the instruction to publish in dependency order shows attention to sequencing correctness. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and the issue template is appropriately inlined. However, the reference to '/setup-matt-pocock-skills' and 'triage label vocabulary' assumes external context without clear signaling of where that content lives. For a standalone skill with no bundle files, the content is reasonably structured but could benefit from clearer navigation to supporting materials. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- mattpocock/skills
- Commit
0288510
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.