run-looplisted

# /run-loop — Single-command pipeline (create → plan → work) **Type:** pipeline orchestrator / entry point ## Purpose `/run-loop` is the single-command entry point for the full stagecrew pipeline. It accepts a task description and chains the three main phases internally: ``` /run-loop "<task>" → /create-issue (one or more fully-specified issues) → /plan-issues (wave assignment — collision-safe grouping) → [human confirms] (mandatory review gate) → /work-issue (parallel loops per wave, wave by wave) ``` This reduces the common case from three separate commands to **one command + one confirmation**. `/close-out` is intentionally **not** part of `run-loop`. It is a separate decision point after all PRs are ready for review — a deliberate human checkpoint before merging. ### When to use | Situation | Use | |-----------|-----| | You have a task idea and want to go from idea to running loops in one step | `/run-loop "<idea>"` | | You want to drive an existing issue through the loop | `/work-issue <num>` | | You want to plan existing issues before running them | `/plan-issues` | | You want to merge completed PRs in wave order | `/close-out` | ## Invocation variants ``` /run-loop "add user authentication with JWT refresh" /run-loop --repo owner/slug "add user authentication" /run-loop --type=research "benchmark ollama tool-use latency" /run-loop --issues 42,44,51 # plan and work existing issues (skip create-issue) /run-loop # → a