◀ back to the crew

> cat ~/docs/use-cases.md

use cases

How I actually use each of my nine Grok Bots, written up as docs so anyone can see how the fleet works.

00

how the fleet works

I run my bots like a small company. I'm the CEO, Lily is the front door, and everyone else sits in a division with a clear job.

top management

technical division · ryan

resources division · amanda

1

ask

I either tell Lily what I need and she routes it, or I chat the right bot directly. Every bot is set up so I can message them anytime.

2

work

The bot does the job with its own tools (GitHub, Notion, Netlify, Google, Mermaid) and hands off to another bot when the task belongs to someone else.

3

report

Division heads report daily, and Top Management meets in a group chat at 6:00 PM every day to report each division's work to me.

a day in the fleet

  1. Sophia drops the morning brief
  2. James audits the latest commits
  3. Ryan files the tech division report
  4. Amanda files the resources division report
  5. Top Management meets and the division heads report to fiqq
01

the bots

Jump to a bot, or scroll through all nine.

bot 01 / 09

Lily

Chief of Bots

division
Chief of Bots
reports to
fiqq (CEO)

My primary bot and the front door to the whole fleet. If I'm not sure who should handle something, I just tell Lily.

what I use her for

  • Takes any task I throw at her and routes it to the right bot in the fleet.
  • Saves me from remembering who does what: I describe the job, she picks the bot.
  • Handles switching my primary bot: she lists my bots with a one-line reason for each, asks which one I want, sets it and confirms.

when it runs

On demand, whenever I send her a task.

works with

  • Every bot in the fleet (she hands tasks to them)
  • fiqq

example asks examples

  • > I need a workflow diagram for my deploy process. Who should take this?
  • > Pass this question about my GitHub repo to whoever handles it.
  • > I want a different primary bot. What are my options?
▲ back to the list

bot 02 / 09

Xavier

Bot Manager

division
Top Management
reports to
fiqq (CEO)

The day-to-day ops lead of the fleet. Xavier keeps the bots running so I only get pulled in when there's a real decision to make.

what I use him for

  • Manages the bots themselves: adds new bots and edits existing ones (deleting a bot stays with me).
  • Assigns tasks and routines to the bots.
  • Reports when a bot fails a routine or a task.
  • Runs the fleet day to day and only pulls me in for decisions.

when it runs

On demand, plus whenever a bot misses a routine or fails a task. Reports in the 6:00 PM Top Management meeting.

works with

  • All bots in the fleet
  • Ryan and Amanda (Top Management)
  • fiqq, for decisions only

example asks examples

  • > Did any bot miss a routine today?
  • > Add a new bot to the Technical Division and give it a routine.
  • > Assign Alex a task to update the project docs.
▲ back to the list

bot 03 / 09

Ryan

Chief Technical Officer

division
Top Management · head of Technical Division
reports to
fiqq (CEO)

Runs the Technical Division and is my go-to for anything technical or development related.

what I use him for

  • Sends a daily Technical Division report in a Division Update / Officer Update format, and stays quiet if there's nothing to report.
  • Answers my questions about technical matters and development.
  • Asks clarifying questions when my request is ambiguous instead of guessing.
  • Oversees the division's officers: Mark, James, Alex and Nina.

when it runs

Daily Technical Division report, plus the 6:00 PM Top Management meeting. Technical questions on demand.

works with

  • Mark, James, Alex and Nina (his officers)
  • Xavier and Amanda (Top Management)
  • The Top Management group

example asks examples

  • > What's the Technical Division update for today?
  • > Should this logic live in React or on the Node.js side?
  • > What should I think about before changing my MySQL schema?
▲ back to the list

bot 04 / 09

Amanda

Personal Assistance

division
Top Management · head of Resources Division
reports to
fiqq (CEO)

Runs the Resources Division and owns the fleet's memory. If it needs to be remembered, logged or connected, it goes through Amanda.

what I use her for

  • Owns Notion for the fleet: manages the Shared Memory (facts every bot shares) and each bot's own Memories.
  • Keeps the Activity logs of tasks the bots have run.
  • Handles account authentication and third-party integrations.
  • Keeps the fleet calendar.
  • Sends a daily report about the Resources Division.

when it runs

Daily Resources Division report, plus the 6:00 PM Top Management meeting. Memory, logs and integrations on demand.

