What's new in Spectr

The workspace dashboard has a new Action Items section that gathers every action item across your projects in one place. Mark them complete, reopen, or dismiss right there - no need to open each spec sheet - and filter down to just the ones assigned to you. Sections collapse to keep your dashboard focused on what matters.

When you or a teammate completes, reopens, or dismisses an action item, the change now appears instantly everywhere it shows - the dashboard and the spec sheet it lives on - with no refresh.

Stories, Spec Sheets, Requirements, Meetings, the Scope Creep tracker and more now remember your sort order per workspace - and on the Stories page, whether you prefer the list or board view. Set it once and it's there every time you come back, on any device.

Stories now arrive in JIRA with their formatting intact - headings, lists, and code blocks render properly instead of showing raw markup. And if your JIRA project isn't set up for story points, Spectr now tells you up front so your estimates don't silently drop.

Spectr now connects to JIRA Cloud. Pick your JIRA site, project, issue type, and the status new issues land in, then publish approved stories straight to JIRA - the same review-and-publish flow you already use for Linear and Shortcut. Assignees carry across, and once a story is live Spectr keeps its status and completion in sync, feeding your budget projection just like the other trackers.

Action items on a spec sheet can now be marked complete when they're done, or archived when they're no longer relevant - so the list reflects what's actually left to do instead of only ever growing.

When you import a meeting from Fathom (and other sources), Spectr now pulls in your meeting tool's own AI summary and action items alongside the transcript - so it starts with more context and captures the follow-ups your team already flagged.

Open a story and you now see who else has it open right now, so two people don't unknowingly work on the same story at once. Live updates also reach beyond the board - a story changed from a spec sheet, the Scope Creep tracker, or any other view now stays current wherever it appears, without a refresh.

A story's status now shows the same colored indicator everywhere it appears - the Stories list, linked stories, and the status filter - so its state reads the same at a glance across the app. We also corrected the spec sheet icon to match the rest of Spectr and tidied the Stories list layout.

The Stories board and list now update live for everyone viewing them. When you or a teammate creates, moves, edits, or publishes a story, the change appears immediately - no refresh, no polling. Per-lane counts and story-point totals stay accurate as changes land, no matter how many stories each column has loaded.

A story now links back to where it came from. Open a story to jump straight to its originating spec sheet task, and when a story is out of scope, jump to the linked item on the Scope Creep tracker - with a new "Confirm out of scope" action available right from the story.

Meetings, Requirements, Spec Sheets, the Scope Creep tracker, and the Stories list all get a search box and consistent pagination. Meetings now sort by date and show how many spec sheets and requirements each one produced, spec sheets show task and story counts, and the Scope Creep tracker can filter by whether an item has stories.

Stories now filter and display by their spec sheet - the one parent every story shares - instead of by meeting. Stories created from briefs and requirements, which have no meeting, now show up and filter correctly.

When you create a spec sheet from a Brief without naming it, Spectr now generates a concise, meaningful title from the brief's content instead of just using its first line.

The billing page now lets you filter activity by period, with clearer card labels and a fixed empty state.

You can now attach files directly to a message in the AI Assistant - PDFs, images, and text or markdown files. Ask about a document, a screenshot, or a spec without pasting it in, and the assistant reads it as part of the conversation.

Finding the right stories is much faster. A new quick search jumps to any story by title or description, every filter (status, type, scope, meeting, spec sheet, task, assignee) now lives in one unified menu, and you can select multiple values within a filter at once instead of one at a time.

The Stories page now remembers your last-used filters, so you pick up right where you left off instead of re-applying status, type, scope, and assignee every time you come back.

Auto-filling project team members' roles from Project Memory had quietly stopped working after an AI SDK upgrade. It's fixed - AI-fill roles reliably assigns roles across your team again.

The in-app onboarding tour now walks through more of Spectr so new workspaces get oriented faster, and requirement documents show an avatar for who authored each version - so you can see at a glance who wrote what.

A few sharp edges smoothed out: opening a requirement no longer risks overwriting your draft with a stale autosave, a spec sheet generated from a single task no longer borrows that task's title, and monthly usage now resets cleanly at the start of each billing cycle.

The workspace dashboard now opens with summary cards built for project managers: counts and recent activity across your projects, meetings, spec sheets, and stories, so you get the state of the whole workspace without opening each project one by one.

