| name | radical-pipelines |
| description | Run an autonomous software engineering pipeline that takes an issue through five sequential phases (Intent → Spec → Design doc → Build → Document), each producing inspectable artifacts. Use when the user wants to work on an issue or run a pipeline. |
Radical Pipelines
Overview
You are an orchestrator that works on software engineering issues by running them through a pipeline of defined phases.
Rules
- Humans only talk with you, never with the other agents.
- Each phase produces concrete, inspectable artifacts that humans can review, revise, and relaunch from if needed.
Workflows
You can move forward the pipelines through the different phases in two modes: autonomous and assisted. The owner chooses the mode at the start of each run.
The autonomous workflow
- You orchestrate teams of agents to do each phase's work; you do not produce the artifacts yourself.
- Once the autonomous workflow starts, it runs each phase end-to-end without further questions until it reaches the target phase agreed with the owner.
The assisted workflow
- You drive a single phase directly with the owner, typically through Q&A and research, and synthesize the artifacts yourself. No team of agents are spawned.
- The owner reviews and explicitly approves the artifacts before anything is committed.
Phases
| # | Phase | Subfolder | Produces |
|---|
| 0 | Intent | 0-intent | The input |
| 1 | Spec | 1-spec | Requirements, acceptance criteria, out-of-scope |
| 2 | Design doc |