works with

  • Notion
  • Sophia (her officer)
  • Lily and Ryan (Top Management)

example asks examples

  • > Save this to Shared Memory so every bot knows it.
  • > What tasks did the bots run today? Check the activity log.
  • > Help me connect a new account integration.
▲ back to the list

bot 05 / 09

Mark

Project Manager

division
Technical Division
reports to
Ryan (CTO)

My personal assistant for all my GitHub repos. Mark is who I talk to when I'm thinking through a project.

what I use him for

  • Q&A and discussion about any of my GitHub repos.
  • Talks through architecture and how a project is put together.
  • Discusses features and helps write implementation plans.
  • Pulls context from GitHub and the Notion progress hub (Commit Logs and Project Milestone).
  • Asks clarifying questions when my request is ambiguous.

when it runs

On demand, anytime I want to talk about a repo.

works with

  • GitHub
  • Notion (Commit Logs, Project Milestone)
  • James (security audits stay with him)
  • Ryan

example asks examples

  • > How is this repo structured, and where should a new feature go?
  • > Write an implementation plan for adding this feature to my project.
  • > Which milestones has this project hit so far?
▲ back to the list

bot 06 / 09

James

Technical Auditor

division
Technical Division
reports to
Ryan (CTO)

My daily security and improvement auditor. James looks at what I committed and tells me what to fix or improve.

what I use him for

  • Runs a daily security and improvement audit of my GitHub commits across my active repos.
  • Keeps the chat report to improvements and security findings only: no commit dumps, no repo Q&A.
  • Logs commits and features into the Notion Commit Logs.
  • Updates the Project Milestone when commits map to features.
  • Stays silent on days with no commits.

when it runs

Daily audit (silent if there were no commits). I can also ask for an audit directly.

works with

  • GitHub
  • Notion (Commit Logs, Project Milestone)
  • Mark (repo questions go to him)
  • Ryan

example asks examples

  • > Run a security audit on today's commits.
  • > Any improvements you'd suggest from my latest commits?
▲ back to the list

bot 07 / 09

Alex

Designer

division
Technical Division
reports to
Ryan (CTO)

The fleet's designer. When I need something visual or written up, Alex handles it.

what I use him for

  • Generates images.
  • Turns workflows into Mermaid diagrams.
  • Writes and handles markdown documentation.

when it runs

On demand, whenever I need design, diagrams or docs.

works with

  • Mermaid
  • Markdown
  • Ryan

example asks examples

  • > Turn this workflow into a Mermaid diagram.
  • > Write a markdown README for this project.
  • > Generate a pixel-style image for my site.
▲ back to the list

bot 08 / 09

Nina

Netlify Manager

division
Technical Division
reports to
Ryan (CTO)

Looks after my Netlify account and the sites on it. Nina built and shipped this website.

what I use her for

  • Handles deploys for my Netlify sites.
  • Manages site settings, domains, environment variables, forms and functions.
  • Keeps an eye on deploy health, and can check status, logs and settings anytime.
  • Asks me first before anything destructive or public-facing: deleting sites or deploys, changing domains or DNS, changing environment variables, rolling back production or creating new sites.
  • Keeps replies short and plain, with times in Malaysia time.

when it runs

On demand. Reports into Ryan's Technical Division update.

works with

  • Netlify
  • GitHub (where my code lives)
  • Ryan

example asks examples

  • > Is the latest deploy on my portfolio healthy?
  • > Check the deploy logs for my most recent site.
  • > Build me a site and deploy it to a new Netlify site. (She checks with me first.)
▲ back to the list

bot 09 / 09

Sophia

Reporter

division
Resources Division
reports to
Amanda (Personal Assistance)

My morning news buddy. Sophia keeps me up to date on AI and Malaysia, and talks like a friend rather than a news anchor.

what I use her for

  • Sends a daily news brief at 8:00 AM covering AI news (with context) and Malaysia news.
  • Looks things up on Google before answering factual questions.
  • Keeps the tone casual and conversational, like chatting with a friend.

when it runs

Daily at 8:00 AM. Questions on demand.

works with

  • Google search
  • Amanda

example asks examples

  • > What's the big AI news today, and why does it matter?
  • > Anything happening in Malaysia I should know about?
  • > Quick fact check: is this headline true?
▲ back to the list
◀ back to the crew