Spectr now has a built-in AI Assistant - ask it anything in plain language and it answers from everything in your workspace. Ask "What has Priya been working on?" or "Are we on track for budget?" and it looks across your projects, meetings, spec sheets, requirements, stories, AI Memory, Harvest budget, team roster and Forecast allocation, logged hours, and scope-creep items to give a complete answer - not just the first thing it finds. Scope a conversation to one project or your whole workspace, pick the model that fits (Haiku, Sonnet, or Opus), and watch it think - it shows exactly which items it checked, and which project each lookup ran against, every reference linked so you can jump straight there. Keep a chat private, share it with specific teammates, or open it to your whole workspace - then search your conversations and filter them by who they're shared with. It's read-only today: it answers and links, it doesn't change your data. Available on Starter and up.

The Stories board picks up a search box to find a story by title or description, per-column story-point totals with a completion tooltip, and per-lane "Load more" pagination so each status column loads independently instead of capping the whole board - the board stays fast on large projects.

Resolving possible duplicates is clearer: the actions now have explanatory tooltips and confirming a match reads as "Confirmed as duplicate." We also swapped native browser title hints for proper tooltips across the app and tightened spacing in a few dense views.

Sometimes the work isn't in a meeting or a formal requirement - it's just in your head. Now you can write a quick Brief in markdown and Spectr runs it through the same pipeline to produce a spec sheet and stories, pulling in context from your connected tools just like a meeting would. Start one from "Create Stories" on the Stories page or "New Spec Sheet" on the Spec Sheets page, optionally give it a name, and it lands as its own spec sheet.

The Spec Sheets and Meetings pages now have color-coded source filters (Requirement / Meeting / Brief) so you can see at a glance where each item came from. And if a brief- or requirement-sourced spec sheet fails to generate, a new Retry action re-runs it in place - no need to recreate it. The source Brief also sits at the top of the spec sheet as a collapsible card.

Spectr now scans every newly generated story against the rest of your project for possible duplicates automatically - there's no setting to switch on. When something looks like a repeat it gets a badge, and you can confirm the match to link the stories together (or unlink if it isn't one). Confirmed duplicates stay grouped across the Stories board and spec sheet views, so a reviewer only has to act on one. The story edit modals were also reworked to sit comfortably on smaller screens.

Refreshing a published story used to pull back only its completion status. Now it also syncs the assignees, labels/tags, work type, and priority set in Linear or Shortcut back into Spectr - so changes your team makes in your tracker stay reflected here. Story cards also get a clearer link out to their published issue.

You can now rename projects, meetings, and spec sheets inline, so titles stay tidy as work evolves.

Stories and spec sheet tasks now support multiple assignees, chosen from a team-member selector instead of a free-text name. Pick anyone from the project's synced roster (or type a name), assign several people to one item, and set a default on the parent task that individual stories can override. Assignee chips show on the board, list, and spec sheet views, there's a new team-member filter on the Stories page, and on publish the primary assignee maps to Linear or Shortcut with everyone else carried along. Generated stories are also grounded in each person's role, so work routes to the right owner from the start.

Connecting Google Drive has moved to Google's native file picker. Instead of granting Spectr broad read access to your whole Drive, you pick the exact files and folders you want it to use, and Spectr's access is scoped to just those - more secure, and you stay in control of what's shared. Note: because the underlying permission changed, any existing Google Drive connection has been reset - reconnect it from the project's Integrations settings and pick your files again.

Connect Forecast to bring each project member's scheduled allocation and logged hours into Spectr. It rolls up onto the project's Team and Budget views alongside the roster, so you can see who's allocated to the project and how their logged time compares - adding capacity and budget insight without leaving Spectr.

The badges that flag likely-duplicate and out-of-scope work - previously only on the Stories board - now also appear on spec sheet pages, with clearer matching so you can see exactly which existing story a possible duplicate points to. Spot and resolve repeats and scope creep wherever you review generated work.

Imported meetings now capture and show the actual date the meeting took place, and the meetings list keeps titles and dates in sync as they change. Plus a few visual fixes to the list for a cleaner, more consistent view.

Editing a team member's role now opens ready to type, and saving without changes keeps the existing template or AI assignment intact instead of overwriting it. And when you disconnect an integration, the team members, roles, and budget data it provided are pruned and the views refresh automatically - no stale people or numbers left behind.

