CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

to-tickets

Decompose a PRD issue into tracer-bullet tickets — demoable vertical slices sized to one fresh context window, with blocking edges and autonomy labels, published to the project issue tracker. Use after /to-prd when a build spans more than one session; skip it (use /implement directly) when the whole change fits one context window.

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/to-tickets/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

62%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.

The body delivers an exceptionally rigorous, validated workflow with concrete commands and decision procedures, but at a heavy reading cost: monolithic paragraphs, repeated restatements, and inlined infrastructure code. The referenced companion files being absent from the bundle also leaves the progressive-disclosure structure only partly verifiable.

Suggestions

Split the trust-boundary section's ~70 lines of shell functions (vocab_checker, span_ok, prescreen_ok, checked_prescreen) into a scripts/ or references/ file, keeping only the call contract and the pre-screen end-to-end sequence inline.

Tighten the longest passages — rules 15–16 and steps 3–5 — into short normative statements with examples, and state the scratch-home cleanup once (in step 5) instead of three times.

Ship FACTORY.md, RISK.md, DOMAIN-RUBRIC.md, and RETRO-CANDIDATES.md alongside SKILL.md in the bundle so the four relative links resolve and the deferred content is actually available.

DimensionReasoningScore

Conciseness

The body is noticeably verbose: rules 15 and 16 and steps 3–5 are 300–600-word single paragraphs with deeply nested em-dash clauses; the scratch-directory cleanup is stated at least three times (trust-boundary section, 'What the verdict means', step 5); and lines 154–156 re-explain in prose the exact logic the shell functions and their comments already specify. It avoids anchor 1 because nothing explains concepts Claude already knows — every passage is skill-specific — but well beyond anchor 3's 'some unnecessary explanation'.

2 / 5

Actionability

Guidance is concrete and mostly executable: exact commands ('gh issue view "$PRD" --json body --jq .body', the mktemp templates, the full trace.sh emit call with every key), copy-paste shell functions (prescreen_ok, span_ok, checked_prescreen), exact stamp formats, and a first-hit-wins tier rubric. Anchor 5 is missed only because the reader-subagent spawn is deliberately left to the adapter ('the adapter names the command') and several oracle scripts live outside the bundle, leaving minor gaps the operator must fill.

4 / 5

Workflow Clarity

The five-step procedure has explicit validation checkpoints and feedback loops throughout: checked_prescreen gates every read of the untrusted return, refused stamps are 'repaired and checked again, never shown', the coverage check enumerates exit codes 0–3 with re-runs after every change to a Covers: line, a mandatory human quiz gates publication, and cleanup paths exist for both completion and every stop condition. This matches anchor 5's sequence plus feedback loops plus error recovery.

5 / 5

Progressive Disclosure

References are well signaled and one level deep — 'open [FACTORY.md](FACTORY.md) and run its check', 'the rubric is [RISK.md](RISK.md)', '[DOMAIN-RUBRIC.md](DOMAIN-RUBRIC.md)', '[RETRO-CANDIDATES.md](RETRO-CANDIDATES.md)' — and each is loaded exactly when needed. However, none of these four files is present in the evaluated bundle, and roughly 70 lines of trust-boundary shell functions that would naturally live in a scripts/ file are inlined in SKILL.md, which keeps it below anchor 5 and sits between anchors 3 and 4.

4 / 5

Total

15

/

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 about the artifact and its properties, explicit about when to use it and when to skip it, and clearly distinguishable within its toolchain. The only gap is modest synonym coverage for how users might phrase the request.

DimensionReasoningScore

Specificity

The description concretely characterizes the deliverable — 'demoable vertical slices sized to one fresh context window, with blocking edges and autonomy labels, published to the project issue tracker' — naming the artifact and several of its concrete properties. It falls short of anchor 5 because it describes one pipeline action (decompose → publish) rather than a comprehensive list of multiple distinct actions, but it is well above anchor 3's '1-2 concrete actions'.

4 / 5

Completeness

Both halves are explicit: the 'what' (decompose a PRD into tracer-bullet tickets with edges, labels, and tracker publication) and the 'when' with concrete trigger phrasing ('Use after /to-prd when a build spans more than one session'), plus an explicit skip condition ('skip it (use /implement directly) when the whole change fits one context window'). This matches anchor 5; anchor 4's 'when could be more explicit' does not apply.

5 / 5

Trigger Term Quality

Natural phrases for the niche are present: 'Decompose a PRD issue into tracer-bullet tickets', 'Use after /to-prd when a build spans more than one session'. Common variations a user might say — 'break down', 'split the work', 'task breakdown' — are missing, which keeps it at anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche in the planner chain with distinct triggers (/to-prd, /implement, builds spanning sessions) and is unlikely to fire for unrelated skills. This matches anchor 5's 'clear niche with distinct triggers; minimal conflict risk'.

5 / 5

Total

18

/

20

Passed

Validation

75%

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

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

metadata_version

'metadata.version' is missing

Warning

relative_links

Relative link issues: 4 possibly missing (DOMAIN-RUBRIC.md, FACTORY.md, RETRO-CANDIDATES.md, RISK.md)

Warning

referenced_paths_exist

Referenced path issues: 7 possibly missing (scripts/agents.config.sh, scripts/agents.lib.sh, scripts/check.sh, scripts/coverage.sh, scripts/trace.sh, +2 more)

Warning

Total

12

/

16

Passed

Repository

agranado2k/agentic-sdlc

Path

.agents/skills/to-tickets/SKILL.md

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.