Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.thor.ai/llms.txt

Use this file to discover all available pages before exploring further.

You shouldn’t have to choose between doing the work and tracking the work. Thor handles the tracking. You focus on the work.

​
The work nobody wants to do

Every team is held together by a quiet pile of busy work. Nobody enjoys it. Almost nobody is great at it. If it doesn’t get done, things start to fall apart. You know the list:
  • Writing the issue after the Slack discussion ended.
  • Updating the issue’s status when you actually start it. Or finish it. Or get blocked.
  • Writing meeting notes. Tagging the right people. Listing action items.
  • Following up the next day to see if those action items got done.
  • Updating the doc that became wrong as soon as the feature shipped.
  • Logging the decision that was clearly made in chat but written down nowhere.
  • Closing out the “good idea, but we’re not doing it” so nobody re-pitches it in three months.
This is the connective tissue of a healthy team. It’s also exactly the work that gets skipped when people are busy — which is always.

​
You skipped hiring a PM. You didn’t skip the PM work.

A lot of fast-moving AI-first teams have made a deliberate call: no dedicated project manager, no dedicated product manager, no extra layer of process. Engineers ship. Founders decide. Things move. The problem is that the work a PM would have done didn’t disappear. The issues still need to be written. Decisions still need to be tracked. Action items still need follow-up. Docs still need to stay current. That work just quietly landed on whoever was closest to it — usually the tech lead or the founder. The same people who were supposed to be heads-down building are now writing meeting notes, updating the roadmap, and chasing down owners. You inherited it. It’s slowing you down.

​
What LLMs did for code, Thor does for the team

Cursor and Claude Code didn’t make engineers obsolete. They removed the parts of writing software that were tedious and repetitive — boilerplate, unit tests, doc drafts — so engineers could spend their time on the parts that actually need a brain. Thor does the same thing for everything around the code. It doesn’t replace the judgment calls. It doesn’t replace the meetings, the decisions, or the work itself. It removes the paperwork around the work — the tracking, logging, tagging, summarizing, reminding, and following up that has to happen for the team to stay coordinated, but that nobody signed up to do.

​
Thor doesn’t replace your tools. It makes them work better.

You already picked the tools your team likes. Linear, GitHub, Google Docs, Notion, Google Calendar, Zoom, Slack. Thor’s job isn’t to replace any of them — it’s to make them more accurate, more current, and more useful.
  • Linear and GitHub stay your source of truth for issues. Thor makes sure issues exist, get updated, and reflect what’s actually happening.
  • Google Docs and Notion stay where knowledge lives. Thor watches for changes that matter and proposes the edits.
  • Google Calendar, Meet, and Zoom stay where meetings happen. Thor turns transcripts into action items in the systems you already use.
  • Slack stays where your team talks. Thor lives there too — no new app to check.
Every action Thor takes lands in a system you already trust. Same tools you have today, with the tracking, history, and follow-up they were always supposed to have.

​
Three buckets of busy work Thor handles

​
1. Not every change needs a task. The big ones do.

AI has made some work so fast that logging it is overhead. Need a small fix or a one-off script? Hand it to Claude or Cursor, get a PR, ship it. The whole loop takes minutes — a Linear ticket would slow it down, not help it. But that’s not most of what your team does. Bigger projects, long-running work, epics, anything that spans more than one person or more than a week — those still need a tracked home. Roadmaps need work items. Estimates need a record of what’s actually been done. New hires need a trail to follow. The catch is that the useful tasks — the ones tied to real work in flight — are exactly the ones that get neglected. The discussion happened in Slack. The decision happened in a meeting. By the time someone gets back to Linear, half the context is gone. Thor closes that gap:
  • Turn a Slack thread into a properly written GitHub or Linear issue in one message. See Tasks.
  • Pull action items out of meeting transcripts and offer to convert them into tracked work. See Meetings.
  • Notice when work has started, stalled, or finished — and offer inline buttons to update status without leaving Slack. See Quick actions.
When the tasks that matter actually reflect reality, your roadmaps, estimates, and reports start to mean something.

​
2. Docs should stay reliable

The fastest way to lose trust in your docs is to write a beautiful one that’s wrong six weeks later. Thor treats docs as living context, not static artifacts. As your team ships features, makes decisions, and changes course, Thor listens for the changes that matter and proposes updates to the docs that need them. See Documents. The bar isn’t “every doc is perfect.” It’s “you can trust what’s there.”

​
3. Conversations should leave a trace

Every meeting and every long Slack thread either produces something concrete or leaves a question hanging. Both need to be captured — including the boring ones. After a meeting, Thor will:
  • DM each participant their action items and decisions.
  • Cross-reference anything that was also discussed in a previous meeting (so “we already decided this” stops happening).
  • Follow up the next day if action items haven’t moved.
Even the “good idea, but we’re not doing it” decisions get logged — because future-you will thank present-you for writing it down.

​
Why this matters more than it sounds

When the busy work gets done consistently:
  • Predictability gets better, because what’s in flight reflects what’s actually happening.
  • Onboarding gets faster, because the trail of decisions actually exists.
  • Less work falls through the cracks, because action items have an owner and a follow-up.
  • Your lead gets a real picture, because reports aren’t built on incomplete data.
  • Your AI agents get smarter, because they have a reliable history to draw from.
When it doesn’t, the team runs on tribal knowledge, status meetings, and the heroics of whichever person is best at remembering things.

​
An honest note

Thor handles a lot, but it doesn’t replace your judgment. Thor will draft an issue from a Slack thread — you decide whether to ship it. Thor will propose a doc update — you approve it. Thor will surface action items from a meeting — you call which ones matter. Think of Thor as a teammate who does the first 80% of the busy work for you. The last 20% — the part that needs your call — is still yours.