AICHE +Linear Integration

The short answer: open Linear, create a new issue, click into the description field, press ⌃+⌥+R (Mac) or Ctrl+Alt+R (Windows/Linux), speak your complete requirement for 45-60 seconds, and AICHE inserts the formatted description with full context.

Linear is built for speed. Keyboard shortcuts for everything: C for new issue, L for label, S for status. The entire interface is designed so engineers never touch the mouse. But there's one part of the workflow where speed falls apart: writing the issue description. You can create an issue in two keystrokes, then spend 8 minutes typing the description. That friction means most Linear issues ship with thin descriptions, and the clarification happens in comments over the next three days. Voice input matches Linear's velocity philosophy. You create an issue at keyboard speed, then fill in the description at speaking speed.

1. Open Linear in your browser or desktop app.
2. Press C to create a new issue, or click into an existing issue's description.
3. Type a short title, then Tab or click into the description field.
4. Press your AICHE hotkey (⌃+⌥+R on Mac, Ctrl+Alt+R on Windows/Linux) to start recording.
5. Speak the full requirement. Include what needs to happen, why it matters, who's affected, and what the acceptance criteria are.
6. Press the hotkey again. AICHE transcribes your speech, applies Content Organization formatting if enabled, and inserts the structured text.
7. Use Linear's keyboard shortcuts to set priority (1-4), add labels (L), assign the issue, and link to a project or cycle.

Issue Creation with Full Technical Context

Engineers know more context than they write down. When you're debugging a payment failure and realize it needs a fix, you understand the call chain, the edge case that triggered it, the related code paths, and the potential ripple effects. By the time you open Linear and start typing, you've already simplified the problem to "payment webhook fails intermittently." Voice captures the full picture. Press your hotkey and speak everything: "The payment webhook handler in the billing service drops events when Stripe sends duplicate webhook IDs within the same second. This happens because our idempotency check uses a timestamp-based key with one-second resolution. The fix needs to use the Stripe event ID as the idempotency key instead. This affects roughly 0.3% of transactions based on the last week's logs. Related code is in billing-service/handlers/webhook.ts. The acceptance criteria are zero duplicate event processing, no dropped legitimate events, and the fix should be backward compatible with events already in the queue." That's 30 seconds of speaking. Typing that takes 6-8 minutes.

Cycle Planning and Triage

During cycle planning, you're reviewing a backlog of issues and deciding what goes into the next cycle. Each issue might need scope adjustments, priority changes, or additional context. Moving through the triage queue with just keyboard shortcuts and voice is fast: press J/K to navigate between issues, click into the description to add context, press your hotkey, and speak the scoping note. "Reducing scope on this one. We'll implement the basic retry logic first without the exponential backoff. That covers 90% of the failure cases. Backoff can be a follow-up issue." Then move to the next issue. You can process 20 issues in the time it would take to type detailed notes on 5.

Project Specs and Roadmap Descriptions

Linear projects and roadmap items need longer-form descriptions that explain the "why" behind a body of work. These sit empty on most teams because writing a project spec feels like a chore. With voice, a project description takes two minutes. Press your hotkey and speak through the problem you're solving, the approach you're taking, the milestones you expect, and the success metrics you'll track. AICHE's Content Organization feature structures your spoken explanation into sections. The project page goes from empty to useful, and new team members joining the project mid-cycle can read the spec instead of asking for a verbal walkthrough.

Heads-up: Linear renders markdown in descriptions. AICHE inserts plain text by default. If you want formatted output, enable Content Organization in AICHE settings, which structures your dictation with clear sections. You can also add markdown syntax manually after dictation.

Pro tip: include the "why" when dictating issues. Saying "this prevents users from losing checkout progress when webhooks fail" gives engineers context that a title like "add retry logic" never will. Engineers who understand the user impact write better solutions.

Result: comprehensive issue descriptions that took 8 minutes to type now take 60 seconds to speak, and developers implement tickets correctly on the first try because the context was captured, not summarized away.

Do this now: open Linear, press C to create an issue, type a title, press your hotkey, and dictate one feature request you've been postponing because writing a proper description felt like too much work.