ticket-creator
Ticket Creator
Create well-structured Linear tickets optimized for AI agent (Claude Code) implementation. Follow a pattern-first, template-driven workflow that ensures the implementing agent can plan and execute without making open-ended architectural decisions. Consult references/guidelines.md for detailed quality criteria and writing guidelines.
Core Principle: Pattern-First
The strongest predictor of ticket success is whether the implementing agent can copy-and-adapt from an existing pattern. Every ticket MUST reference an existing code pattern or explicitly flag it as a first-time pattern requiring extra specification.
AskUserQuestion Usage
Only invoke AskUserQuestion when the answer cannot be deduced from the current conversation context, the codebase, or prior responses. If the information is available or can be inferred, proceed without asking. This applies to all stages — classification, deduplication, information gathering, anti-pattern resolution, splitting, and confirmation.
Workflow
Use TaskCreate at the start to plan the workflow steps, and TaskUpdate to mark each step as you complete it. This keeps progress visible and survives /compact.
1. Gather Context & Classify
Extract as much information as possible from the current conversation before asking any questions. If work has been discussed, use that context to pre-fill ticket details.
More from sylla-bv/sylla-skills
pr-sweep
>-
7coding-standards
>-
6verify
>-
3brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
2playwright-cli
Automate browser interactions, test web pages and work with Playwright tests.
1code-upkeep
>-
1