skills.rest
kwam1na
kwam1naCOMMUNITY
Explore all skills by this author →
GitHub

execute-linear-ticket

Execute existing Linear tickets from implementation through merge and closure.

Updated Sep 25, 2024
Search Tags:#workflow#linear#end-to-end#test-driven#pr-management#ticket-execution#ticket-closure
One-click install
npx skills add https://github.com/kwam1na/athena --skill execute-linear-ticket
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: execute-linear-ticket
Source: https://github.com/kwam1na/athena/tree/main/.agents/skills/execute-linear-ticket
Command: npx skills add https://github.com/kwam1na/athena --skill execute-linear-ticket

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Use when work already exists in Linear and the user wants implementation rather than new planning.

Core Features & Use Cases

  • End-to-end ticket execution: implementation through to merge and Linear closure
  • Delivery posture: apply $compound-delivery-kernel throughout execution. Linear owns the work record, the repo owns sensors, and the skills system owns the delivery workflow. Preserve test-driven delivery: behavior changes start with a failing test or characterization capture, not implementation.
  • Shared context and governance: use references/linear-project-resolution.md before mutating Linear or choosing the next ticket from a backlog.
  • Defaults and workflow: start from the latest origin/main in a fresh worktree; manage patch-level validations, guardrails, and PR hygiene.

Quick Start

Direct the agent to execute an existing Linear ticket end-to-end, from implementation through verification, review, and closure.

Frequently Asked Questions about execute-linear-ticket

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

FAQPage Schema
How do I automate Linear ticket execution end-to-end from implementation to merge?▼

Use an agent-driven delivery workflow that starts from the latest origin/main, applies test-driven or characterization-first practices, validates repo sensors, and links PRs for successful Linear ticket closure.

How does test-driven delivery work when closing existing Linear issues?▼

Test-driven delivery for Linear issues requires behavior changes to start with a failing test or characterization capture rather than implementation. The repo owns sensors while the workflow manages guardrails and PR hygiene throughout execution.

Can I batch handle multiple Linear tickets for end-to-end delivery?▼

Batch-handling is supported for Linear ticket execution, allowing the delivery workflow to process multiple issues while preserving test-driven delivery postures and repo-sensor validations to ensure successful closure.

What is the best way to manage PR linking and status updates for Linear tickets?▼

Manage PR linking and status updates by using a delivery workflow that automates Linear state transitions and PR referencing. This maintains shared context governance and validates repo sensors before mutating Linear records.

Do I need a fresh worktree to execute Linear tickets through to closure?▼

Executing Linear tickets defaults to starting from the latest origin/main in a fresh worktree. This ensures clean patch-level validations and proper PR hygiene before completing end-to-end delivery and closure.

Related Skills

Explore More Software Engineering Skills→
f4irlinef4irline
5

git-branch-create

Generate convention-compliant git branch names from Linear ticket IDs.

Community
Intermediate
kvnxiaokvnxiao

linear-fix

Create per-ticket git worktrees and generate GitHub PRs for Linear tickets.

Community
Advanced
erenisiklarerenisiklar

test-driven-development

Enforce a test-driven development workflow with the RED-GREEN-REFACTOR cycle.

Community
Advanced
find-xposed-magiskfind-xposed-magisk
30

linear

Manage Linear issues by retrieving, updating, and commenting on them.

Community
Intermediate