⚠️ LEGACY ALERT: DevUssy is now the internal cognitive engine for Geoffrussy. This page documents the underlying protocol, but for active development, please use Geoffrussy.
The First Circular Development Pipeline.
DevUssy is a methodology for organizing development work so that plans are reusable, portable, and agent-agnostic. Generate an optimal plan once, execute in a loop. It decouples the "Architect" from the "Builder," allowing for a purely specification-driven development cycle.
Guided Q&A captures goals, constraints, and target stack. It feels like talking to a senior PM.
Pure-Python scoring rubrics rate difficulty and estimate phase count based on feature density.
Frontier Model combines interview + complexity scores. Small projects stay tiny; large ones get microservices.
Rule-based checks + Automated sanity reviewer catch hallucinated services or conflicting requirements.
Generates dynamic phases, explicit tests, and acceptance criteria in standard Markdown.
One-click export for agent handoffs. Generates a 'handoff.md' that summarizes state.
Most development pipelines are linear: Plan → Code → Deploy. DevUssy acknowledges that software is never "done." The Circular Handoff stage feeds the output of the last cycle back into the Context for the next iteration. It preserves the "Mental State" of the project in a file, not in an agent's RAM.
DevUssy is part of the larger Ussyverse ecosystem. While others build "God Agents" that try to do everything, we build specialized protocols. DevUssy is the protocol for planning. Geoffrussy is the protocol for execution. They interface via standard Markdown.
Your specplan.md is a stateless artifact — pure markdown.