speclet-ticket

Split a draft into numbered ticket folders with JSON metadata and an index file.

Updated Jan 9, 2026
One-click install
npx skills add https://github.com/danielcastro-dev/speclet --skill speclet-ticket
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speclet-ticket
Source: https://github.com/danielcastro-dev/speclet/tree/main/.opencode/skill/speclet-ticket
Command: npx skills add https://github.com/danielcastro-dev/speclet --skill speclet-ticket

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Convert a large draft into discrete, trackable tickets to enable focused, session-based work.

Core Features & Use Cases

  • Read .speclet/draft.md and identify discrete work items
  • Create ticket folders at .speclet/tickets/TICKET-N/
  • Generate ticket metadata at .speclet/tickets/TICKET-N/ticket.json
  • Copy general draft to .speclet/tickets/TICKET-N/ticket-draft.md
  • Create/update .speclet/tickets/index.json for centralized status tracking
  • Delete root draft after ALL tickets are created
  • Enable ticket-by-ticket workflow: one ticket → one session → full speclet cycle

Quick Start

Split your draft into discrete tickets by running the speclet-ticket workflow to create ticket folders and ticket JSON files.

Frequently Asked Questions about speclet-ticket

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I split a large draft into discrete implementation-ready tickets?

Splitting a project draft into trackable tickets enables focused work by isolating each item into its own session, preventing context switching and allowing you to tackle complex drafts one implementation-ready ticket at a time.

How does centralized status tracking work for split draft tickets?

Centralized ticket tracking works by maintaining an index.json file in the .speclet/tickets/ directory, which records a specletVersion and sourceContext pointing to the original draft to monitor all split work items.

What is the best way to manage draft items across multiple work sessions?

Managing draft items across sessions involves splitting the draft into discrete ticket folders, each containing ticket.json and ticket-draft.md files, enabling a strict one ticket per session workflow for focused execution.

When should I use a ticket splitting workflow for project drafts?

Use a ticket splitting workflow when your draft contains multiple independent items and you want to tackle them one at a time across isolated work sessions, generating structured ticket folders for each discrete item.

Does the draft splitting process delete the original draft file?

Yes, the draft splitting process deletes the root .speclet/draft.md file only after ALL tickets are successfully created, ensuring the original draft is safely removed once every discrete work item has its own generated folder.

What files are generated when breaking a draft into trackable tickets?

Breaking a draft into trackable tickets generates ticket folders at .speclet/tickets/TICKET-N/, each containing a ticket.json metadata file and a ticket-draft.md copy, plus a central index.json for tracking.