Skip to content
Spool, the agent

A teammate that has read every meeting and every doc.

Ask it anything about a project and get an answer with sources. Or hand it work the way you would a teammate, and review what comes back.

Spoolfor Priya ShahWaiting on you

@Spool write stories from this meetingKickoff call with Acme · comment

  1. Read Kickoff call with Acme42 min · 3 decisions
  2. Read Payments requirements v38 sections
  3. Checked Triage for duplicatesnone found
  4. Drafted 3 storieswith acceptance criteria
  5. Waiting for Priya to reviewnothing lands until then
  • ACM-42DraftPartial refunds4 acceptance criteriaCall · 14:02
  • ACM-43DraftManager approval after 30 days3 acceptance criteriaCall · 21:40
  • ACM-44DraftRefund reason on the receipt2 acceptance criteriaRequirements v3 · §4
Nothing is saved until you choose.
The rules

Agents do the work. People stay in charge.

Every run acts for a person and sees only what they can. Risky changes wait for that person, and every change is logged.

Acme payments · Run for Priya ShahGroom the refunds backlog
Waiting on you

Close 3 duplicate items?Bulk changes wait for a person.

  • ACM-38Refund fails on bundle orderssame as ACM-46
  • ACM-39Refund button greyed outsame as ACM-42
  • ACM-40Refund older orders in partsame as ACM-43
Acting as Priya · her access only
Ask

Ask anything. Get the source.

Spool searches the meetings, docs, items and files you can see, and links each part of the answer to where it came from.

WorkspaceAsk Spool
Acme payments

Why did we drop Stripe Checkout?

The client wants partial refunds first, and Checkout only refunds whole orders. Requirements v3 moved refunds to the Payments API instead.

Searched 6 meetings · 4 docs · 31 items

Sources

  1. “Bundle customers churn when refunds are all or nothing. Partial refunds ship first.”

  2. “Checkout can only refund the whole order, so bundles don’t work there.”

  3. Refunds go through the Payments API, not Stripe Checkout.

Hand it work

Give it work like a teammate.

Assign it an item, @mention it in a comment or tell it in ⌘K. When it needs you, it asks in your Inbox.

Acme payments · ACM-45Groom the refunds backlog
Assignee
UnassignedSpool
Requested by
Priya Shah
Status
In progressWaiting on you

Merge ACM-38 into ACM-46?They describe the same bug.

Skills and MCP

A playbook for each job. Your agent too.

Spool follows a skill for each job, set per team. Your coding agent connects over MCP, with your permissions.

Payments team · SettingsSkills
  • Write storiesWith acceptance criteria, linked to the sourceOn
  • Draft requirementsScope and rules, citing the callsOn
  • Groom the backlogDuplicates, stale items, missing criteriaOn
  • Summarise for a clientPlain language, no internal notesOff
  • Make a reportWhat moved and what is blockedOn
  • Implement an itemA coding session that opens a pull requestSoon
Questions

Fair questions.

Still unsure? Book a call or write to us.

01Is our data used to train models?

No.

02Can Spool see things I can’t?

No. It reads only what the person who asked can read, so private teams stay out of your answers.

03What does it do without asking?

Small things, like creating an item, land in Triage. Bigger work comes back as a draft, and risky changes wait for a person.

04Can I use my own coding agent?

Yes. Connect any MCP client and it works as you, with your permissions. See how.

05Who can turn skills on or off?

Admins and team leads, for each team.

  1. MeetingKickoff call with Acme42 min · 3 decisions
  2. DocPayments requirementsv3 published
  3. ItemACM-42 Partial refundsSprint 12 · review
  4. CodePull request linkedcoming next
  5. TestTested against the storycoming next

Bring the whole project. Close the other eight tabs.

Book a call

Free until public launch · onboarding teams in small groups

Type to search…

↑↓ navigate↵ selectEsc close