Skip to content
Agentmart
Submit a tool

to-tickets

Turn a plan or specification into verifiable tickets with explicit dependencies.

Skill by jamesdebatty

IndexedMIT
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/jamesdebatty-to-tickets

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Turn a plan or specification into verifiable tickets with explicit dependencies. Publish only within an authorized tracker workflow.

Use cases: productivity

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/to-tickets

What's inside

Skill name
to-tickets
Description
Turn a plan or specification into verifiable tickets with explicit dependencies. Publish only within an authorized tracker workflow.
License
MIT
Metadata
updated: 2026-09-06 · use-case: Turn a plan or specification into verifiable tickets with explicit dependencies. Publish only within an authorized tracker workflow.
Instructions
11 lines in SKILL.md · view on GitHub

Files (4)

  • SKILL.md
  • openai.yaml · agents/
  • delivery.md
  • slicing.md

SKILL.md (first lines)

# Plan tickets

Use the supplied plan, specification, or conversation. Inspect relevant code only to resolve gaps affecting the breakdown. Each ticket should deliver verifiable behavior and state its acceptance criteria and true blockers.

Read [slicing.md](slicing.md) for vertical-slice and wide-refactor guidance. Choose the smallest useful dependency graph; do not create tickets merely to mirror implementation layers.

Present titles, delivered behavior, and blocking edges. Reuse supplied scope and granularity decisions; ask only when an unresolved choice materially changes the plan. Honor a requested review checkpoint without imposing one on already authorized work.

Complete local ticket preparation by default. Read [delivery.md](delivery.md) for one-file-per-ticket local output or an explicitly authorized tracker workflow. Use existing tracker configuration; missing remote setup does not block local drafting. Preserve the parent issue and unrelated tickets.

From jamesdebatty/skills, MIT.

More from jamesdebatty/skills

Signals

Stars
0
Forks
0
Open issues
0
Last commit (this folder)
Sep 8, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
Repository
github.com/jamesdebatty/skills
First seen
Oct 24, 2026
Last checked
Oct 24, 2026
Source
GitHubgithub-graphql

More from jamesdebatty

Cite this page

to-tickets skill. Agent Mart. https://agentmart.dev/skills/jamesdebatty-to-tickets (last updated 2026-10-24)