Turn Plans Into Agent-Ready Tickets
Large engineering plans often become vague task lists with unclear dependencies. This skill turns plans into vertical-slice tickets with blockers, acceptance criteria, and tracker-ready wording.
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "to-tickets" from https://skillstore.io/skills/mattpocock-to-tickets.md and its manifest at https://skillstore.io/api/skills/mattpocock-to-tickets/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Using "to-tickets". A checkout redesign needs backend flags, API changes, UI updates, and tests.
Expected outcome:
A numbered ticket plan with one setup ticket, several independently testable vertical slices, blocker relationships, and acceptance criteria.
Using "to-tickets". A shared status field must be renamed across many packages.
Expected outcome:
An expand-contract sequence with migration batches, dependency ordering, and a final cleanup ticket.
Using "to-tickets". A team wants local planning output instead of tracker issues.
Expected outcome:
A tickets.md-style plan ordered by blockers, with each ticket describing user-visible behavior and verification steps.
The static findings are false positives caused by Markdown inline code spans around slash commands and template labels, not shell backtick execution. I found no prompt injection text, data exfiltration intent, or malicious system reconnaissance in SKILL.md.
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
https://skillstore.io/skills/mattpocock-to-tickets/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/mattpocock-to-tickets?utm_source=security_passport_badge)<a href="https://skillstore.io/skills/mattpocock-to-tickets?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/mattpocock-to-tickets/security.svg" alt="Skillstore security assessment" loading="lazy"></a><iframe src="https://skillstore.io/embed/skills/mattpocock-to-tickets.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>mattpocock. (2026). to-tickets security audit report (audit version 2) [Author version unspecified]. Skillstore. https://skillstore.io/skills/mattpocock-to-tickets/audits/2@techreport{mattpocock-mattpocock-to-tickets-2026,
author = {mattpocock},
title = {to-tickets security audit report (audit version 2)},
institution = {Skillstore},
year = {2026},
number = {2},
url = {https://skillstore.io/skills/mattpocock-to-tickets/audits/2},
note = {Author version unspecified}
}cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "to-tickets security audit report (audit version 2)"
version: "unspecified"
type: report
authors:
- name: "mattpocock"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/mattpocock-to-tickets/audits/2"
identifiers:
- type: other
value: "skillstore:mattpocock-to-tickets:audit:2"
description: "Skillstore immutable audit report identifier"
Convert a feature spec into small tickets that can ship and verify independently.
Create ready-for-agent tickets with clear blockers and acceptance criteria.
Split wide refactors into expand, migrate, contract, and verification tickets.
Use to-tickets to turn the plan in this conversation into a small set of vertical-slice tickets.
Use to-tickets with the spec at docs/feature-plan.md. Draft tickets, blockers, and acceptance criteria before publishing.
Use to-tickets for issue #42. Read the issue context, propose the ticket breakdown, and ask for approval before publishing.
Use to-tickets to sequence this refactor with expand, migrate, contract, and final verification tickets. Preserve green CI between batches.
Author
mattpocockLicense
MIT
Skillstore revision
r1
Version notice
The author did not declare a version.
Ref
1bf22d3f5624f0760cf4b4337c7dfa2efb3bd403
Maintenance freshness
7/18/2026
Usage
1 downloads · 0 views
File structure
📄 SKILL.md
Guide TDD with Red-Green-Refactor
Test-first work often becomes brittle when teams test internals or write too many tests upfront. This skill guides Codex, Claude, and Claude Code through behavior-focused red-green-refactor cycles.
Sharpen Plans and Create Decision Documentation
Unresolved assumptions weaken plans and technical designs. This skill conducts a focused interview and uses domain modeling to produce ADRs and a glossary.
Stress-Test Your Plan Before Building
Unresolved decisions can make a plan expensive to change during implementation. This skill interviews you systematically and recommends an answer for each decision.
Create Agent Skills
Teams need consistent skill files that agents can discover and use correctly. This skill guides authors through structure, descriptions, examples, scripts, and review checks.
Build Focused Logic and UI Prototypes
Design decisions are difficult to evaluate before users can interact with them. This skill builds disposable prototypes that expose state behavior or compare interface variants.
Pressure-test plans with grilling interviews
Plans and designs often fail because weak assumptions are found too late. This skill starts a focused grilling session that challenges gaps before execution begins.
Create and Update Linear Issues
by Bind
Manual issue entry slows project workflows and introduces inconsistent fields. This skill creates and updates Linear issues through documented command-line options.
Read Linear Issues from the Command Line
by Bind
Finding relevant Linear issues manually can slow project reviews. This skill provides read-only commands for filtered lists and individual issue details.
Manage Jira Workflows from the CLI
by Code-and-Sorts
Teams lose time switching between Jira screens and development tools. This skill guides Claude, Codex, and Claude Code through jira-cli commands for common issue, sprint, and epic work.
Manage IdeaVim YouTrack Issues
by JetBrains
Teams working on IdeaVim need consistent YouTrack workflows instead of GitHub Issues. This skill gives agents the ticket conventions, commands, tags, and release steps for VIM issues.
Automate Linear Workflows Through Rube MCP
by sickn33
Teams lose time on repetitive Linear issue, project, and cycle tasks. This skill guides Claude, Codex, and Claude Code through Rube MCP Linear workflows.
Manage Jira Workflows with Approval Gates
by 01000001-01001110
Jira updates often drift from development work and require manual follow-up. This skill helps Claude, Codex, or Claude Code propose stories, request approval, create issues, and sync workflow status.