Endgame — Project Generator
Describe a tool in plain English; get a governed spec, scaffold, repo and task board — in minutes.
Live in production
- minutes — From a plain-English brief to a running, governed scaffold — not days of setup
- 100% — Of generated projects born under the Geidi Framework — governance isn't an afterthought
- 3 — A spec, a repo and a Plane board — created together and wired up, not by hand
The first day of a project is mostly plumbing
And the plumbing is where the standard quietly gets skipped.
Every new project restarts the same setup — repo, board, structure — before any real work begins. The governance standard lives in a document, so whether a new project actually follows it is anyone’s guess. Two engineers scaffolding the same kind of service produce two different shapes. And by the time the project is tracked and owned, it has often been running unlabelled for a week.
What it produces
- A real project, not a zip file. A specification, a runnable scaffold, the repository and a task board with work items already created — so the team starts in the project rather than setting one up.
- The house rules in the code. Every generation runs under our framework: domain-driven design, telemetry from the first commit, business-logic governance. The standard is present in the code, not only in a document someone might read.
- Registered the moment it exists. On creation the project records its identity — owner, lifecycle, where it runs — so nothing runs unaccounted for.
- A shared vocabulary, seeded. The project’s glossary flows into the estate glossary as its own tenant, so its language is defined once and readable by people and by AI.
- A gate, not a guideline. Governance is enforced in the build. A generation that would violate the framework is caught before it ships.
How it goes
You write the problem statement the way you would explain it to a colleague — no templates, no boilerplate to fill in.
That description becomes a compliant specification: the framework applied to your problem rather than pasted in by hand. The scaffold, the repository and the board are created together. The project then registers itself and seeds its vocabulary, with no manual paperwork and no forgotten labelling.
From there it is an ordinary project, except the standard is already enforced and a build gate keeps it that way.
Why this rather than a template
Templates decay. The copy-paste step — pasting conventions into a tool, or a document into an AI assistant — is exactly where conventions drift, and it happens once per project, invisibly.
Generating the project from the standard removes that step. Owned, tracked and observable stop being intentions and become properties of how the project was born.
Where it fits
- Engineering leads who want every new project to start governed, not merely intended to be.
- Teams re-scaffolding the same plumbing before any real work begins.
- Estates standardising how projects are born across many services and people.
- Anyone tired of pasting their conventions into an AI tool on every new build.
Bring a brief
The demonstration is a plain-English description of something you actually want built, turned into a spec, a scaffold, a repository and a board — with the standard already in it.