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.

1.48x

Quality

81%

Does it follow best practices?

Impact

83%

1.48x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, instruction-only skill with a clear sequenced workflow, concrete templates, and an approval feedback loop. The main gap is the absence of a publish-verification step for the batch issue-creation operation.

Suggestions

Add a publish-verification checkpoint after step 5 (e.g., confirm each issue was created with the expected identifier and needs-triage label, and that 'Blocked by' references resolve to real issues) to strengthen the batch-operation feedback loop.

Tighten the opening line to avoid restating the description, e.g. drop it or reduce to a single sentence pointing straight at the Process.

Optionally split the issue-template into a referenced file if the template grows, keeping SKILL.md as a concise overview.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence, avoiding explanations of concepts Claude already knows; the opening line and the HITL/AFK definitions earn their place, with only minor redundancy against the description.	4 / 5
Actionability	Concrete, actionable guidance: a 5-step process, a numbered quiz format with named fields, and a copy-paste issue template with the needs-triage label; gaps are tracker-specific publish mechanics that are delegated to the configured tracker.	4 / 5
Workflow Clarity	A clearly sequenced 5-step process with an explicit feedback loop ('Iterate until the user approves the breakdown') and a safety guard ('Do NOT close or modify any parent issue'); the publish step lacks an explicit post-publish verification checkpoint.	4 / 5
Progressive Disclosure	Well-organized into Process subsections with inline vertical-slice-rules and issue-template blocks that belong inline; no nested references and no bundle files, though at ~78 lines the under-50-line simple-skill exception does not fully apply.	4 / 5
	Total	16 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete, third-person, with explicit what and when clauses and natural trigger terms. Minor specificity upside would come from enumerating more discrete capabilities.

Dimension	Reasoning	Score
Specificity	Names the domain (plan/spec/PRD) and a concrete method ('independently-grabbable issues' via 'tracer-bullet vertical slices'), but it is essentially one capability rather than several listed actions.	4 / 5
Completeness	Explicitly answers what (break a plan into independently-grabbable issues via tracer-bullet slices) and when (a 'Use when...' clause with three concrete trigger phrases), matching the top anchor.	5 / 5
Trigger Term Quality	Natural trigger phrases are present ('convert a plan into issues', 'create implementation tickets', 'break down work into issues'); a few common variants (e.g. 'write tickets', 'split a spec') are missing.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (issue-tracker decomposition via tracer bullets) with distinct triggers, so overlap with general planning skills is minimal.	5 / 5
	Total	18 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: SnowingFox/ai-skills
Path: .cursor/skills/to-issues/SKILL.md
Commit: d6882ad

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.