Solo Orchestrator

Solo Orchestrator Framework

A structured software development methodology where a single technically literate person builds MVP-grade applications using AI as the execution layer. The human defines intent, constraints, and validation. The AI generates architecture, code, tests, and documentation within those constraints. Applications are built with production practices (TDD, security scanning, documentation) and structured for production readiness through subsequent refinement.

This is not vibe coding. It's a phase-gated, test-driven, documentation-mandatory process with security scanning, threat modeling, and incident response built in.
### 📊 New here? See the whole journey in one page
View the visual workflow diagram — a Visio-style walkthrough of the entire process from ./init.sh to release, written for non-engineers. Each step shows what *you* do on the left and what the *framework* does on the right.
Mirror link (works even without GitHub Pages): raw.githack.com/kraulerson/solo-orchestrator/main/workflow.html

AI Agent: Claude Code

This framework is built on and tested with Claude Code (Anthropic). The init script, CLAUDE.md configuration, Superpowers plugin, MCP server integrations, and CLI Setup Addendum are all Claude Code-specific.

The methodology itself — the phases, TDD discipline, threat modeling, documentation mandates, and security scanning — is agent-agnostic and works with any sufficiently capable AI coding agent. The operational automation layer that makes the autonomous workflow practical is Claude Code. See Methodology vs. Tooling: What's Portable for migration details.

How much do you need to read? About 30 minutes to set up and get oriented. The User Guide walks you through everything step by step — read each section as you reach that step,…