THE ORIGIN: DevUssy is the planning methodology that helped shape Geoffrussy's execution engine and much of the broader Ussyverse workflow logic.

DEVUSSY

The Circular Development Pipeline.

DevUssy is a methodology and toolkit for generating development plans that are reusable, portable, and agent-agnostic. Run an adaptive interview, analyze complexity, generate a plan, hand it off to any AI agent or human developer. The plan is a Markdown artifact — no database, no vendor lock-in, no runtime state.

View on GitHubOpen Manuals

Built With

Python 3.9+Next.jsTypeScriptServer-Sent EventsMarkdownMIT License

Profile

MD
Plaintext Output
7
Pipeline Stages
ANY
Agent Handoff

The Problem

  • xContext Loss: Every new agent session starts from scratch, burning tokens to re-understand the project.
  • xDrift: Handoffs between humans and agents cause the project to slowly diverge from the original intent.
  • xBrittle Plans: Prose documents are hard to update and impossible to validate programmatically.

The DevUssy Way

  • >Reusable: One plan works across humans, frontier models, and open-source models. Generate once, execute anywhere.
  • >Portable: Export as plain Markdown. No database, no runtime dependencies, no vendor lock-in.
  • >Agent-Agnostic: Any coding agent — Claude, GPT, Llama, a human — can pick up a DevUssy plan and execute it.

Adaptive Architecture Pipeline

STAGE 01

Interview

Guided Q&A captures goals, constraints, target stack, and edge cases. Adapts questions based on your answers.

STAGE 02

Complexity Analyzer

Python-based scoring rubrics rate difficulty and estimate phase count based on feature density and technical scope.

STAGE 03

Adaptive Design

Frontier models combine interview data with complexity scores. Small projects stay minimal; large ones get detailed architecture.

STAGE 04

Design Validation

Rule-based checks plus automated review catch conflicting requirements or hallucinated components before planning begins.

STAGE 05

SpecPlan Generation

Generates dynamic phases with explicit tests and acceptance criteria in standard Markdown. Streamed live via Server-Sent Events.

STAGE 06

Circular Handoff

Exports state for agent handoffs. The output of the last cycle feeds back as context for the next iteration.

Why "Circular"?

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. Project state is preserved in files, not in an agent's memory.

DevUssy + Geoffrussy

DevUssy can be used standalone as a Python CLI (python -m src.cli interactive), or through Geoffrussy where it powers the planning engine. The methodology is the same either way — DevUssy handles the thinking (interview, complexity, design, validation, plan generation) while Geoffrussy adds the doing (file I/O, git, terminal, code execution).

Current Status

DevUssy remains the cleanest expression of the planning side of the Ussyverse: interview, complexity analysis, design shaping, and portable Markdown output. It is still evolving, but the core value is stable: plans that survive handoffs instead of dying with the session that created them.

Try the pipeline yourself

git clone https://github.com/mojomast/devussy.git
cd devussy && pip install -e .
python -m src.cli interactive
View on GitHub