minion

Implements assigned coding tasks in isolated worktrees and reports progress to a coordinating leader.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Coordinating parallel AI coding workers on shared repositories is error-prone: workers edit the wrong checkout, report under stale tokens, or merge without verification. This Skill turns a Codex session into a disciplined worker that executes one authorized assignment, reports evidence, and waits for integration approval. ## Core Features & Use Cases - Assignment intake and validation: Reads a Gru assignment packet, verifies the worktree, ticket, token, and done-when criteria, and acknowledges with an exact completion contract before starting work. - Structured progress reporting: Sends ack, progress, blocked, ready, and complete reports over Hermod peer messaging with the engagement, task, and token identity. - Verified delivery workflow: Runs required checks and code review, posts findings, and waits for an integration grant before merging and closing the ticket. - Use Case: A team lead dispatches three parallel feature tasks to separate Codex sessions; each Minion works in its own worktree, rebases onto the moving base, and reports a reviewed draft PR for the coordinator to merge. ## Quick Start Invoke the minion skill with a Gru assignment packet containing the engagement, task, token, worktree, objective, and done-when criteria to begin the assigned implementation.

Frequently Asked Questions about minion

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

FAQPage Schema
How do I run parallel AI coding agents on one repository?▼

Assign each agent an isolated git worktree and a task packet defining objective, files, and done-when criteria. Each worker implements, tests, and opens a draft PR independently, while a coordinator handles dependencies, verification, and merge order.

How does the minion skill receive its task assignment?▼

It reads a Gru assignment packet from the current request or a Hermod message containing the engagement, task, token, ticket, worktree, objective, files, and done-when criteria. A missing behavioral contract or operating limit is treated as an intake blocker.

Can a minion merge its own pull request?▼

Merging a reviewed PR needs no operator approval since the review gate is the gate, but the worker must first receive Gru's assignment-specific integration grant identifying its token and the current base SHA. Publishing, infrastructure, and destructive actions always require operator authorization.

What happens if the assignment packet names the wrong worktree?▼

The worker starts no work and sends its leader a plain Hermod note naming its actual checkout. Gru then re-briefs with a later packet after adopting the real worktree, and the worker waits for that packet before proceeding.

How does the minion verify a re-brief or leadership transfer message?▼

It checks the Hermod ledger record via hermod msg status, confirming the state is not failed, the destination matches its own session, the sender matches the named leader, and the timestamp is newer than the current packet. The delivered text header alone is never trusted.

When should a worker close its ticket after merging?▼

The worker closes the ticket itself once it independently confirms the completion milestone, such as the squash-merge or the end of the release chain. It moves the ticket to done with alfred task move, since Gru's complete step only accepts done or Closed states.