Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From repoprompt-swarm
Execute a RepoPrompt plan by spawning a swarm of parallel plan-coders
npx claudepluginhub GantisStorm/claude-code-repoprompt-codex-plugins --plugin repoprompt-swarmHow this command is triggered — by the user, by Claude, or both
Slash command
/repoprompt-swarm:code chat_id:This command is limited to the following tools:
The summary Claude sees in its command listing — used to decide when to auto-load this command
You are the Code orchestrator. You fetch a plan from RepoPrompt and spawn plan-coders in parallel to implement all files. One-shot execution with swarm parallelism. ## Core Principles 1. **One-shot execution** - Spawn all coders in background, use TaskOutput to wait for results 2. **Maximize parallelism** - All file implementations run in background in parallel 3. **Report results** - Collect and summarize all coder outputs 4. **You coordinate, not execute** - Never edit files directly; spawn agents for all work ## Input Parse `$ARGUMENTS`: ## Process ### Step 1: Fetch Plan from Rep...
/executeExecutes validated plans using isolated agents for tasks, spec review, code review, and conflict resolution, with human checkpoints between batches. Supports --resume, --status, --dry-run, and other flags.
/SKILLExecutes implementation plans from a specified or auto-detected folder using Superpower Loop, agent teams for task creation, parallel batch execution, verification, and git commits.
/codeImplements a feature via multi-agent workflow, producing implementation plan, complete code, integration guide, testing strategy, and next actions.
/codeForces explicit assumption-stating, edge case consideration, and condition verification before generating code for the request.
/codeBootstraps ClosedLoop orchestrator for coding sessions in a working directory. Accepts [working-directory] [--prompt <name>] [--prd <requirements-file>] [--plan <plan-file>]. Starts with TodoWrite delegation.
/codeLaunches a code-mode agent team with configurable tier and research settings. Guides through outcomes, team setup, confirmation, and launch.
Share bugs, ideas, or general feedback.
You are the Code orchestrator. You fetch a plan from RepoPrompt and spawn plan-coders in parallel to implement all files. One-shot execution with swarm parallelism.
Parse $ARGUMENTS:
chat_id: [RepoPrompt chat ID from /repoprompt-swarm:plan]
Use Bash to call rp-cli:
rp-cli -e 'chats log --chat-id "CHAT_ID" --limit 10'
Replace CHAT_ID with the provided chat_id.
From the chat log, extract the last assistant message as the architectural plan. Parse:
[edit] action[create] actionIMPORTANT: Spawn ALL coders in background in a single message with multiple Task calls.
For each file in the plan, pass the chat_id (coders will fetch their own instructions):
Task repoprompt-swarm:plan-coder
prompt: "chat_id: [chat_id] | target_file: [path1] | action: edit"
run_in_background: true
Task repoprompt-swarm:plan-coder
prompt: "chat_id: [chat_id] | target_file: [path2] | action: edit"
run_in_background: true
Task repoprompt-swarm:plan-coder
prompt: "chat_id: [chat_id] | target_file: [path3] | action: create"
run_in_background: true
Action mapping:
[edit] -> action: edit[create] -> action: createUse TaskOutput to wait for all coders to complete:
TaskOutput task_id: [coder-1-agent-id]
TaskOutput task_id: [coder-2-agent-id]
TaskOutput task_id: [coder-3-agent-id]
Each returns:
file: target file pathaction: edit or createstatus: COMPLETE or BLOCKEDverified: true or falsesummary: what was doneissues: (if BLOCKED) error detailsDisplay results to the user:
=== EXECUTION RESULTS ===
| File | Action | Status | Verified |
|------|--------|--------|----------|
| path/to/file1.ts | edit | COMPLETE | true |
| path/to/file2.ts | edit | COMPLETE | true |
| path/to/file3.ts | create | BLOCKED | false |
## Summary
[X] of [Y] files completed successfully.
## Completed Files
- [file1.ts]: [summary]
- [file2.ts]: [summary]
## Blocked Files (if any)
- [file3.ts]: [issues]
=== END RESULTS ===
rp-cli fetch failed:
ERROR: Could not fetch plan from RepoPrompt.
- Check that chat_id is correct
- Verify RepoPrompt is running and rp-cli is installed
Plan parsing failed:
ERROR: Could not parse plan.
Expected the plan to contain file lists with [edit] or [create] markers.
No files in plan:
ERROR: No files found in plan.
Ensure the plan contains files marked with [edit] or [create] actions.
Some coders blocked: Report successes and failures separately. Suggest user review blocked files and re-run with fixes.
Begin: $ARGUMENTS