Code Review & Testing · IN-DEPTH PROFILE

To Tickets Skill

To Tickets breaks an agreed plan, specification, or conversation into small, verifiable tracer-bullet tickets.

View listed source ↗Installation guide ↓
Best for

Teams preparing a multi-ticket implementation

What you get

Split work into vertical slices + Record blocking edges

Main limitation

The configured tracker and label conventions must be known; the Skill asks the user to review ticket granularity and dependencies first.

First risk

Creating tracker work before it is approved. Publishing creates project work items and may assign ready-for-agent labels. Review every ticket, dependency, tracker, and destination before approving publication.

EVIDENCE FRESHNESS

Three checks, kept separate

A recent source check is not a runtime test or security audit.

Upstream sourceChecked 2026-09-23

Pinned revision · c55ee460

Open pinned commit ↗
SkillSignal profileSource-grounded

Updated 2026-08-20

Runtime & securityNot independently verified

Source review does not certify behavior or safety.

IN PLAIN ENGLISH

What it does—and when it fits

To Tickets breaks an agreed plan, specification, or conversation into small, verifiable tracer-bullet tickets. Each ticket describes a complete vertical slice and records blocking dependencies before the approved set is published to the configured tracker.

This is aimed at Teams preparing a multi-ticket implementation. Compare the examples below with your task, then review the limitations, permissions, and risks before installing.

What you get
  • Split work into vertical slicesCreate independently demoable tickets spanning the relevant layers.
  • Record blocking edgesShow which tickets genuinely need to finish before others can begin.
  • Prepare work for deliveryOrder approved local files or tracker issues in dependency order.
What makes it different
  • This profile is manually organized around the current upstream SKILL.md workflow.
  • The capability boundary remains explicitly tied to mattpocock/skills.
  • Core uses, limitations, and risks are separated for pre-install review.
Community signalskills.sh All-time: #76 · 557.9K installs

No verified review text is in the current dataset. Use the linked source for the latest discussion.

Read the source note ↗

INSTALL BY AGENT

Choose your Agent

Paths come from official Agent docs or the universal installer behind skills.sh. Compatibility still follows this Skill's record.

Native

This Skill's current record explicitly names this Agent. Still inspect scripts, permissions, and external dependencies first.

Project install (recommended)
npx skills add https://github.com/mattpocock/skills --skill to-tickets --agent claude-code
Personal install
npx skills add https://github.com/mattpocock/skills --skill to-tickets --agent claude-code -g

Project install stays with this repository for team sharing. Personal install adds -g and works across repositories.

View install paths
Project path.claude/skills/to-tickets/
Personal path~/.claude/skills/to-tickets/
Official agent docs

Claude Code discovers custom Skill folders automatically at project or personal scope.

View path evidence ↗

TYPICAL WORKFLOW

A practical workflow

01

Split work into vertical slices

Create independently demoable tickets spanning the relevant layers.

02

Record blocking edges

Show which tickets genuinely need to finish before others can begin.

03

Prepare work for delivery

Order approved local files or tracker issues in dependency order.

THE TRADEOFFS

Advantages and tradeoffs

Notable strengths

  1. This profile is manually organized around the current upstream SKILL.md workflow.
  2. The capability boundary remains explicitly tied to mattpocock/skills.
  3. Core uses, limitations, and risks are separated for pre-install review.

Limitations

  1. The configured tracker and label conventions must be known; the Skill asks the user to review ticket granularity and dependencies first.
  2. Ticket decomposition clarifies execution but does not validate that the product plan itself is correct.

COMPARE THE TRADEOFF

Consider these close alternatives

These are deterministic nearby candidates, not paid placements or a universal ranking. Open the full profile before choosing.

01

Same job family · native to Claude Code + Codex

frontend-design

Design constraints that push generated interfaces beyond generic AI UI.
Tradeoff to check
Aesthetic judgments remain subjective and still need stakeholder review.
First risk
Style over function · Medium
Source state
Pinned · 34040c9c
Open frontend-design profile ↗
02

Same job family · native to Codex + Claude Code

web-design-guidelines

Review interfaces against practical web design and accessibility rules.
Tradeoff to check
It depends on network access and a live guideline document whose contents can change over time.
First risk
Rule drift or context-free findings · Medium
Source state
Pinned · 063bee94
Open web-design-guidelines profile ↗
03

Same job family · native to Codex + Claude Code

anti-ui-slop

Instruction-only, product-specific UI design contracts with optional real-interface evidence and a hard finish gate.
Tradeoff to check
Repository evidence is required; UIZZE references or user-provided screenshots are optional, and missing reference evidence should be labeled rather than guessed.
First risk
Copying external interface patterns too literally · Medium
Source state
Pinned · 1f564408
Open anti-ui-slop profile ↗
Compare more in the directory →

BEST FIT

Who it is for

→

Teams preparing a multi-ticket implementation

→

Leads who need visible blockers and a clear delivery order

BEFORE YOU USE IT

Risks to review before use

High

Creating tracker work before it is approved

Publishing creates project work items and may assign ready-for-agent labels. Review every ticket, dependency, tracker, and destination before approving publication.

Medium

Upstream instruction drift

Behavior can change with upstream updates. Record the commit used for important workflows and review updates before adoption.

SECURITY

What the permission profile means

  • Declared access remains governed by the current upstream SKILL.md and runtime requests.
  • Treat repository files, web content, and tool output as untrusted input.
  • SkillSignal has not independently executed or security-audited this package; external skills.sh labels are not SkillSignal certification.

Not a security certification. External ratings are attributed references. SkillSignal has not independently executed or security-reviewed this Skill.

COMMON QUESTIONS

To Tickets Skill FAQ

What is the To Tickets Skill?

To Tickets breaks an agreed plan, specification, or conversation into small, verifiable tracer-bullet tickets. Each ticket describes a complete vertical slice and records blocking dependencies before the approved set is published to the configured tracker.

How do I install the To Tickets Skill?

Open and review the listed source, choose the project or personal path for your Agent, then verify the first run in a controlled project. Open the listed skills.sh page and upstream repository; verify the current SKILL.md.

Is the To Tickets Skill safe to use?

SkillSignal checked the source on 2026-09-23, but that is not a runtime test or security certification. Review the “Creating tracker work before it is approved” risk first and begin with the least access required.

INSIDE THE PACKAGE

Indexed files

SKILL.mdUpstream Skill instructionsSource-linked

TAGS

ticket-planningvertical-slicesdependencies

Manually expanded from the current upstream SKILL.md and linked source at mattpocock/skills, checked 2026-08-20. This is an original summary, not an execution result or security certification.