MirevoxGitHub (opens in a new tab)

Module 03 · Delivery stages

runnable

Stage Gate

Make the path from appointment to build visible.

View on GitHub (opens in a new tab)

Runnable v0.1 slice available on GitHub — architecture and scope below.

Problem

AI-assisted projects can jump from an appointment straight into generated code. The missing middle—prerequisites, requirements, decisions, and clear advance criteria—is usually spread across documents and understood by only a few people.

Where it sits

Sits over an existing delivery harness and makes its stages visible. It is meant to guide work from pre-requirements through requirements, architecture, build, and specification without forcing one development framework.

Think of it as the difference between booking the appointment and doing the work. A project first checks pre-requirements, then moves through requirements and architecture before build or specification work is allowed to advance—on top of a harness you already have, for example VS Code plus a side agent.

The proposed flow connects high-level requirements to functional and non-functional requirements, ADRs, and implementation specs. SpecKit or OpenSpec can plug in where useful, but neither is required. A non-technical owner should be able to follow the same flow and answer “when do I advance?” without living in a terminal.

How it fits

Stage Gate and Shadow Versioning share the same project ID: the gate explains where the work is, while versioning keeps the related artifacts tied together. Context Engine can supply indexed project material without turning the gate into another repository browser.

Capabilities