Run any Skill in Manus with one click

linear-agent-workflow

Stars0

Forks0

UpdatedJune 14, 2026 at 14:39

Use when coding from Linear issues, syncing task status, creating implementation plans, posting progress comments, or linking GitHub PRs.

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.

Run Skill in Manus

Source

Parsa-29

Parsa-29/loop-config

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	linear-agent-workflow
description	Use when coding from Linear issues, syncing task status, creating implementation plans, posting progress comments, or linking GitHub PRs.

Linear Agent Workflow

Use Linear as the task context and status surface for coding work.

When to Use

Use this skill when the user:

Provides a Linear issue ID or project name.
Asks what to work on next.
Asks to sync task status, post progress, or link a GitHub PR.
Mentions Linear-backed coding, agent task management, worktrees, branches, forks, or PR handoff.

Workflow

Fetch Linear context first.
- Read the issue or project before inspecting code when the task starts from Linear.
- Treat title, description, comments, labels, status, linked PRs, assignee, priority, cycle, and project as task context.
Plan before non-trivial work.
- For multi-file, risky, or ambiguous changes, post a short implementation plan as a Linear comment.
- Include intended files/modules, verification commands, risks, and blockers.
Keep status aligned.
- Move to In Progress when implementation starts.
- Move to In Review when a PR exists or the diff is review-ready.
- Move to Blocked when credentials, approvals, CI, environment, or product decisions are missing.
Report completion in Linear.
- Comment with summary, changed files, verification output, unresolved risks, and PR link if available.
- Do not mark complete unless the requested done condition is satisfied.

Guardrails

Do not create or update Linear issues unless the user asked or provided an issue ID.
Do not invent issue IDs, team names, labels, projects, statuses, or PR URLs.
Read before write: list/fetch Linear entities before mutating them.
If Linear tools are unavailable or auth fails, tell the user exactly what failed and continue with local work only if the task has enough context.
Git push, deploys, DB writes/migrations, dependency additions, secret edits, and live external mutations still require human approval.

Suggested Linear Comment Shapes

Plan comment:

Plan:
- Scope: ...
- Files/modules: ...
- Verification: ...
- Risks/blockers: ...

Completion comment:

Done:
- Summary: ...
- Changed files: ...
- Verification: ...
- PR: ...
- Remaining risks: ...

More from this repository

same repository

plantask

Parsa-29/loop-config

Plan a feature or bug fix and break it into well-formed, non-mixing Linear tasks — one parent issue per feature with ordered, dependency-linked sub-issues, each with a detailed plan, acceptance criteria, labels, and a branch name — ready for a coding agent to execute. Use when the user runs /plantask, or asks to plan and create Linear issues/tasks for a feature, bug, or piece of work.

2026-06-180

shopify-app-store-review

Parsa-29/loop-config

Run a pre-submission compliance check against your Shopify app's codebase. Reviews App Store requirements and surfaces likely issues before you submit for official review.

2026-06-140

cartesia-api

Parsa-29/loop-config

Integrate Cartesia speech APIs (TTS, STT, voices) in application code or coding-agent workflows. Use when the user asks about Cartesia REST/WebSocket APIs, SDKs, API keys, Sonic TTS, Ink STT, voice IDs, access tokens, or embedding voice in an app. For Cartesia Line deployed agents, CLI deploy, and telephony, use the line-voice-agent skill instead.

2026-06-140

flitt-payments

Parsa-29/loop-config

Flitt payment API implementation guidance for auth, SHA1 request/callback signatures, sandbox testing, hosted checkout, Payment (redirect), Payment (direct), saved-card /api/recurring charges, card token saving, scheduled subscriptions, reversals/refunds, captures for preauth payments, reservation_data payloads, supported currencies, callback/webhook handling, response codes, 3DS steps, order status polling, and response handling. Use when Codex needs to integrate or debug Flitt payments, create payment requests, build or verify signatures, attach reservation_data, validate currency support, implement callback handlers, interpret response codes, obtain or charge a rectoken, create/cancel subscriptions, reverse/refund through /api/reverse/order_id, capture through /api/capture/order_id, poll status, or troubleshoot Flitt API failures.

2026-06-140

line-voice-agent

Parsa-29/loop-config

Build voice agents with the Cartesia Line SDK. Supports 100+ LLM providers via LiteLLM with tool calling, multi-agent handoffs, and real-time interruption handling.

2026-06-140

Linear Agent Workflow

Use Linear as the task context and status surface for coding work.

When to Use

Use this skill when the user:

Provides a Linear issue ID or project name.

Asks what to work on next.

Asks to sync task status, post progress, or link a GitHub PR.

Mentions Linear-backed coding, agent task management, worktrees, branches, forks, or PR handoff.

Workflow

Fetch Linear context first.

Read the issue or project before inspecting code when the task starts from Linear.
Treat title, description, comments, labels, status, linked PRs, assignee, priority, cycle, and project as task context.

Plan before non-trivial work.

For multi-file, risky, or ambiguous changes, post a short implementation plan as a Linear comment.
Include intended files/modules, verification commands, risks, and blockers.

Keep status aligned.

Move to In Progress when implementation starts.
Move to In Review when a PR exists or the diff is review-ready.
Move to Blocked when credentials, approvals, CI, environment, or product decisions are missing.

Report completion in Linear.

Comment with summary, changed files, verification output, unresolved risks, and PR link if available.
Do not mark complete unless the requested done condition is satisfied.

Guardrails

Do not create or update Linear issues unless the user asked or provided an issue ID.

Do not invent issue IDs, team names, labels, projects, statuses, or PR URLs.

Read before write: list/fetch Linear entities before mutating them.

If Linear tools are unavailable or auth fails, tell the user exactly what failed and continue with local work only if the task has enough context.

Git push, deploys, DB writes/migrations, dependency additions, secret edits, and live external mutations still require human approval.

Suggested Linear Comment Shapes

Plan comment:

Plan: - Scope: ... - Files/modules: ... - Verification: ... - Risks/blockers: ...

Completion comment:

Done: - Summary: ... - Changed files: ... - Verification: ... - PR: ... - Remaining risks: ...