Run a mission from Linear

Turn a ticket into bounded work, keep scope honest, and return proof to the issue.

Last updated August 2026Copy a starter prompt ↓

Start from the issue, not a pasted summary

A Linear mission keeps the ticket, repository evidence, and implementation handoff connected. Brief should read the issue and its current discussion, then verify assumptions against the code before planning work.

Ask your coding agent

Use Brief to start a mission from <Linear issue URL or ID>. Read the issue, acceptance criteria, relevant comments, links, and current status. Then map the repo context, applicable team rules, closest reusable implementation, owners, and focused tests. Tell me what the ticket gets right, what is ambiguous or stale, and the smallest safe mission. Don't edit or update Linear yet.

Make the contract explicit

Ask your coding agent

Turn the Linear issue and repo evidence into a bounded Brief mission. Preserve the user outcome, define in-scope and out-of-scope work, list acceptance checks, approvals, dependencies, and stop conditions, and identify any ticket wording that should change. Show me the mission and proposed ticket update before writing anything back.

Run the mission without narrating every step

Ask your coding agent

Run the approved mission. Keep Linear quiet while the work is in progress unless scope, ownership, or a blocker materially changes. Reuse the mapped patterns, run the required verification, review the diff, and stop before any action that needs new authority.

Write back proof, not activity

Ask your coding agent

Prepare the Linear handoff. Summarize the user-visible outcome, changed behavior and files, validation that actually ran, review result, remaining risk, screenshots or runtime proof, and any follow-up work. Update acceptance criteria honestly and propose the correct issue status. Show me the exact comment and field changes before posting them.

Do not mark the issue done when required proof or approval is missing.
Create follow-up issues only for real, bounded work—not every observation.
Keep secrets, raw customer data, and private source out of ticket comments.
Link durable evidence instead of pasting long agent transcripts.

Was this guide useful?Help us make Brief easier to learn.

Ready for another workflow?Choose your next mission →