// the find
ruvnet/rUv-dev
Ai power Dev using the rUv approach
create-sparc is a CLI scaffold tool for setting up Roo Code (a Cline fork) with the SPARC methodology — a structured five-phase development process delegated across specialized AI modes. It generates config files, mode definitions, and MCP server wiring so you can use Claude or GPT-4 as domain-specific assistants within VS Code. The target audience is developers who want to organize AI-assisted work into defined phases rather than one giant prompt.
The mode isolation idea is genuinely useful — having separate AI contexts for spec writing, architecture, TDD, and security review prevents the sprawl you get when you dump everything into a single conversation. The MCP wizard with security auditing (env-var detection, least-privilege scoping, config integrity hashing) is a real feature, not just docs. The test suite is substantial for a scaffolding tool — unit and integration tests covering the wizard, registry client, file manager, and CLI commands. The clinerules-bank pattern for per-client and per-framework rule overrides is practical for agency or consultancy use.
The README is almost entirely marketing copy — there is no honest description of what files actually get generated or what the modes can and cannot do autonomously. The hard dependency on Roo Code extension means you're locked to a VS Code fork that may diverge from or lag behind upstream Cline; this risk is not mentioned anywhere. The MCP 'registry' is a mock with five hardcoded entries (supabase, openai, github, aws, firebase) — the docs imply a real discovery service exists, which it does not. The SPARC phases sound structured but the actual enforcement is just markdown files in `.roo/` directories; there's nothing preventing an agent from ignoring the phase boundaries entirely.