Greenfield project from a specification

Case study in full

Synthetic example — illustrative magnitudes, not a measurement.

Stack profile: typescript-react-vite-spa · Data origin: Synthetic example, not a reference run. · Measurement period: —

A new project starts without existing code, but with a written requirement. From that requirement a structured specification emerges first, then a repository scaffold, and finally a set of workable epics.

Out of scope — not automated: Not automated: the substantive direction of the specification, its approval before the repository is created, and the prioritization of the resulting epics remain human decisions.

Prerequisites

• A requirement text as the starting point of the specification.
• A chosen or newly created stack profile for the emerging project.
• Approval of the specification before it produces a repository and epics.
• A connected repository target for the new project.

Workflow

1. A structured, sectioned specification emerges from the requirement text.
2. Once the specification is approved, the repository scaffold is created.
3. Epics are derived from the specification and taken into the tracker.
4. Each epic is broken down into slices and worked, as in the other examples.
5. The result goes out as pull requests to the new repository, traceable per epic.

Result artifacts

• The approved specification remains available as a document.
• The repository scaffold, complete with stack profile and guardrails.
• Epics in the tracker, linked to their pull requests.
• Progress visible per epic, not just one overall status for the whole project.

Key figures

Log in to see your own run and cost details in the cockpit

Every example on this page was created for illustration. It is not a promise about the duration, quality or cost of a future run of your own — your own figures appear in the cockpit after logging in, within your own tenant context.