Atlas Workflow
- pauloborini/atlas-workflow
atlas-workflow is a plugin marketplace that provides the Atlas Workflow Orchestrator for deterministic PRD-to-plan-to-execution pipelines with cold validation.
About
atlas-workflow is a one-plugin marketplace by Paulo Borini that packages the Atlas Workflow Orchestrator for developers who distrust open-ended agent loops for software delivery. The orchestrator enforces a deterministic, artifact-first path: start from a PRD, derive a plan, execute against that plan, then run a cold validation pass before you accept the result. Skills stay inside a single atlas-* family so context does not fragment across unrelated prompt packs. Local MCP is part of the story, which suits developers who want tools on disk rather than opaque remote chains. Catalog metadata positions the bundle for Claude Code, Cursor, Codex, opencode, and pi cli, making it a multi-phase productivity layer across validate, build, and ship rather than a narrow formatter. It does not replace human code review or production monitoring, but it gives a repeatable ritual when you need agents to prove they followed a plan. Intermediate complexity reflects pipeline discipline and MCP setup. Confidence is moderate because the marketplace exposes one orchestrator without enumerating every atlas-* sub-skill in the ingest payload.
- Single marketplace plugin: atlas-workflow-orchestrator
- Deterministic artifact-oriented pipeline: PRD → plan → execution → cold validation
- Uses one atlas-* skill family for consistent handoffs between steps
- Local MCP support for tooling without cloud-only dependencies
- Documented for Claude Code, Cursor, Codex, opencode, and pi cli style workflows
Atlas Workflow by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
/plugin marketplace add pauloborini/atlas-workflowAdd your badge
Show developers this marketplace is listed on Skillselion. Paste this into your README.
| Repository | pauloborini/atlas-workflow ↗ |
|---|
What it does
Add atlas-workflow when you want a deterministic PRD-to-plan-to-execution pipeline with cold validation and a single atlas-* skill family plus local MCP.
Who is it for?
Best when you want a strict delivery orchestrator across Claude Code, Cursor, Codex, or similar CLIs with local MCP.
Skip if: Casual one-off prompts, teams that do not work from PRDs, or users who need a large multi-plugin studio instead of one orchestrator.
What you get
After installing the marketplace plugin, you can run a structured atlas-* pipeline that ends in cold validation instead of ad hoc completion claims.
- Execution plan derived from PRD
- Executed implementation artifacts per plan step
- Cold validation report or gate output
By the numbers
- 1 plugin in marketplace
- Pipeline stages: PRD → plan → execution → cold validation
Plugins in this marketplace
1 plugin - install individually after you add the marketplace.
Recommended Marketplaces
How it compares
Single orchestrator marketplace with deterministic pipeline semantics, not a broad skill library or MCP server directory entry.
FAQ
Who is Atlas Workflow for?
It is for developers who ship with coding agents and want a PRD-driven, step-locked workflow rather than improvised multi-turn coding.
When should I use Atlas Workflow?
Use it when you have a PRD or equivalent spec and need plan generation, controlled execution, and a final validation pass.
How do I add Atlas Workflow to my agent?
Register Atlas Workflow in your agent’s marketplace or plugin config, install Atlas Workflow-orchestrator, and connect local MCP per the repo README.