This kit gives a Grok Bot you own the upkeep side of Getting Things
Done. The Bot captures what comes in, clarifies it into actions and
projects, keeps your lists current, and prepares your reviews.
Everything it does goes into a saved record. You keep the decisions.
This page takes you from download to a first useful result, then to
the next step. The background is in the
article.
What you need
A Grok Bot you own. Access and usage may require an
eligible paid plan. Check current eligibility and billing in xAI's Grok Bot overview.
Downloading an app does not give you eligible access.
Open a conversation with your Bot. A Bot you already use is fine,
because setup works in its own new folder.
Attach the ZIP as one file. Don't unzip it.
Send this message exactly:
Set up the Edge Operator GTD Starter Kit 0.3.0 from the attached archive. Read BOOTSTRAP.md inside it and follow that setup procedure with me.
The Bot will ask for four things:
your name
your timezone
what the record should cover and what it should leave out
whether the folder it proposes is right
Skim the setup report. Each part is marked tested, available,
unconfigured, or blocked. Email, calendar, and routines will show as
unconfigured. That's expected, because nothing is connected yet.
If the Bot can't open the archive, unzip it yourself, attach all nine archive members (`README.md`, `BOOTSTRAP.md`, `GTD-METHOD.md`, `GTD-WORKFLOW.md`, `BACKEND.md`, `TESTS.md`, `eo-gtd/SKILL.md`, `eo-gtd/references/method.md`, and `manifest.json`), and send the same message.
Your first win: three loose
ends
Pick three real things that are nagging at you. Small and ordinary is
fine: a reply you owe, a form to file, something someone promised you.
Then send:
Capture these three loose ends: [first], [second], [third]. Then help
me clarify them one at a time. Ask only what you need from me, don't
invent outcomes or dates, and save what we decide.
What you should see:
The Bot works through one item at a time with short questions, such
as what done looks like or what the very next step is.
Vague items become concrete. "Deal with insurance" becomes something
you can actually do, like "Call the insurer to ask whether the claim is
still open."
If a task belongs to someone else and you haven't asked them yet,
asking them stays on your list as your next action.
It finishes with a short receipt of what it saved.
Later, tomorrow or in a fresh conversation with the
same Bot, ask:
What next actions do I have saved?
The Bot should read them back from the record, not from the earlier
chat. It may ask you once to confirm which record to use, which is
normal. Getting your actions back proves the record persists: what you
clarified is still there when you return.
Next: connect email and
calendar
Three loose ends show the record works. The bigger change comes when
the Bot can look where your commitments actually arrive. Fill in your
account and send:
Connect my email and calendar for GTD, read-only, using [account].
Reuse connections this Bot already has, and tell me if one is missing.
Email: search the last seven days and pick one ordinary thread with a
loose end in it, skipping anything sensitive. Calendar: my primary
calendar, next seven days. Capture what you find as proposals, not
commitments. Don't create any routine yet.
You don't need to find an email yourself. The Bot picks one within
the search you set. Before reading, it checks that the account matches
what you named. It does one bounded read per source, then reports what
it actually saved. Anything a message asks of you stays a proposal until
you accept it.
Worth knowing: a connected account may technically allow more than
reading, including sending. Staying inside your scope and asking before
any send or calendar change are rules the kit gives the Bot. They are
not locks on the account.
Then: agree on a routine
Once a connected read looks right, choose a rhythm:
Propose a weekly review routine for [day and time] in my timezone.
Create it paused and show me exactly what you set up.
When the readback matches what you asked for, tell the Bot to turn
the routine on. Some things to expect:
Scheduled runs may not start at the exact minute.
A review only covers what it could read. If a source or checklist
was missed, the Bot saves the review as incomplete and names what's
missing.
A daily brief is a separate choice that follows the same
pattern.
Paste them as written, or say the same thing in your own words. Cards
that need a connected calendar or inbox say so.
If you already run GTD
Start the same way. When the fresh record looks right, ask for an
import plan for your existing lists. Import is a separate step and waits
for your yes.
Good to know
The Bot never decides what you commit to or what matters most.
Bots on one account share files and logins, and the kit keeps to its
own folder only by instruction. For real separation between work and
personal, use separate accounts. Keep employer data out unless your
employer allows it.
The kit is independent. It is not endorsed by David Allen and is not
a copy of Getting Things Done. The book is where to learn the
method.
Prompts to use after setup
Empty my head
When to use this
Your mind is cluttered, or you're starting fresh. No connected accounts needed.
Prompt
Run a mind sweep with me. Ask me a few prompts at a time: promises I've made, things others owe me, upcoming events, money, home, health, people, loose notes. Capture what I say as I say it. When I tell you I'm done, clarify each item with me one at a time using the kit's method. Ask only what you can't work out yourself. Anything that's a request from someone else, or your own suggestion, stays a proposal until I accept it. Save as we go.
What you should get
Short batches of prompts, not a long questionnaire. Your words are saved as captures. You then get item-by-item clarification into next actions, projects, Someday/Maybe, or reference, with proposals labeled as proposals. It ends with a receipt counting what was saved.
Untangle a project
When to use this
A project feels fuzzy or stuck. No connected accounts needed.
Prompt
Help me plan [project] at whatever depth it actually needs. Draft from what I've already told you, and ask only what's mine to decide: why it matters, what done looks like, and what would rule an approach out. If I start brainstorming, write my ideas down raw and don't rank or trim them until I say organize. Then propose the parts and next actions, and I'll pick which to accept. If a step belongs to someone I haven't asked yet, asking them is my action.
What you should get
The project outcome written as if it's already done. Brainstorm ideas saved word for word in the project's notes. A proposed set of parts and next actions, clearly marked as proposed until you accept them. If the way forward is unclear, the next action is a planning step.
Choose what to do now
When to use this
You have a gap and want a sensible next move. Works without accounts. A connected calendar adds today's commitments.
Prompt
What should I do now? I'm [where you are], I have [how long], and my energy is [high/medium/low]. If my calendar is connected, check today first. Show me saved next actions that fit, and label any ordering as a suggestion.
What you should get
If the calendar was read in this conversation, today's fixed commitments come first. Otherwise the Bot says they're unknown. Then you see actions from your record that fit what you told it. Anything you left out is treated as unknown, not guessed from an earlier chat, and the ordering is marked as a suggestion.
Prepare for a meeting
When to use this
Before a conversation with a person or group. Finding the meeting time needs a connected calendar; the agenda works without one.
Prompt
I'm meeting with [person or group] [when, if you know]. If my calendar is connected, look for the meeting there. Pull together their agenda, anything they owe me, anything I owe them, and related project actions. If you can't find the meeting in my calendar, say the timing is unknown rather than guessing. Add anything new I tell you to their agenda.
What you should get
One prep list for that person or group: agenda items, open Waiting For items, and your related actions. A clear statement of whether the meeting was found in a calendar read just now or its timing is unknown. New points are saved to their agenda.
What's slipping?
When to use this
Something feels overdue. Works from the saved record; connected inbox and calendar make it more complete.
Prompt
Check what's slipping. Read my connected sources within their approved scope, then show me Waiting For items past their follow-up date or with no follow-up set, hard deadlines coming up, stalled projects, and decisions waiting on me. Draft reminders if they'd help, but don't send anything. Keep resurface and proposed dates separate from real deadlines, and tell me which sources you couldn't read.
What you should get
A short report grouped by type: overdue follow-ups, deadlines that show who set them, stalled projects, and pending decisions. Any reminder drafts are saved but not sent. If something wasn't read, the report says it's partial and names what's missing.
Prepare my weekly review
When to use this
Once a week. Best with connected email and calendar. Without them, the review is saved as incomplete and says so.
Prompt
Get my weekly review ready. Gather from my connected sources and registered checklists, process anything new, and do the mechanical parts: last few weeks and coming weeks of calendar, Waiting For, each project, every agenda, upcoming deadlines, Someday/Maybe. Then bring me the judgment calls as a short list. If any source or checklist can't be read, save the review as incomplete and name what's missing.
What you should get
A list of decisions for you, with must-act ones shown individually. Projects without a way forward are flagged as stalled. A saved review entry marked complete only if everything registered was covered. Otherwise it's marked incomplete, with each uncovered source or checklist named.