devgeco is ugeco's AI-augmented coding workflow for small startups and freelancers. Start a project from the template and you get an agent skill pack, a delivery workflow with a gate at every phase, and a folder discipline that keeps client material out of git. ugeco runs its own builds with it. Work moves one way. Nothing skips a step.
How it works
The workflow is written for the human lead engineer who conducts the agents: every phase gives a when, a model, a copy-paste prompt, what to expect, and the checklist that lets you move on. The model changes as the work changes.
Every file in inbox_00/ is read page by page, inventoried, and turned into a digest where client names, contacts and commercial figures are replaced with stable placeholders. Contradictions become questions for the client before anything is built on them.
The digest becomes a BRD, a PRD and a TRD, then an HLD, LLDs, an OpenAPI contract, a schema and a design spec. Requirements carry stable IDs so every later document can point back at them.
Epics and stories, each linked to the HLD section, LLD section, OpenAPI operation and tables it depends on. A story an agent can pick up cold.
One story at a time: plan, implement, test, evaluate against the planned scope, fill the gaps, audit security, update the docs and the context graph. Nothing is done until the last step is.
The epic is checked against the artifacts that asked for it. Where code and design disagree, that is a finding, not something to paper over.
The skill pack
coding-agent runs the pipeline and invokes the specialists at the right stage rather than reinventing their judgment. The skills are deliberately generic: project facts live in AGENTS.md and the context graph, which is what makes the pack portable between projects.
Ground rules
Never committed. It stages in inbox_00/, gitignored, and only the redacted digest ships.
Thinking on Opus or Fable, typing on Sonnet. The pipeline stops so the human can switch.
Each phase ends with a checklist. A failed gate is re-prompted in the same phase, never carried forward.
Done means which file, and which command proves it. “It should work” is a failed gate.
No project specifics inside the skills. The pack reads AGENTS.md and the context graph at runtime.
Services pinned to exact commits by the root. Commit inside the service first, then bump the pointer.
How a project starts
The template ships the workflow, the skill pack, the inbox and the artifact folders. You add the project's own identity to AGENTS.md, your service repositories under submodules/, and the first client requirement to inbox_00/. Then you start at Phase 0.
$ cd my-project $ $EDITOR AGENTS.md $ cp ~/Downloads/requirement-brief.pdf inbox_00/
Works with Claude Code today; the skills are plain markdown folders, so any agent that can read a SKILL.md can run them. The workflow is licensed by ugeco. Ask for access through the form.
devgeco
It is the workflow we run our own builds with. Ask for access, and we show you how a project starts at Phase 0.
