gru

Coordinates multi-worker ticket execution with dispatch, verification, and recovery in Codex sessions.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/21StarkCom/stark-skills --skill gru-21starkcom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gru
Source: https://github.com/21StarkCom/stark-skills/tree/main/runtime-overrides/codex/skill/gru
Command: npx skills add https://github.com/21StarkCom/stark-skills --skill gru-21starkcom

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Coordinating multiple AI workers across tickets, dependencies, and merges is error-prone when done manually. Gru acts as an autonomous leader that dispatches Minion workers, verifies their claims, manages integration locks, and recovers from failures without constant operator supervision. ## Core Features & Use Cases - Autonomous worker dispatch: Launch and manage Minion workers through Hermod with concurrency, attempt, and recovery limits. - Dependency-aware coordination: Track durable assignments and dependency readiness in a shared SQLite state store, integrating one change at a time under a merge lock. - Bounded recovery and lifecycle control: Resume interrupted runs, reconnect existing workers, stop engagements cleanly, and escalate concrete blockers with evidence. - Use Case: You have five approved tickets from a gated spec. Run Gru with the objective and ticket list, and it dispatches workers, verifies each PR through the required review gate, merges them in dependency order, and closes tickets only after verified completion. ## Quick Start Ask Gru to start leading work on your approved tickets by running $gru start with your objective and ticket IDs.

Frequently Asked Questions about gru

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I coordinate multiple AI coding workers on tickets?▼

Use Gru's start command with an objective and ticket list to dispatch Minion workers through Hermod. It enforces concurrency limits, verifies worker claims independently, and integrates one change at a time under a merge lock.

How do I resume an interrupted multi-worker run?▼

Run gru resume with the run id to restore leadership from the saved state. Gru reconnects existing worker identities, sends fresh packets with the current leader identity, and preserves pending launches and merges.

Can Gru work with both Claude and Codex workers?▼

Yes, Gru supports both providers through Hermod, using Claude worktrees under .claude/worktrees and Codex worktrees under .worktrees. It never emulates a Codex worker by launching Claude and uses each provider's supported lifecycle paths.

What limits can I set on worker dispatch?▼

You can set --max-workers for simultaneous workers, --max-attempts for total launches per task, and --max-recoveries for reconnecting dead workers. An incoming leader can replace limits only via an operator-authored limits file.

When does Gru escalate instead of acting autonomously?▼

Gru escalates when it needs operator authorization for new tickets, direct publishing, live infrastructure changes, destructive teardown, or credential actions. It presents concrete choices with observed evidence rather than weakening the objective.