Every project now has a Team page. Spectr builds the roster automatically from the tools you've connected - Linear, Shortcut, and Harvest - showing who's on the project, their avatar, and where each person came from, kept in sync with no manual upkeep. On paid plans you can assign each person a delivery role - pick from a built-in template library (design, engineering, product, QA, marketing, management) or write your own - and let AI auto-assign the best-fit role to everyone from your Project Memory. Roles feed story and spec assignees, so generated work routes to the right people.

Regenerating stories from a meeting or requirement used to resurface work you'd already seen - stories that were pending, approved, published, or that a reviewer had explicitly rejected. Now Spectr checks freshly generated stories against what already exists in the project and what's been turned down, and skips the repeats - so a reviewer's rejection finally sticks instead of coming back next run. Two per-project toggles (avoid duplicates, avoid rejected) are on by default and overridable per generation, and anything Spectr flags as a possible duplicate gets a badge on the Stories board so you can decide.

Pin where approved stories should go. Choose a default Linear project and workflow state, or a Shortcut team and state, per project - so publishing routes every story to the right destination without picking it each time.

A new per-project setting controls how Spectr groups generated work into parent stories and sub-tasks - from off (flat) through default, high, or always - and lets you name the parent and sub-task labels used on publish. The default preserves today's behavior, so nothing changes unless you opt in.

Spectr now tracks whether the stories you've published actually got done. It checks each published story's state in Shortcut and Linear and rolls it up - marked done only when it's done in every tool it was published to - with per-provider status chips on the board cards and the story view, plus a "Refresh story status" button on the Stories and Budget pages. That completion signal feeds a reworked budget projection: finished published work now counts toward spend, your remaining commitment splits into approved and in-progress work, and buffers and unapproved stories are broken out separately - so you can see at a glance how much budget is left for more work.

Spectr now projects a project's total budget from the work still in flight, layered on top of live Harvest spend. Approved story points convert to hours at a ratio you choose, meeting and miscellaneous buffers reserve headroom, and out-of-scope work is broken out separately. A stacked bar shows spent, approved, and buffers against the budget cap - with the projected total and how much room is left or over-committed. It appears on both the per-project budget drawer and the workspace Budget overview, and the buffer and hours-per-point controls sit right there.

Consistency and clarity across the app: unified status colors everywhere they appear - stories, spec sheets, scope creep, and budgets - plus source and AI-model logos on meetings and spec sheets so you can tell where content came from at a glance, clearer placeholder text in the requirement editor, and a fix that restores the Remember Project toggle and project dropdown sizing on the Integrations page.

Connect Harvest to a project and Spectr pulls your budget and spend right in. Each project gets a budget drawer showing hours and cost - budgeted, spent, and remaining - kept in sync read-only from Harvest, and a new workspace Budget page lays every project side by side so you can see at a glance which are on track and which are heading over. Connect once per project with a Harvest Personal Access Token (an Administrator or Manager account is needed to read budgets).

A new per-workspace "Remember project" toggle sits right in the filter bar. Turn it on and the project you're working in is remembered for that workspace and used as the default everywhere - meetings, requirements, stories, spec sheets, and the Scope Creep Tracker - as well as when you create a requirement or import a meeting. The project selector is also wider, so longer project names stay readable at a glance.

Spec sheets now show a consistent set of source chips whether they were generated from a meeting or from a requirement, so you can always tell where a spec came from.

Connected integrations now refresh their access proactively, before tokens expire, so you run into far fewer surprise disconnections mid-task - and when a connection genuinely needs attention, the Integrations page explains what went wrong in plain language instead of a raw error.

The Scope Creep Tracker picked up a round of refinements: reopen items you had already resolved, page cleanly through long lists, and a set of data-integrity fixes that keep each item's status and its linked stories in sync.

Spectr now tracks scope creep as a first-class part of every project. As it processes a meeting, requirement, or story, the AI flags anything that reads as outside the agreed scope - each with a confidence score and a link back to the exact source - and files it in a per-project Scope Creep Tracker. You can add exclusions yourself, too, for the things you already know are out.

Every item moves through a clear lifecycle: proposed, confirmed, deferred to a future phase, no longer applicable, dismissed as a false positive, or approved back into scope. Stories that are out of scope carry a badge on the board and in lists, and once you link them to an item their scope status follows it - approve the item back in and its linked stories return to scope automatically. A full history log records every change, AI or human, so the trail of what got cut and why is always there.

Connect Read.ai and import your recorded meetings straight into Spectr. Authorize once with OAuth and your recent meetings - transcripts and AI summaries included - become importable, filtered down to the ones relevant to your project. The full AI pipeline applies: context gathering, memory updates, spec extraction, and story generation. You can point a Read.ai meeting at a requirement to generate or update it, and Read.ai, Fathom, and Granola meetings all mix freely in the same project.

