to-issues
Break a plan, spec, or PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices. Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues.
100
100%
Does it follow best practices?
Impact
Pending
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 uses natural trigger terms that users would employ. It specifies concrete input types (plan, spec, PRD), a clear output (GitHub issues), and a methodology (tracer-bullet vertical slices), making it highly distinctive and easy for Claude to select appropriately.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: 'Break a plan, spec, or PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices.' This describes a clear methodology (tracer-bullet vertical slices) and specific input types (plan, spec, PRD) and output (GitHub issues). | 3 / 3 |
Completeness | Clearly answers both what ('Break a plan, spec, or PRD into independently-grabbable GitHub issues using tracer-bullet vertical slices') and when ('Use when user wants to convert a plan into issues, create implementation tickets, or break down work into issues') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'plan', 'spec', 'PRD', 'GitHub issues', 'implementation tickets', 'break down work', 'convert a plan into issues'. These cover multiple natural phrasings a user might use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: converting plans/specs/PRDs specifically into GitHub issues using a specific methodology (tracer-bullet vertical slices). Unlikely to conflict with general project management or coding skills due to the specific input-output pairing and methodology. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that efficiently guides Claude through breaking plans into GitHub issues. It excels in workflow clarity with an explicit human-in-the-loop validation step (Step 4) before the destructive action of creating issues (Step 5), and the issue template provides concrete, copy-paste-ready structure. The vertical slice rules and HITL/AFK distinction add genuine value without being verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It doesn't explain what GitHub issues are, what vertical slices are conceptually beyond what's needed, or how `gh` CLI works. Every section serves a clear purpose and no tokens are wasted on things Claude already knows. | 3 / 3 |
Actionability | Provides concrete commands (`gh issue view <number>`, `gh issue create`), a specific issue body template with exact markdown structure, a clear numbered list format for presenting slices to users, and explicit fields (Title, Type, Blocked by, User stories covered). The guidance is specific enough to execute directly. | 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) → create issues. Step 4 is an explicit validation checkpoint with specific questions to ask, and step 5 specifies dependency ordering to ensure correct issue number references. The iterate-until-approved loop is a strong feedback mechanism. | 3 / 3 |
Progressive Disclosure | For a skill of this size (~60 lines of meaningful content), the structure is well-organized with clear sections, embedded templates using XML tags for scannability, and no need for external file references. The content is appropriately scoped and doesn't need to be split further. | 3 / 3 |
Total | 12 / 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
edd9893
- 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.