Atlas Workflow
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.
Overview
atlas-workflow is a plugin marketplace for the Build phase that provides the Atlas Workflow Orchestrator for deterministic PRD-to-plan-to-execution pipelines with cold validation.
What is this marketplace?
- 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
- 1 plugin in marketplace
- Pipeline stages: PRD → plan → execution → cold validation
What problem does it solve?
Agent-assisted builds often drift because there is no fixed artifact chain from PRD through plan, execution, and objective validation.
Who is it for?
Solo builders who 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 do I get? / Deliverables
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
Plugins in this marketplace
1 plugin — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Orchestrated delivery starts in Build where PRDs become executable plans, while the same marketplace spans validation and ship gates. The orchestrator is plan-centric artifact flow (PRD → plan → execution), which maps to pm as the primary shelf before testing-style validation.
How it compares
Single orchestrator marketplace with deterministic pipeline semantics, not a broad skill library or MCP server directory entry.
Common Questions / 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.