steward.foo

Your agents can parallelize. Your judgment cannot.

Stewards turn judgment into narrow reviewers you can reuse. Make one for billing, auth, migrations, or any concern worth watching; it checks the plan before you build and reviews what your agent ships back before you merge.

Start in your coding agent

Good stewards are narrow.

You add them one per concern, wherever something needs to keep working as the code changes.

Billing steward
Checks charges, invoices, plan changes, refunds, and retry behavior before they reach customers.
Auth steward
Reviews sign-in flows, session boundaries, redirects, and public routes before access changes merge.
Migrations steward
Watches schema changes, rollout order, reversibility, and whether old data survives the move.
Release steward
Looks for risky deploy steps, missing rollback notes, and checks that need to pass before shipping.
Dependency steward
Reviews package changes, dependency drift, license surprises, and version bumps that alter runtime behavior.
Billing steward
Checks charges, invoices, plan changes, refunds, and retry behavior before they reach customers.
Auth steward
Reviews sign-in flows, session boundaries, redirects, and public routes before access changes merge.
Migrations steward
Watches schema changes, rollout order, reversibility, and whether old data survives the move.
Release steward
Looks for risky deploy steps, missing rollback notes, and checks that need to pass before shipping.
Dependency steward
Reviews package changes, dependency drift, license surprises, and version bumps that alter runtime behavior.

How a steward works

Before the agent builds

Ask the event reliability steward about a telemetry plan. It spots the part that needs a test before your agent writes the first diff.

After the diff lands

The same steward reads the changed files, raises the concern that still needs you, then clears the check when the agent proves the fix.

A steward.foo GitHub review requesting changes on a pull request

Install where your agents already work

One steward reviews your work wherever your agent runs: first when you plan it, then again before you merge it.

Claude Code

Plugin install, MCP auth, then define the steward from inside the repo.

1. Add the marketplace

/plugin marketplace add contextgraph/claude-code-plugin

2. Install the steward plugin

/plugin install steward

3. Authorize the MCP connection

Sign in to mcp.steward.foo when Claude Code prompts you.

/mcp

4. Define your first steward

Run this from inside your repo. The plugin walks the codebase and proposes a rubric for your approval.

/steward:define-steward
Other MCP clients →
steward.foo - Your agents can parallelize. Your judgment cannot.