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 all context.

Creating detailed issue descriptions with acceptance criteria takes 6-10 minutes per ticket, slowing sprint planning. Teams rush through ticket creation, then spend hours in clarification comments because critical context was omitted.

1. Open Linear in your browser or desktop app.
2. Click "New Issue" or press C to create a ticket.
3. Add the title, then click into the description field.
4. Press your AICHE hotkey to start recording.
5. Speak your complete requirement (example: "Add retry logic to the payment webhook handler with exponential backoff starting at 1 second up to 30 seconds maximum, cap at 5 retry attempts, log all failures to Sentry with full request context, send Slack alerts to the payments channel after 3 consecutive failures, and add a dashboard widget showing retry success rates over the last 24 hours").
6. Press the hotkey again-AICHE transcribes, applies Content Organization formatting to structure acceptance criteria, and inserts the text.

Heads-up: when dictating acceptance criteria, pause naturally between points. AICHE's Content Organization feature will automatically structure your stream-of-consciousness into clear sections and bullet points that Linear renders properly.

The pro-tip: include the "why" in your dictation by mentioning the user impact or business context. Saying "this prevents users from losing checkout progress when webhooks fail" gives engineers context that typing "add retry logic" misses completely.

Result: comprehensive issue descriptions that took 8 minutes to type with proper acceptance criteria now take 60 seconds to speak, and developers implement tickets correctly on the first try because all context was captured.

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