start_skill

Overview

This skill automates starting work on a Linear issue from blocker checks to branch creation and incremental implementation. It guides assignment, moves the issue to In Progress, creates or switches to a git branch, produces a proposed implementation plan, and enforces checkpoint updates in Linear as work completes.

How this skill works

The skill inspects the issue description, checkboxes, parent issue, comments, and attachments using the linear CLI and authenticated downloads for images. It searches for blockers, updates assignee and state, checks for or creates a git branch following naming rules, enters a plan mode to propose steps, and then runs the approved implementation workflow while updating checkboxes and posting checkpoint comments.

When to use it

• You say 'start issue', 'work on PL-XX', 'begin PL-XX', or invoke /start.
• You want to confirm blockers and ownership before coding.
• You need a consistent branch name and to avoid duplicate branches.
• You want a clear implementation plan before writing code.
• You need to make progress visible in Linear with checkbox updates and comments.

Best practices

• Always review requirement and success-criteria checkboxes and parent issue context before planning.
• Do not ignore unresolved blockers — list them and ask user direction.
• Create branch names with the required prefix and kebab-case issue title, or switch if one exists.
• Present a step-by-step implementation plan and wait for user approval before implementing.
• After each logical change, verify tests/type checks and update the issue description by checking only the completed checkboxes.
• Post brief checkpoint comments for significant decisions or unexpected blockers to keep progress discoverable.

Example use cases

• Start work on PL-13: check blockers, assign to me, move to In Progress, and create kevinross/pl-13-short-title branch.
• Resume a paused issue: locate existing branch, switch to it, review prior comments and continue with next checkbox.
• Handle a blocked issue: list blocking issues and ask whether to proceed or resolve blockers first.
• Implement a multi-step feature: produce an implementation plan from checkboxes and parent epic, get approval, then execute with checkpoint updates.