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

79%

Does it follow best practices?

Impact

78%

1.11x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/sdlc/skills/to-issues/SKILL.md

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, actionable instruction skill with a clear sequenced workflow and built-in user-approval feedback loop. The main gaps are a missing worked example and lack of post-publish verification.

Suggestions

Add one short worked example of a completed issue (title, type, blocked-by, body) to make the template copy-paste concrete.

Add a post-publish verification step (e.g. confirm each issue was created with the correct triage label and correct 'Blocked by' references) to the workflow.

Tighten the AFK-readiness and prototype-snippet prose to remove minor verbosity.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, avoiding over-explanation of concepts; not a 5 because a few prose passages (e.g. the AFK readiness note, the prototype-snippet exception) could be tightened slightly.	4 / 5
Actionability	Provides concrete, copy-paste-ready guidance via the issue-template, vertical-slice-rules, and explicit quiz fields; not a 5 because it lacks a fully worked example of a published issue to anchor the template.	4 / 5
Workflow Clarity	A clearly numbered five-step sequence with an explicit validation checkpoint ('Quiz the user', 'Iterate until the user approves') before the batch publish step; not a 5 because there is no post-publish verification or error-recovery guidance for failed publishes.	4 / 5
Progressive Disclosure	Well-organized into clearly signaled sections and tagged blocks (vertical-slice-rules, issue-template) with no nested references; not a 5 because the skill exceeds 50 lines with the template inlined rather than split into a reference file.	4 / 5
	Total	16 / 20 Passed

Description

83%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, concrete description that clearly states both capability and trigger conditions with natural synonyms. It is distinct and well-targeted, with only minor overlap and keyword-coverage gaps.

Dimension	Reasoning	Score
Specificity	Names the domain and concrete actions ('Break a plan, spec, or PRD into independently-grabbable issues', 'using tracer-bullet vertical slices', 'on the project issue tracker'), with minor coverage gaps; not a 5 because it is essentially one core action rather than multiple distinct concrete actions.	4 / 5
Completeness	Explicitly answers both what ('Break a plan... into independently-grabbable 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 concrete trigger phrases.	5 / 5
Trigger Term Quality	Provides good keyword coverage with natural synonyms users would say ('convert a plan into issues', 'create implementation tickets', 'break down work into issues'); not a 5 because a few natural variations are absent and file extensions do not apply.	4 / 5
Distinctiveness Conflict Risk	The tracer-bullet/vertical-slice and issue-tracker framing carves a clear niche with mostly distinct triggers; not a 5 because 'break down work into issues' has minor overlap risk with general planning or spec-drafting skills.	4 / 5
	Total	17 / 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: whimzyLive/nightshift-ai
Path: plugins/sdlc/skills/to-issues/SKILL.md
Commit: a2b4df7

Reviewed: 3 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.