linear

Convert coding session discussions into tracked issues with state transitions.

Updated Apr 17, 2026
One-click install
npx skills add https://github.com/Aradotso/ara.engineer --skill linear-aradotso
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: linear
Source: https://github.com/Aradotso/ara.engineer/tree/main/skills/linear
Command: npx skills add https://github.com/Aradotso/ara.engineer --skill linear-aradotso

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Always active. Any work discussed in a session should be tracked.

Core Features & Use Cases

  • Feature discussed → create issue when planning; assign on start; move through Todo, In Progress, In Review, Done.
  • Use case: during coding sessions, convert ideas into tracked issues and monitor progress.

Quick Start

During a coding session, document a discussed feature as a new issue and assign it to yourself to begin tracking.

Frequently Asked Questions about linear

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I track issues from discussions during coding sessions?

To track issues from coding sessions, document the discussed feature as a new issue, assign an owner, and transition it through Todo, In Progress, In Review, and Done states within the active workflow.

What is the best way to convert feature ideas into tracked issues?

Converting feature ideas into tracked issues requires capturing the discussion as a new issue during planning, assigning an owner when work starts, and moving it through standard Todo, In Progress, In Review, and Done states.

Can I assign owners and track status for issues discussed in real-time?

Yes, you can assign owners and track status in real-time by creating an issue when a feature is discussed, then explicitly transitioning its state through Todo, In Progress, In Review, and Done as work progresses.

Does lightweight issue tracking work without external dependencies?

Yes, lightweight issue tracking works without external dependencies by applying front matter for team and project context and using explicit state transition rules to manage issues directly during coding sessions.

When should I create an issue during a coding session?

Create an issue during a coding session whenever a feature is discussed during planning; assign it to yourself or a teammate to begin tracking, then move it from Todo through In Progress, In Review, and Done.

How does the issue state transition workflow move work forward?

The issue state transition workflow moves work forward by enforcing explicit rules that progress issues from Todo to In Progress, then to In Review, and finally to Done, ensuring all discussed work is actively tracked.