Skip to content
Development
Command

/summon

Summon the egregore to autonomously process work items through the full development lifecycle. Runs indefinitely by default until dismissed.

From plugin
claude-night-market
337162 skills59 agents162 commands1 MCP
Install
> /plugin marketplace add athola/claude-night-market

How it fires

How this command gets triggered: by you, by Claude, or both.

  • Fires itselfClaude auto-loads it when your prompt matches the work.
  • You can call itInvoke it directly when you want it.
  • Slash command/summon

Context preview

What this command does when you run it.

Summon the egregore to autonomously process work items through the full development lifecycle. Runs indefinitely by default until dismissed.

Command definition

summon.md
name: summon
description: >-
  Summon the egregore to autonomously process work items
  through the full development lifecycle. Runs indefinitely
  by default until dismissed.
usage: >-
  /egregore:summon "<prompt>" [--window 5h|7d]
  [--bounded] [--issues N,N] [--issues-label LABEL]

summon

Launch the egregore to autonomously process work items through planning, implementation, testing, and PR creation. By default the egregore runs indefinitely, scanning for new work after completing its current manifest. Use `/egregore:dismiss` to stop it.

Invoke `Skill(egregore:summon)`, which carries the orchestration loop, the manifest mode, the pipeline mapping, the context-overflow and token-budget protocols, the progress monitoring and the failure handling.

When To Use

  • You have one or more issues or tasks to process

without manual intervention.

  • You want to run a multi-hour or multi-day development

pipeline overnight or over a weekend.

  • You want the agent to self-recover from crashes and

rate limits via the watchdog.

  • You want continuous autonomous processing that finds

and handles new work as it appears.

When NOT To Use

  • For quick, single-file changes. Just do them directly.
  • When you need tight human-in-the-loop review at every

step. Use normal Claude sessions instead.

  • On repositories you do not trust the agent to modify.

Egregore creates branches and opens PRs autonomously.

Usage

From a prompt:

/egregore:summon "Refactor the auth module to use JWT"

From GitHub issues by number:

/egregore:summon --issues 42,43,44

From GitHub issues by label:

/egregore:summon --issues-label "egregore"

Bounded mode (stops when time window expires):

/egregore:summon --bounded --window 2d --issues 42,43,44

Options

| Option | Default | Description | |------------------|---------|------------------------------| | `<prompt>` | none | Free-text work description | | `--window` | `5h` | Time window (e.g. 5h, 7d) | | `--bounded` | false | Stop when time window expires| | `--issues` | none | Comma-separated issue numbers| | `--issues-label` | none | GitHub label to pull issues |

The egregore runs indefinitely by default. Pass `--bounded` to set a hard time limit. In both modes, the egregore scans for new work after completing all current items. The only difference is that bounded mode exits when the time window expires.

Stopping the Egregore

The egregore does not stop on its own. To shut it down:

/egregore:dismiss

This pauses all active work items, saves state, and removes the pidfile. You can resume later with another `/egregore:summon`.

See Also

  • `/egregore:status` to check progress.
  • `/egregore:dismiss` to stop gracefully.
  • `/egregore:install-watchdog` to enable auto-relaunch.
Read more
Ships withclaude-night-market

A plugin marketplace for Claude Code. Install only the plugins you need to run git workflows, code review, spec-driven development, and autonomous agents from inside your Claude Code session.

Get the whole plugin

Other commands on claude-night-market.