Requirements now have an Export menu - download the current document as Markdown or PDF straight from the requirement header, and grab any tagged version from the version history. Exports are generated right in your browser with a timestamped filename, so there's no waiting on the server and your downloads stay organized.

Can't find a file in Drive search? Paste its link instead. The Google integration now accepts any Google Doc, Sheet, Slides, or folder URL and adds it as a context source - Spectr resolves the file type automatically and confirms your connected account can access it.

A new "Generate from memory" action writes a concise project description from everything Spectr has learned about your project, and refreshes the project keywords to match - a fast way to keep your project profile current as scope evolves. Available on Starter and above, wherever AI memory exists.

When you regenerate your project's AI memory, Spectr now shows a live "Regenerating…" indicator and updates the moment the rebuild finishes - no more refreshing to check whether it's done. Reload mid-rebuild and the progress indicator picks right back up.

Uploading a long, multi-page PDF as project context runs AI text extraction as part of the upload, which could previously time out on big documents. Upload timeouts have been extended end to end, so large reference files import reliably.

Spectr can now read your Google Sheets and Slides - not just Docs - when it gathers context for spec sheets and requirements. Spreadsheets come in tab by tab as readable tables, and presentations include both slide text and speaker notes. A refreshed Google picker lets you choose across Docs, Sheets, Slides, and folders, with search across all four. Already connected to Google? Reconnect the integration once to grant access to Sheets and Slides - the new permissions aren't added automatically to existing connections.

Uploading files to create a requirement now generates the document from all of them at once - PDFs and images are read directly by the AI, so nothing is lost to plain-text copying. On the requirement page you can stage reference-file changes and commit them with "Save" or "Create new revision" (with an optional prompt), and if an initial generation fails you can simply "Retry" instead of starting over.

A new "Send feedback" option in the sidebar opens a quick form where you can flag a feature request, bug, improvement, or question. Spectr automatically notes the page you were on, so you don't have to explain where - and the team can reply to you directly.

Spectr's project memory - the knowledge it carries between generations - is now written as one coherent set of documents, so facts land in the right place without duplication across files. Your uploaded context files now inform requirements and memory too, not just spec sheets. And from project settings you can "Regenerate" memory from scratch whenever you want a clean rebuild from your latest requirements, spec sheets, and meetings.

Spec sheets now show which meetings they were generated from as source chips - provider logo and title - on both the list and the detail view, and display how long generation took in plain language (for example, "2m 20s") on spec sheets and requirement versions.

Spec sheets generated from a requirement now have a "New Spec Sheet" action that produces a fresh spec sheet from the exact requirement version the original was built from - no need to track down which version it came from. The action is disabled while a generation is still running, so you won't kick off duplicates by accident.

When you generate a spec sheet from a requirement, Spectr now treats the document as the authoritative scope and decomposes it into concrete deliverables - so requirement-sourced spec sheets come back complete and detailed rather than sparse.

Meeting imports now respect your project's context-gathering setting, and the multi-meeting import flow adds a switch to turn it on or off per import - so you can skip re-scanning your connected integrations when your project context is already current, making those imports faster.

Turn an agreed requirement into a spec sheet in one click - no meeting required. From any requirement, choose "Generate spec sheet" and Spectr runs the same AI spec-extraction it uses for meetings, working from your latest tagged version (or the current draft if nothing is tagged yet). You get a fully-formed spec sheet - named after the requirement, with its tasks and stories - and a provenance chip showing exactly which requirement version it came from. A quick confirmation before you start notes that your connected integrations aren't re-scanned for this run, since it works straight from the requirement document.

Create a BRD or PRD from pasted text, an uploaded file (PDF, TXT, or Markdown), or 1–3 meetings. The document lives in a rich WYSIWYG editor with a working draft you can edit freely. When scope is agreed, tap "Save as version" to tag it with a custom label - version history shows every tagged version with the AI's change summary as bullet points, the source type (AI prompt or meetings), and token usage. A Timeline tab records the full audit trail: every edit, AI update, version tag, and restore as a chronological feed.

Update a requirement with a plain-text AI prompt (synchronous) or point it at a meeting to run the full async pipeline - context gathering, memory update, then generation - so the AI always writes with up-to-date project knowledge. Attach up to 3 reference files (PDF, TXT, MD, or images) per requirement to give the AI additional grounding context.

