speckroo GitHub →
multi-tool·MIT·zero-config

Spec-driven dev with five agents, and you in the loop.

speckroo is a reusable, project-agnostic development framework. A product manager, designer, monetization strategist, engineer, and reviewer hand off through reviewable Markdown artifacts — with a fully autonomous loop between your two approval checkpoints.

Runs in

01Install

Works in Claude Code, OpenCode, Copilot CLI, Cursor, Windsurf, Codex — and any AGENTS.md tool. One canonical source, projected into each.

Claude Code — native plugin:

>/plugin marketplace add phoinixi/speckroo
>/plugin install speckroo@speckroo

Every other tool — one command in your project:

$npx github:phoinixi/speckroo setup opencode

Swap opencode for copilot, cursor, windsurf, or codex. Then run init-framework to scaffold your project, add ideas to .framework/queue.md, and run loop.

02The workflow

Three steps. Two checkpoints. Autonomous loop between them.

/shape <idea>
→ spec.md + design.md
/plan
→ plan.md + tasks.md
/monetize
→ monetization.md · optional
/build
→ code, all tasks, one summary
/review
→ review.md · auto-chained

After each phase the agent asks "Approve and continue?" — a "yes" flips Status: draft → approved and starts the next phase. /review chains automatically after build. The /approve command is still available as an explicit fallback.

03Loop mode

Add ideas to a queue. Let the loop do the rest — stopping only when a human decision is needed.

>/loop

Add ideas to .framework/queue.md — one checkbox per feature. Run /loop and it picks the first unchecked item, runs shape (PM + designer), then stops:

"Approve shape and continue to /plan? (yes / revise / stop)"

Say yes → engineer plans → stops again → say yes → engineer builds everything → code reviewer writes review.md → feature box checked → loop picks the next idea. Two decisions from you per feature.

/loop check shows all queued features and their current phase without running anything. A project-level skill.md accumulates conventions after each build — every agent reads it, so the loop gets smarter over time.

04The five agents

One owner per phase. Each writes only its own artifact.

Product Manager

Requirements, scope, priorities, success metrics.

spec.md

Product Designer

UX, user flows, design specs.

design.md

Monetization Strategist

Pricing, business model, revenue. Optional.

monetization.md

Software Engineer

Architecture, plan, task breakdown, code.

plan.md · tasks.md · code

Code Reviewer

Adversarial verification of the finished build. Finds drift, gaps, and bugs.

review.md

05Why five agents, not one?

A single mega-agent loses the thread across a long build. speckroo's agents hand off through files in .framework/, not chat history — so context persists across phases, each role stays tight and accountable, and you have a reviewable paper trail at every checkpoint. This very site was built by running speckroo on itself; the artifacts live in .framework/speckroo-docs/.