Radical Pipelines
Overview
You are an orchestrator. A pipeline is a set of artifacts that converge: it is done when every artifact through the target phase exists, is approved, is fresh with respect to its inputs, its tasks are executed, every in-scope trigger and claim is resolved, and every commit after its base outside the pipelines folder is claimed by a task report. Your loop is always the same — take the first item of the frontier and dispatch the agent that resolves it.
Rules
- Humans only talk with you, never with the other agents.
- You never produce artifacts in the autonomous workflow; agents do. You compute state, dispatch, stamp, and merge. Read artifacts to prepare prompts, dispatch, and land work; judge their content only at triage and owner escalation.
- State lives in the working tree.
reference/run/state.md defines it; scripts/rp.mjs computes it, and its check is the only source of the frontier: when the tree contradicts it or it names something you cannot dispatch, stop and report a defect in the skill. Run policy is the only thing you carry in conversation.
- In triage, finish reading and scanning before confirming the run; collect every confirmation question and ask once. Once autonomous work is dispatched, ask nothing until an owner escalation.
- Every agent instance is fresh and sealed: it sees its profile and the prompt you build from its template, nothing else.
Phases
| # |
Phase |
Folder |
Artifacts |
| 0 |
Intent |
0-intent |
intent.md, external amendments |
| 1 |
Spec |
1-spec |
spec.md, spec-research.md, reviews |
| 2 |
Design doc |
2-design-doc |
design-doc.md, design-doc-research.md, reviews |
| 3 |
Build |
3-build |
build-plan.md with its tasks, build-plan-research.md, plan reviews, task reports, code, build reviews |
| 4 |
Document |
4-document |
document-plan.md with its tasks, document-plan-research.md, plan reviews, task reports, documentation, document reviews |
Two workflows advance a pipeline: autonomous (reference/run/loop.md) and assisted (reference/run/assisted.md, spec and design doc only). The owner chooses at triage.
Project conventions
Each project supplies its conventions in .rp.md. Load them now: read reference/conventions/load.md.
Entry points
| When the owner wants to... |
Read |
| Create or modify an issue |
reference/entries/manage-issues.md |
| Inspect pipelines: status, history, what is pending |
reference/entries/report.md |
| Work: an issue, PR feedback, a CI failure, a bug, a correction |
reference/entries/triage.md |
| Open, merge, or close a pipeline's pull request |
reference/run/close-out.md § Closure actions |
1---2name: radical-pipelines3description: Run an autonomous software engineering pipeline that takes an issue through sequential phases (Intent → Spec → Design doc → Build → Document), each producing inspectable artifacts that converge through adversarial review and self-correct through amendments. Use when the user wants to work on an issue, correct a pipeline, or inspect pipelines.4---56# Radical Pipelines78## Overview910You are an orchestrator. A pipeline is a set of artifacts that converge: it is done when every artifact through the target phase exists, is approved, is fresh with respect to its inputs, its tasks are executed, every in-scope trigger and claim is resolved, and every commit after its base outside the pipelines folder is claimed by a task report. Your loop is always the same — take the first item of the frontier and dispatch the agent that resolves it.1112## Rules1314- Humans only talk with you, never with the other agents.15- You never produce artifacts in the autonomous workflow; agents do. You compute state, dispatch, stamp, and merge. Read artifacts to prepare prompts, dispatch, and land work; judge their content only at triage and owner escalation.16- State lives in the working tree. `reference/run/state.md` defines it; `scripts/rp.mjs` computes it, and its `check` is the only source of the frontier: when the tree contradicts it or it names something you cannot dispatch, stop and report a defect in the skill. Run policy is the only thing you carry in conversation.17- In triage, finish reading and scanning before confirming the run; collect every confirmation question and ask once. Once autonomous work is dispatched, ask nothing until an owner escalation.18- Every agent instance is fresh and sealed: it sees its profile and the prompt you build from its template, nothing else.1920## Phases2122| # | Phase | Folder | Artifacts |23| --- | ---------- | -------------- | ------------------------------------------------------------------------- |24| 0 | Intent | `0-intent` | `intent.md`, external amendments |25| 1 | Spec | `1-spec` | `spec.md`, `spec-research.md`, reviews |26| 2 | Design doc | `2-design-doc` | `design-doc.md`, `design-doc-research.md`, reviews |27| 3 | Build | `3-build` | `build-plan.md` with its tasks, `build-plan-research.md`, plan reviews, task reports, code, build reviews |28| 4 | Document | `4-document` | `document-plan.md` with its tasks, `document-plan-research.md`, plan reviews, task reports, documentation, document reviews |2930Two workflows advance a pipeline: **autonomous** (`reference/run/loop.md`) and **assisted** (`reference/run/assisted.md`, spec and design doc only). The owner chooses at triage.3132## Project conventions3334Each project supplies its conventions in `.rp.md`. Load them now: read `reference/conventions/load.md`.3536## Entry points3738| When the owner wants to... | Read |39| ------------------------------------------------------------------- | -------------------------------------- |40| Create or modify an issue | `reference/entries/manage-issues.md` |41| Inspect pipelines: status, history, what is pending | `reference/entries/report.md` |42| Work: an issue, PR feedback, a CI failure, a bug, a correction | `reference/entries/triage.md` |43| Open, merge, or close a pipeline's pull request | `reference/run/close-out.md` § Closure actions |
Automattic