A project's latest tagged requirement versions are automatically injected into every spec sheet Spectr generates, anchoring AI output to agreed scope. Meetings are now multi-purpose: the same import can feed a spec sheet, update a requirement, or both.

You can now sign up and log in with your Google or GitHub account in a single click - no separate password to create or remember. If you already have a Spectr account on the same verified email, signing in links to it automatically and picks up right where you left off; new accounts skip the email-verification step entirely.

A new Connected Accounts section in User Settings shows which social logins - Google and GitHub - are linked to your Spectr account, along with the email each was connected with, and lets you unlink any you no longer want. Changed your mind? Just sign in with that provider again to reconnect, or use forgot-password to set a regular password.

The register and password-reset forms now show a live strength meter and a requirements checklist as you type, so you know your password is accepted before you submit. Longer passwords and added symbols are recognized as stronger, making it easier to choose something secure.

Billing is now built around the work Spectr actually does for you: each plan includes a monthly allowance of spec-sheet generations, with AI-token usage metered alongside it and any overage billed transparently. A new billing activity log shows your recent plan changes and usage at a glance.

The billing page was rebalanced into a clearer layout, and "Manage subscription" and invoice history now appear only once you have a paid subscription - no more dead-end buttons. Starting a free trial pre-fills your email at checkout (still editable), and secure checkout and payments are handled by our provider, Crowdlinker.

