Issue trackers
Spectr drafts the stories. Shortcut is where the approved ones go. Connect a Shortcut workspace with an API token, optionally set a default team, and each approved story arrives with its description, acceptance criteria, estimate, tags and assignee already set. A status refresh reads each story's state back, so your delivery and budget numbers reflect what is really done.
How Shortcut fits in
A call is imported from a note-taker (Fathom, Granola, Read.ai, or Fireflies.ai). Spectr picks out a requirement, a bug, an action item and an out-of-scope ask, and drafts a story and a bug with acceptance criteria. A person approves both, they are published to Shortcut, and the requirements, scope log and project memory update from the same call.
API token. You create a token in Shortcut and paste it into the project, then optionally set a default team and the workflow state new stories start in.
A Shortcut workspace, and an API token from an account that can create stories in the team you choose.
In Shortcut, create an API token from your account settings.
In Spectr, open the project, go to Integrations, choose Shortcut and paste the token.
Select the team new stories should be created in, and the workflow state they should start in.
Generate stories from a meeting and review them.
Publish the approved stories. Each story in Spectr links to the Shortcut story it became.
Anything else? Email hello@crowdlinker.com and a person will answer.
Spectr connects with a Shortcut API token rather than OAuth. The token is encrypted at rest and can be revoked from Shortcut at any time.
Spectr publishes stories, and nests them under a parent story when the spec marks a task as a parent. It does not create epics.
Members of your Shortcut workspace, which Spectr syncs into the project team, so an assignee picked in review is a real Shortcut user.
Use case
Draft stories with real acceptance criteria, then approve, edit or reject each one
Publish stories as Linear issues and keep their status and labels in sync
Publish stories as Jira issues, with sub-task nesting, and read their status back
Import a Fathom call and get structured specs and stories from its notes, action items, and transcript
Connect Read.ai over OAuth and mix its meetings freely with Fathom and Granola in one project
Granola
Fireflies.ai