Context & docs
The quickest way to write a useless ticket is to describe something that already exists, or to name a module that does not. Connect GitHub, pin up to five repos, and Spectr reads the relevant code before drafting - so a story names your actual services and endpoints, and the estimate reflects what the change would really touch.
How GitHub 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, reads GitHub, Notion, and Figma for context, and drafts a story and a bug with acceptance criteria. A person approves both, they are published to the team's tracker (Jira, Linear, or Shortcut), and the requirements, scope log and project memory update from the same call.
OAuth App with the repo and read:org scopes. Spectr only uses them to read code and issues; it never pushes, opens pull requests, or comments.
A GitHub account that can see the repositories you want read, private ones included. Up to five repositories can be pinned per project.
In Spectr, open the project and go to Integrations.
Choose GitHub and click Connect, then authorise the OAuth app.
Select up to five repositories to pin as project context.
On your next spec sheet, open Context Gathered to see exactly which source files were read.
Anything else? Email hello@crowdlinker.com and a person will answer.
No. GitHub is read-only context. Spectr reads code and issues to write better specs.
Yes, for repositories the authorising GitHub account can already access.
Standard GitHub OAuth tokens do not expire. They can be revoked - including automatically by GitHub if a token is ever exposed in a public repo - and if that happens, reconnect GitHub in the project's Integrations tab.
Use case
Draft stories with real acceptance criteria, then approve, edit or reject each one
Fathom
Granola
Read.ai
Fireflies.ai
Webhooks RFC
Delivery settings
Jira
Linear
Shortcut