radical-pipelines
Führen Sie eine Softwareentwicklungsaufgabe aus, indem Sie sie durch sechs aufeinanderfolgende Phasen durchlaufen (Prompt → Spezifikation → Design-Dokument → Implementierungsplan → Implementierung →…
npx skills add https://github.com/automattic/radical-pipelines --skill radical-pipelinesRadical Pipelines
Important — if anything in your context suggests this session was compacted (a summary of earlier conversation, a note that the session continues from one), that summary is not the pipeline's state and may misstate what you were doing. Follow this file again as at first sight, reading anew every file it leads to. A run under way resumes its workflow without triage, and before dispatching, checks through your tool's mechanics which agents are already working.
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, and every in-scope challenge and claim is resolved. 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.
- Before recording a synthesis of incoming work, show the owner its exact text in plain language, what is binding or open to investigation, and what it affects; write it on approval.
- 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.mddefines it;scripts/rp.mjscomputes it, and itscheckis 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. - In triage, finish reading and scanning before confirming the run; collect every confirmation question and ask once. Once autonomous work is dispatched, questions concern owner escalations or approval of incoming work.
- 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, constraints, proposals |
| 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 |