linear-story

To format a user story spec into a Linear issue, provide your structured story spec including acceptance criteria and technical notes. The skill packages this input into a Markdown block matching Linear's issue template with Title, Priority, Labels, and Description sections.

Creating a Linear-ready ticket requires a structured story spec containing your user story, acceptance criteria, technical notes, dependencies, and open questions. The formatter validates these components and surfaces gaps as inferred open questions within the final Markdown output.

Yes, you can use this to generate Linear tickets for product management workflows. It ingests structured story specs and outputs a single Markdown block suitable for pasting directly into Linear, ensuring consistent formatting and faster handoffs.

Yes, the Linear issue formatter includes fields for cycle and priority. The generated Markdown template contains standard Linear fields like Title, Team, Assignee, Priority, Estimate, Cycle/Sprint, Labels, and Status alongside detailed description sections.

If your story spec is missing acceptance criteria or open questions, the formatter validates the input and surfaces those gaps. Missing elements are automatically generated and highlighted as inferred open questions in the final Linear issue template.

To package technical notes and dependencies into a Linear ticket, input your raw structured spec. The formatter maps these details into the Description section and builds a comprehensive Technical Notes and Dependencies block within the Markdown output.