Linear Create

If ambiguous, ask one question to clarify before proceeding.

Pre-Work Draft Mode

1. Ask the user to describe what needs to be done if they haven't already
2. Infer: title (concise, imperative), description (what + why + context), labels if obvious
3. Ask only for what cannot be inferred — do not run through a form
4. Show a preview of the ticket draft (title, description, assignee = me, team, labels)
5. Confirm, then create via Linear-save_issue
6. Share the ticket ID and URL

Retroactive Draft Mode

Work already exists — inspect git context to infer the ticket:

1. Run git --no-pager log --oneline -20 and git --no-pager diff main...HEAD --stat (or origin/main if main is remote) to understand what changed
2. Check the current branch name for clues (issue numbers, descriptive slugs)
3. If a PR exists, use its title/body as additional input
4. Infer: what was changed, why it was needed, what problem it solves
5. Draft the ticket: title, description (including what was done and why), acceptance criteria if determinable, labels
6. Ask targeted questions only for gaps git context cannot fill (motivation, business context, acceptance criteria)
7. Show a preview and confirm before creating
8. After creating, offer to add the branch/PR as a link on the ticket

Ticket State Guidance

When creating a ticket, choose the initial state based on the following logic. Always confirm the state as part of the preview — do not silently apply a state.

References

• Use notion-context skill when a ticket links to or references a Notion document that provides spec or context needed for the work