General availability · Grok Bots

Seven phases.
Seven Grok PMs.

Grok Bots are now generally available — one Project Manager per SevenD phase, built on Grok, that runs the process of software development once you give it complete inputs.

They don't guess. They don't skip ahead. Hand a PM the finished work of the phase before it, and it drives that phase to a done, gate-passing output — then hands off to the next one.

Meet the bots ↓ How to use them →
Built on Grok (xAI) SevenD Framework Cursor Projects Levels 1–4
What a Grok Bot PM actually does

A PM bot is not a chatbot you brainstorm with. It's a process manager — it takes the complete inputs for one SevenD phase and runs that phase to a decision.

Feed the Discovery PM a raw idea and market context, and it comes back with a prioritized backlog. Feed the Design PM an approved spec, and it comes back with a locked component registry and interface contracts. Every bot enforces the same phase gates the SevenD framework already enforces on humans and coding agents — no spec without a backlog item, no code without a completed design, no deploy without diagnostics passing.

The lineup

The seven Grok PM bots

One bot per phase of the loop. Open a bot, paste in the complete input for that phase, and let it run the process.

Product Loop
01 · Discovery

Discovery PM

Turns a raw idea into a prioritized backlog.

  • Needs: the idea, market/user context, constraints
  • Delivers: backlog with priorities (D‑NNN items)
Open Discovery PM ↗
02 · Definition

Definition PM

Turns an approved backlog item into testable specs.

  • Needs: an approved backlog item
  • Delivers: requirements + acceptance criteria (F##/N##)
Open Definition PM ↗
03 · Design

Design PM

Turns an approved spec into a technical blueprint.

  • Needs: an approved spec
  • Delivers: components, interfaces, contracts, standards
Open Design PM ↗
The Bridge
04 · Documentation

Document PM

Keeps every phase in sync — the single source of truth. Runs continuously alongside the other six, not once in sequence: it checks status before any phase starts and updates it after any phase finishes.

  • Needs: the latest output from whichever phase just closed
  • Delivers: an updated status board / STATUS.md, document index, changelog
Open Document PM ↗
Engineering Loop
05 · Development

Development PM

Turns a completed design into sprint-ready work.

  • Needs: a completed design (components + interfaces)
  • Delivers: sprint plan, task breakdown, build log
Open Development PM ↗
06 · Diagnostics

Diagnostics PM

Turns built work into a pass/fail quality verdict.

  • Needs: built code/feature ready for verification
  • Delivers: test results, coverage report, zero-bug gate check
Open Diagnostics PM ↗
07 · Deployment

Deployment PM

Turns a passing build into a shipped release — and feeds learnings back to Discovery.

  • Needs: diagnostics passing
  • Delivers: deploy log, monitoring plan, fix log, new backlog items
Open Deployment PM ↗
Works at any level

The bots read whatever level you're on

A PM doesn't require Level 3+. It reads the complete input for its phase wherever that lives today — one markdown file, a phase folder, or a GitHub Issue — and produces the same gate-passing output either way.

1

Two files

Solo · weekend · prototype

Product.md carries Discovery + Definition + Design; Tech.md carries Development + Diagnostics + Deployment. Paste the relevant section into a PM as its complete input — expect a fast, low-ceremony pass.

2

Four files

Small team · real project

Same split, plus Architecture.md and Resources.md. Design PM and Development PM check against the shared component registry instead of guessing at names.

Recommended
3

Phase folders

Complex · weekly sprints

Each PM's natural home: its own phase INDEX.md + sprint file, plus reference/ (architecture, components, contracts, decisions). Document PM keeps STATUS.md as the board every other PM checks first.

4

GitHub-native

Team · CI/CD

Issues and Project fields stand in for backlog/spec/sprint files. A passing PR check is Diagnostics PM's complete input; Deployment PM's gate maps to that check passing before merge.

Directions

How to use a Grok PM bot

Same rule for all seven: complete inputs in, gate-passing output out. Here's the loop — starting with the one-time setup.

Setup · once
1

Set up shared context in Cursor

Grok Bots are built to run inside a Cursor project. Before opening any PM, the project needs its shared context in place — Project Scope, Roadmap, Vision, and Strategy — so every bot inherits the same foundation instead of re-deriving it per phase.

2

Assemble complete inputs

Fill in the SevenD file(s) for the phase you're starting — Product.md at Level 1, or the phase's INDEX + sprint file and reference/ docs at Level 3–4. A PM manages the process; it won't invent the backlog or the spec for you.

3

Open the matching PM

Click through to that phase's bot on x.ai. Paste or link your complete input — the approved output of the previous phase, plus any new context for this one.

4

Let it run the phase

The PM asks clarifying questions on any gap, then drives the phase to its canonical SevenD output — backlog, spec, blueprint, sprint plan, test verdict, or deploy plan.

5

Hand off, don't skip

Copy that output into the next phase's complete input and open the next PM. Document PM stays in the loop the whole time, syncing status across every phase.

Enforced automatically

The bots don't skip gates — even if you ask them to

Every PM inherits the same phase gates as the framework. Incomplete input means the bot pushes back and asks for it, instead of guessing.

GateRule the PM enforcesWhy
Discovery → DefinitionDefinition PM won't write a spec without an approved backlog itemPrevents speccing things nobody asked for
Definition → DesignDesign PM won't design without an approved specPrevents building to a moving target
Design → DevelopmentDevelopment PM won't plan a sprint without a completed designPrevents agents from inventing architecture
Diagnostics → DeploymentDeployment PM won't ship without diagnostics passingPrevents shipping broken code
Grok Bots · General availability

Start wherever you are in the loop.

New idea? Open Discovery PM. Have an approved design? Open Development PM. Every bot picks up exactly where the last one left off.

Start with Discovery PM ↗ ← Back to SevenD