stevesolun/ctx / .agents/skills/to-tickets
to-tickets
VerifiedBreak a plan, spec, or conversation into dependency-aware, independently verifiable tickets. Use explicitly when the user wants work sliced for local planning or an issue tracker.
Create tickets
Read the source plan, spec, issue, or conversation and inspect enough of the repository to avoid fictional boundaries. Use the project's established domain language and preserve relevant architectural decisions.
Prefer narrow vertical slices that deliver observable behavior and can be verified independently. Size work for the actual team and risk rather than a fixed context-window rule. Use horizontal or mechanical slices when the change cannot remain coherent vertically.
Model only real blocking edges. Tickets without blockers form the available frontier and may proceed concurrently. For a broad compatibility migration, consider an expand–migrate–contract sequence so intermediate states remain usable.
Each ticket should communicate:
- the behavior or outcome it delivers;
- concrete acceptance criteria;
- genuine dependencies;
- relevant constraints or source references; and
- scope boundaries when adjacent work is easy to confuse.
Use the ticket format when the destination has no stronger convention. Avoid brittle line numbers and implementation recipes unless the ticket is intentionally mechanical.
Present a draft when granularity or dependencies remain uncertain. Publish or write tickets only when requested and authorized, following the configured tracker's native dependency model. Do not alter a parent item or apply workflow labels unless that action is part of the request.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies. | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |
| meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要". | Stars: 108k | Updated | Claude CodeCodex | Verified | Install |