Coordinate agents through requirements, design, implementation and documentation, with reviewable artifacts at each phase.
Radical Pipelines is a software engineering orchestrator for Claude Code and OpenCode. It takes an issue through specifications, technical design, implementation and documentation, assigning work to producers, workers and reviewers. Requirements, plans, task reports and review evidence remain in the working tree so your team can inspect progress before the final pull request.
In Claude Code, ask Claude to run Radical Pipelines; it can also load the skill when relevant. In OpenCode, the model can discover and load the skill. Once activated, the orchestrator dispatches the agent profiles needed to advance the pipeline. You choose the target phase and autonomous or assisted workflow during triage; assisted work is available for specifications and design documents.
Give the orchestrator an issue and choose how far to take it. The pipeline develops testable requirements and a technical design, then plans implementation tasks, assigns workers and sends the resulting code through review against the plan and acceptance criteria.
For specifications or design documents with competing approaches, configure named lanes with their own briefs and models. Each lane produces and reviews a candidate; a consolidation producer combines the candidates into a canonical artifact for final adversarial review.
Bring a CI failure, pull-request feedback or a correction to an existing pipeline. Later input targets the relevant phase, where agents investigate and revise the affected artifacts; changes to those artifacts drive downstream work.
Use the Document phase to plan and write internal and external documentation from the shipped code, design and specification. Documentation reviewers check the result against those inputs and look for public behavior that still needs coverage.
The skill coordinates the work; the agent profiles carry out production, review and supporting tasks. Install the plugin in Claude Code or OpenCode, then ask the agent to run Radical Pipelines. The orchestrator dispatches profiles as needed. Before project work begins, it loads conventions from .rp.md; if required conventions are missing, interactive setup proposes them for your approval. See the project configuration guide.
Orchestrates issue work, pipeline corrections and status inspection across reviewed engineering phases.
Turns the specification and design into implementation tasks and resolves findings against the plan.
Checks implementation tasks and assumptions against the specification, design and codebase.
Checks the code against its plan, design and specification, running tests and acceptance checks.
Develops architecture and technical decisions from the specification, resolving findings or consolidating lane candidates.
Checks technical decisions and their evidence against the specification and codebase.
Plans internal and external documentation tasks from the shipped code, design and specification.
Checks documentation tasks and file coverage against the shipped code, design and specification.
Checks documentation against the plan and shipped behavior, looking for undocumented public surfaces.
Completes one documentation task and records the changes, checks and supporting evidence.
Answers a bounded question, produces an observation or makes a change for another agent.
Develops testable requirements from the intent, resolving findings or consolidating lane candidates.
Checks requirements, exclusions and claims against the intent and recorded research.
Completes one implementation task, including its code, tests and task report.
Install the whole plugin for your AI tool to get the orchestration skill and agent profiles together.
The Automattic marketplace currently lists Radical Pipelines. Add the marketplace, then install its plugin in a Claude Code session.
Where to get the marketplace
Add the marketplace from GitHub.
/plugin marketplace add Automattic/radical-pipelinesUse a checkout of the Radical Pipelines repository at ./radical-pipelines, relative to the session's working directory. Add that directory as the marketplace source.
/plugin marketplace add ./radical-pipelinesOpen the plugin's installation panel, choose a user, project or local scope, and complete installation.
/plugin install radical-pipelines@automatticCheck the installation summary. If it says the plugin is active now, continue. If it requests a reload, closing the panel runs the reload; follow any remaining prompt before checking availability.
Open the plugin manager and check the Installed tab for radical-pipelines. Type a slash in the session and look for its namespaced skill to confirm it is available.
/pluginSources: Radical Pipelines installation and Claude Code plugin installation and activation.
For active plugin development, Claude Code can read the plugin directly from a working checkout. This bypasses the marketplace cache and reads the working tree on each launch.
Place a checkout of the Radical Pipelines repository at ./radical-pipelines, relative to your shell's working directory, then launch Claude Code with that directory.
claude --plugin-dir ./radical-pipelinesIn the launched Claude Code session, type a slash and look for the Radical Pipelines skill under its plugin name. Its presence confirms the skill is available.
Sources: local development instructions and Claude Code availability checks.
Use stable OpenCode v2. The following procedure comes from Radical Pipelines' installation guide.
Add github:Automattic/radical-pipelines to the plugins array in your global ~/.config/opencode/opencode.json. Keep any existing plugin entries.
{
"$schema": "https://opencode.ai/config.json",
"plugins": ["github:Automattic/radical-pipelines"]
}Restart the OpenCode service. Radical Pipelines completes setup before OpenCode scans agents, making the skill and profiles available when the service returns.
opencode service restartQuery the running service's plugins and check for an ID beginning with radical-pipelines@, followed by the installed version.
opencode api GET /api/pluginSources: Radical Pipelines' OpenCode installation and version check and OpenCode v2 plugin configuration.