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.11x

Quality

96%

Does it follow best practices?

Impact

78%

1.11x

Average score across 3 eval scenarios

Securityby

—

The risk profile of this skill

Quality

Content

92%Scale 1-3

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 instruction skill that provides clear, actionable guidance for breaking plans into issue tracker tickets. Its strengths are the explicit feedback loop with the user before publishing, the concrete issue template, and the efficient use of tokens. The main weakness is that it references external resources (setup command, triage labels, ADRs) without providing clear navigation to them, though this is a minor issue given the skill's otherwise strong structure.

Suggestions

Clarify what '/setup-matt-pocock-skills' provides and where the triage label vocabulary can be found, or link to a reference file that documents these dependencies.

Dimension	Reasoning	Score
Conciseness	The skill is lean and efficient. It doesn't explain what vertical slices or tracer bullets are conceptually beyond what's needed for execution. Every section serves a clear purpose, and the issue template is appropriately concise. The XML-tagged rules are tight and well-scoped.	3 / 3
Actionability	The skill provides a concrete issue body template, specific fields to present to the user (Title, Type, Blocked by, User stories), explicit questions to ask during the quiz step, and clear instructions on publishing order. While there's no executable code, this is an instruction-only skill where the guidance is fully actionable and specific.	3 / 3
Workflow Clarity	The 5-step process is clearly sequenced with logical dependencies between steps. Step 4 provides an explicit validation/feedback loop (iterate until user approves), and step 5 specifies dependency-ordered publishing. The HITL checkpoint before publishing acts as a validation gate for the entire breakdown.	3 / 3
Progressive Disclosure	The content is well-organized with clear sections and the issue template is appropriately separated via XML tags. However, it references external context ('/setup-matt-pocock-skills', triage label vocabulary, ADRs) without clear pointers to where these live. For a standalone skill with no bundle files, some of these references feel under-specified. The content length is reasonable for inline presentation though.	2 / 3
	Total	11 / 12 Passed

Description

100%Scale 1-3

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. It specifies concrete inputs (plan, spec, PRD), outputs (issues on the issue tracker), and methodology (tracer-bullet vertical slices), while the explicit 'Use when' clause covers multiple natural phrasings a user might employ.

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 independently-grabbable issues using tracer-bullet vertical slices) and 'when' (explicit 'Use when' clause covering converting plans to issues, creating implementation tickets, or breaking down work into issues).	3 / 3
Trigger Term Quality	Includes strong natural trigger terms users would say: 'plan', 'spec', 'PRD', 'issues', 'implementation tickets', 'break down work', 'convert a plan into issues', 'issue tracker'. These cover common variations of how users would phrase this request.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with a clear niche: converting planning documents into issue tracker tickets using a specific methodology (tracer-bullet vertical slices). The combination of input types (plan/spec/PRD) and output (issues/tickets) creates a unique trigger profile unlikely to conflict with other skills.	3 / 3
	Total	12 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: whimzyLive/nightshift-ai
Path: plugins/sdlc/skills/to-issues/SKILL.md
Commit: 8a737ca

Reviewed: about 6 hours 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.