linear-method

Stars10

Forks1

UpdatedMarch 23, 2026 at 09:35

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

rawr-ai

rawr-ai/codex-linear-method-toolkit

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Project Management SpecialistsBusiness and Financial Operations Occupations·SOC 13-1082

File Explorer

11 files

SKILL.md

readonly

name

linear-method

description

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

Identify the artifact type (issue, milestone, project, triage decision).
Load the relevant reference doc from references/.
Use the matching template or checklist from assets/ as a starting point.
Apply the local conventions (section order, naming rules, sizing) before adding any extra detail.
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.

More from this repository

same repository

architecture

rawr-ai/codex-linear-method-toolkit

This skill should be used when the user asks about "target architecture", "greenfield spec", "pure SPEC", "decision packet", "migration slice", "architecture decision", "spike to spec", "current vs target", "hybrid to target", "indirection audit", "dependency ordering", "cutover validation", "no legacy left", "legacy cutover", or needs guidance on defining target architecture, creating specs from exploration, resolving architectural ambiguity, planning migrations from current to target state, or validating cutover plans.

2026-03-2310

autonomous-development

rawr-ai/codex-linear-method-toolkit

This skill should be used when the user asks about "dev-auto", "autonomous development", "orchestrator", "worktree lifecycle", "structured output", or when running dev-auto-* commands or any autonomous loop that relies on orchestrator-owned worktrees, explicit inputs, and structured JSON outputs. Auto-safe development contract for orchestrated dev/review/fix workflows.

2026-03-2310

git-worktrees

rawr-ai/codex-linear-method-toolkit

This skill should be used when the user asks about "git worktree", "parallel checkout", "worktree cleanup", "create worktree", "remove worktree", "worktree path", or when a workflow involves git worktrees, parallel development, multiple checkouts, or edits that must happen in the intended worktree path. Reusable workflow for safely creating, entering, and working within git worktrees (plus clean removal).

2026-03-2310

parallel-development-workflow

rawr-ai/codex-linear-method-toolkit

This skill should be used when the user asks about "parallel development", "multiple agents", "worktree + Graphite", "parallel issues", "agent isolation", or needs to coordinate multiple agents or issues in parallel using git worktrees + Graphite stacks (gt). Each agent isolates work in its own worktree + local stack and avoids global restacks. Canonical, reusable parallel development workflow.

2026-03-2310

name

linear-method

description

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

Identify the artifact type (issue, milestone, project, triage decision).
Load the relevant reference doc from references/.
Use the matching template or checklist from assets/ as a starting point.
Apply the local conventions (section order, naming rules, sizing) before adding any extra detail.
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.