linear-fix-issue

Triaging Linear bugs into subtasks requires converting parent issues into actionable items with clear titles, reproduction steps, and severity. This Skill automates that process by linking subtasks to parent issues and generating a prioritized implementation plan with acceptance criteria and dependency mapping.

To connect Linear issues to automated bug triage, you need a connected Linear MCP, a feature-branch workflow, and CLI access. These prerequisites allow the system to create subtasks, link parent issues, and generate a structured implementation plan automatically.

Yes, this issue triage workflow targets Linear-based environments where bugs originate from e2e tests, user reports, or code reviews. It systematically converts these reported issues into structured subtasks and coordinates an end-to-end fix workflow including verification and documentation.

The best way to create an implementation plan from a Linear issue is to parse the bug details and map out dependencies alongside acceptance criteria. This Skill automates that conversion, building a prioritized execution plan while notifying stakeholders of the coordinated fix workflow.

Yes, the bug triage process handles stakeholder notification and issue linkage by guiding the team through an end-to-end fix workflow. It uses CLI access and a Linear MCP to link parent issues with created subtasks and notify relevant stakeholders throughout the implementation plan.