sweep-tickets
SolidRecover or start one unattended Ticket from a configured shared Ticket Store, then stop. Use from a scheduled agent trigger to resume one interrupted automation-owned Auto Ticket or select one ready Auto Ticket and invoke run-ticket. This is the low-frequency correctness path beside issue-event triggers, not a backlog batch runner.
Install
Quality Score: 87/100
Skill Content
Details
- Author
- doodledood
- Repository
- doodledood/manifest-dev
- Created
- 7 months ago
- Last Updated
- 3 days ago
- Language
- Python
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
run-ticket
Run one exact Ticket through recovery, autonomous work, and its required landing, then write DONE or ESCALATED evidence back to that same Ticket. Use when a hosted trigger, agent runner, or person supplies a specific issue, tracker item, or file Ticket to work end to end. This skill does not select backlog work or enforce Auto eligibility at dispatch.
to-tickets
Break an approved plan, specification, or settled conversation into independently verifiable vertical-slice tasks with acceptance criteria and blocking dependencies. Use when the user asks for tickets, issues, a backlog, or work units for multiple sessions or agents. Do not use before requirements are settled, for simple single-session work, or to publish externally without authorization.
factory-sweep
Find Linear tickets that have gone obsolete (duplicate, already shipped, overtaken by events) and retire them with evidence