linear-method

name

linear-method

description

This skill should be used when the user asks about "Linear method", "Linear issue", "milestone sizing", "triage", "Linear project", "acceptance criteria", "issue scope", or needs guidance on shaping high-quality Linear work (issues, milestones, projects) as clear, right-sized units of value and behavior. Covers planning, writing, and reviewing Linear items around scope, sizing, triage, acceptance criteria, and human-first clarity. Includes references and templates.

For humans: This skill teaches your agent how to decompose work into well-shaped issues and milestones. Read references/issue-quality.md for the deepest treatment of what makes a good issue. See the glossary for unfamiliar terms.

Linear Method (Skill Entry Point)

When to use this skill

• Creating or refining Linear issues, milestones, or projects.
• Splitting, sizing, or re-scoping work.
• Triaging new work or deciding whether an item should be an issue, milestone, or project.
• Checking issue quality before handoff or execution.

How to use this skill

1. Identify the artifact type (issue, milestone, project, triage decision).
2. Load the relevant reference doc from references/.
3. Use the matching template or checklist from assets/ as a starting point.
4. Apply the local conventions (section order, naming rules, sizing) before adding any extra detail.
5. Write for a human implementer: clear outcome, boundaries, and verification.

Reference map

• Issues: references/issues.md
• Issue quality (deep treatment): references/issue-quality.md
• Sizing and estimates: references/sizing-and-estimation.md
• Triage and intake: references/triage.md
• Milestones: references/milestones.md
• Projects and PRDs: references/projects.md

Assets map

• Issue template: assets/issue-template.md
• Issue description checklist: assets/issue-description-checklist.md
• Milestone template: assets/milestone-template.md
• Project template: assets/project-template.md

Core invariants (keep this short)

• An issue is a unit of value and a unit of behavior.
• Issues describe concrete tasks in plain language; avoid user-story framing.
• Outcomes and acceptance criteria matter more than activity logs.
• Status and progress live in Linear fields and comments, not in the description body.
• Good scope keeps the system stable and lets the next person ship safely.