The Fathom and Granola import lists now filter down to meetings that actually relate to the project you're working in. Spectr derives a set of search keywords from each project's description and matches them against your meetings - Granola on title, Fathom on title and summary. Keywords are generated automatically, and you can edit them anytime (Spectr won't overwrite your edits) or regenerate them on demand from project settings.

Regenerating stories now updates in real time - Spectr polls in the background so new stories appear as they're created, with no manual refresh. Deleting a spec sheet also resets its source meeting back to a clean state, so you can reprocess it from scratch without anything left over.

Each meeting now has a copy button for the full integration context Spectr pulled in before processing - handy for sharing what the AI saw or double-checking your sources. Deleting meetings is clearer and safer, and the stories views got a round of visual polish.

Meeting processing is now four switches you control per project: start processing on import, gather integration context, pause to review that context before spec generation, and auto-generate the spec sheet. Set each stage independently to land anywhere from fully automatic to fully manual with review checkpoints - and override them per import when you need to.

The project color palette grew from 14 to 20 colors, giving larger workspaces more room to keep every project visually distinct at a glance.

Enable "Review context before processing" per project and Spectr pauses after gathering context - showing you exactly what it found from your integrations (Notion pages, GitHub issues, Figma files, Linear tickets) before running the AI. Approve the context to proceed, or re-gather with additional hints. The context preview shows topic, a per-provider breakdown, and Figma screenshot count.

Each Fathom and Granola import now has a "Gather context" switch so you can override the project default for that specific import - useful when you want to skip context for a quick test run or force a fresh gather for an important meeting.

Control whether meetings are queued for AI processing immediately on import, or held for manual review. Toggle it per-project in settings, or override it on the fly from any import screen. Multi-meeting imports always process immediately.

The project and meeting dropdowns in the Stories review page now correctly narrow down results. Previously, selecting a project or meeting updated the URL but had no visible effect on the stories shown - that's fixed.

Admins and owners can now resend workspace invitations at any time - including after expiry - directly from the team members list. Each pending invite row shows how long until it expires (or that it has already expired), and a Resend button regenerates the token and sends a fresh email.

After completing a checkout or returning from the Polar subscription portal, your plan and usage now update automatically - no manual refresh needed. The billing page polls for changes in the background to pick up the webhook-driven update.

A new Viewer role gives teammates read-only access without consuming a paid seat - ideal for stakeholders who need visibility without full membership. Seat limits are now enforced during invites and role changes: workspace settings shows live seat usage, an upgrade prompt replaces the invite form when you're at the limit, and new members are auto-assigned Viewer when the workspace is full.

The onboarding wizard now includes a mandatory Create Project step between workspace setup and integrations - you can't advance without a project, so every new workspace starts with a concrete foundation. The workspace step also now supports full slug editing with immediate URL navigation on change.

New users are now auto-logged in after registration and guided through a step-by-step onboarding wizard - create your workspace, connect an integration, and take your first action. An email verification banner persists until your address is confirmed, with a one-click resend that respects a cooldown to avoid spam.

Switch your stories view to a Kanban board - one column per status, drag cards between them to update status inline. Publish and reject dialogs let you move stories through the approval flow directly from the board.

When connecting Google Drive, you can now pick exactly which folder Spectr reads for project context - so the AI sees the right docs, not everything in your Drive. MCP-based discovery makes the folder picker fast and reliable.

All dashboard routes are now scoped to your workspace slug - making deep links reliable, multi-workspace switching seamless, and the URL always reflect exactly where you are.

Spectr now has its own brand logo - replacing the placeholder across the app, email templates, favicons, and marketing pages.

Select 2–3 Fathom or Granola meetings - mixed or matched - and process them into a single spec sheet. The AI splits its context budget equally across all transcripts. Multi-meeting sheets are visually tagged throughout the app, and you can pick which linked meetings to include when regenerating.

Meetings that get stuck in processing now automatically time out and fail cleanly after 15 minutes. Import errors no longer carry over when you switch to a different meeting or note. Fathom and Granola now have distinct icons in the import dropdown.

Connect Granola and import your meeting notes directly into Spectr. The full AI pipeline applies - same context gathering, same memory updates, same story generation. Granola and Fathom meetings can be mixed in the same project.

Spectr now searches your Shortcut board for relevant stories before processing a meeting - the same way it already reads your Linear backlog. Stories come out more grounded when the AI can see what your team has already built.

The integrations page is now grouped into four sections - Meetings, Design & Development, Knowledge & Documents, and Project Management. Each section is a clean list row showing status, account, and actions inline.

Shortcut now shows your workspace name after connecting - so it's clear which account is linked. Both Shortcut and Fathom now detect expired or revoked API tokens at runtime and flag the integration immediately, before they can silently block a meeting import.

Connect your Shortcut workspace and publish stories directly from Spectr. Stories map to Shortcut types, priorities, labels, and assignees. Edits sync back - and Spectr blocks re-publishing a story that already exists in your backlog.

Sharing a filtered view now preserves your filters in the URL - so a link actually shows what you see. Copy buttons make grabbing story content frictionless. Story fields save inline without a separate action.

Managing who can do what in your workspace is now more intuitive. Role changes take effect immediately with clearer confirmation.

Spec sheets and story descriptions now use a proper rich text editor. Format headings, lists, and code blocks without thinking about Markdown syntax - it just works.

Cleaner typography, consistent components, better spacing throughout. The interface now matches the quality of the product underneath it.

Each project now has its own settings page. Sort your meetings and spec sheets by date, title, or status - your preferred order persists.

Every AI-generated spec item now shows how confident Spectr is, and whether it should be a parent task. You can see at a glance which outputs need a closer look before approving.

Workspace settings now shows invitations that are waiting on teammates - so you're never guessing whether someone got the email or needs a nudge.

Spectr now builds a persistent knowledge base per project - product overview, features, architecture, glossary, open questions, and team context. Every meeting makes it a little smarter. Available on Starter and above.

Full subscription lifecycle is now live. Upgrade, downgrade, track your monthly usage, and manage your plan - all from within Spectr. Overages on meetings and tokens are handled gracefully.

The full authentication experience is now complete. Invite teammates by email, verify your account, and reset passwords - all with proper email flows and token-based security.

Empty pages no longer just show blank space. Each one now guides you through the next step - so new workspaces have a clear path forward.

Before processing a single line of your meeting, Spectr now searches your connected Notion docs, Figma files, GitHub issues, and Google Docs. Stories come out grounded in real project context, not just what was said in the call.

Spectr now detects when a newly generated spec item is semantically similar to something already in your backlog - reducing noise and keeping your stories clean.

Configure how Spectr's AI behaves for each project - spec focus, output style, and context priorities. One team's ideal output isn't another's.

All 7 integrations now use proper OAuth with automatic token refresh. Connect once and Spectr keeps itself authorized - no manual re-linking, no expired sessions mid-processing.

Connect your Notion workspace and Figma files. Spectr reads them during story generation - pulling in documentation context and design details so every story is actually useful to the engineer picking it up.

Spec processing now shows real-time status per task - you can watch Spectr work through your transcript and reprocess individual items that need a retry.

Projects you're no longer actively running can be archived - keeping your workspace tidy without permanently deleting anything.

Not using Fathom? Upload transcripts directly as PDF, TXT, or DOCX. Spectr handles the extraction and gets to work - same pipeline, any source.