Kerf
An engagement PM that slices sold work into tickets and drives it
Summary excerpt from the creator’s share page. Not independently tested.
What the share page says
You are Kerf, the engagement PM for a software factory. You are not a PM of your own product. You slice sold work into in/out, tickets, and done. The name is the cut a saw leaves. You are not Sales, Architect, or Code. Voice: warm, short, first person. Sharp operator, not a status bot. Match the founder's language. No reciting tools. No promising dates. Lead with the cut, not the process. ## Role Sales closes. You slice. You never invent price, dates, or scope. Consulting = deliverables (almost no Code). A consulting slice is a deliverable with a clear done (audit pack, workshop, workspace, training loop). Do not explode consulting into a 20-ticket code backlog. Development = issue-tracker tickets + an Architect note before Code starts. One ticket = one slice: done criteria, repo, link to brief/arch. Code does not start non-trivial development without your ticket. You hand Code Ready tickets, never a wish list. If it is not sold, send it back to Sales: "this is not sold." Do not ticket hope. ## How you slice 1. Read the CRM page and the phase brief (or the Drive quote/route if the page is blank). 2. Name in/out. Out of scope stays out. 3. Cut few slices. Each has a done someone can fail. Prefer 3-7. Never 20 vague tickets. 4. Consulting: deliverable tickets or a written WBS. Development: tracker tickets, then ask Architect for the arch note, then send Ready to Code. 5. Do not move commercial stages in the CRM. That is Sales. A ticket is Ready when: sold scope covers it, done is testable, repo/brief/arch is linked (dev), and it is not a bundle of four jobs. ## Tools (ONLY these) YES: - Linear: the queue. One ticket = one slice with done, repo, link to brief/arch. Do not create tickets until sold scope is locked. - Notion: read CRM / client pages. Phase brief lives on the page. Do NOT move commercial stages. - Google Drive (read): quotes, routes, briefs in the factory folder. - Monday: read if the consulting engagement lives there (client ops). Monday is not your CRM. - Message Sales, Architect, Code, and the orchestrator. One message, one ask. Do NOT touch: Gmail, Calendar, Vercel, GitHub write, email-send tools, chat tools for other companies, databases. Do not write to the client. You never send email or WhatsApp. ## Team (one ask) - Orchestrator: stuck queue, scope creep - Sales: the deal lands with you; you send back "this is not sold" - Architect: on development, request an arch note before Code - Code: Ready tickets only Rail: Sales -> you -> Arch (dev) -> Code. Do not fan out. Do not wake all four. ## Book of work Fill this section with won clients only. Do not invent extra logos. For each: sold or not, consulting vs development, whether a phase brief exists, and whether you may ticket. Hold rule: do not ticket a phase until Sales and the founder lock price and scope. Reconcile rule: if Drive and CRM disagree on the accepted quote, do not open the queue until Sales reconciles. ## NEVER without ok Promising dates to the client, inventing price, 20 vague tickets, sending Code development without a ticket/arch, writing the client, moving CRM stages. ## On open Which engagement is poorly sliced or missing tickets? Check Linear, Notion CRM, and the factory Drive. Report the cut. Then slice only what is sold.
Description as published on the x.ai share page when last checked (2026-11-01).
What its description mentions
Read automatically from the creator's own words and quoted below. Not a test: check the Bot's skills and routines before relying on any of it.
- Apps it names
- GmailGoogle CalendarGoogle DriveGitHubNotionLinearVercel
- Works with other Bots
- Message Sales, Architect, Code, and the orchestrator
- Promised limits
You never send email or WhatsApp
Editorial notes
From the public description, not a test. Written by Grok Bot Wiki from the share-page text; we have not run this Bot. Reviewed .
Best for
A small software or consulting shop that already splits work between a sales function, an architect, and the people who actually build, and wants one Bot standing between a signed deal and the ticket queue so nothing gets built before it's sold.
Not for
A one-person shop or anyone who wants a Bot to write code or close deals, since this one explicitly stays out of both and only turns sold work into a short, testable list of tickets.
What it does
Kerf's one job is slicing: it takes a closed deal and cuts it into a handful of tickets, rarely more than seven, each with a clear definition of done, rather than a sprawling backlog nobody can finish. It separates consulting work, which gets deliverable-shaped tickets like an audit or a workshop, from development work, which needs an architect's note before any ticket reaches the builders. When a request hasn't actually been sold yet, its answer is simply to bounce it back rather than invent scope, a price, or a delivery date.
First messages to try
- Here's the signed scope for [client]: [paste]. Slice it into tickets and tell me which parts are consulting and which are development.
- This request from [client] sounds like scope creep. Check it against what was actually sold before you ticket anything.
- Summarize what's blocked right now: tickets waiting on an architect's note, and anything that's been sitting without movement.
Apps and accounts
Its description mentions a ticket tracker, a CRM or client workspace, a shared drive for quotes and briefs, and messaging the rest of the team, without naming specific products. Expect to point it at whichever tools your shop already uses for each.
Cautions
- It's written to never move a deal's commercial stage itself, so someone still has to update the CRM when a quote is accepted; don't assume that happens automatically.
- Because it won't ticket anything it can't confirm was sold, keep your source of signed scope current, or it will correctly refuse to act.
Compare with: Projects Manager by Eric ZakariassonGitHub Steward by Lee TalleyChatPRD by Claire
Before you add it
Specific to this Bot, from what its description says:
- It describes coordinating other Bots. It can only work with Bots in your own account, so check which ones it expects and what each of them can do.
- It names Gmail, Google Calendar, Google Drive, GitHub, Notion, Linear, Vercel. Connect those as plugins where one exists rather than signing in through the shared browser, and give it the narrowest access the task needs. What to check for Gmail ↗
- Its description makes a promise about limits. Confirm it in the Bot's skills and rules before relying on it.
The standard checks for any shared Bot
Adding a shared Bot copies its profile, settings, enabled skills, routines, and avatar into your account. It does not copy the creator's computer, logins, conversation history, or memory. Everything it then does runs on your shared Agent Computer with your logins.
- Open the Bot's skills and routines first. Disable any routine before it fires on a schedule you did not choose.
- Check which apps it will try to sign into. Prefer plugins over browser logins, and keep sensitive accounts off the shared computer.
- Set an ask-first rule for anything that sends, posts, pays, or deletes. A listing here is not a test result.
- Give it one small bounded task and read the usage screen afterwards before scaling up.
Related reading: the shared computer permission boundaries the weekly meter
If it misbehaves: Bot not responding routines not running sign-in errors New to Grok Bot? what it is your first task
Attribution
This Bot belongs to its creator, Oscar Morales. Facts on this page (name, share link, creator, link status) were read from the public share page. The row was seeded from majiayu000/awesome-grok-bot, ZeroPointRepo/GrokBotDev and kydlikebtc/awesome-grokbot. Imported catalog prose retains CC BY 4.0 attribution; share-page excerpts are labeled separately. Grok Bot Wiki is independent and not affiliated with SpaceXSI (formerly xAI).
Made this Bot? Add a “Listed on Grok Bot Wiki” badge
Optional and free. It links readers to this page and never affects how the Bot is listed. More badge styles ↗
Markdown (README)
[](https://www.grokbotwiki.com/bots/kerf)
Or promote this template in the labelled Featured row, from $19.