Greenfield project from a specification

Case study in full

Example scenario

Stack profile: typescript-react-vite-spa · Example scenario with typical orders of magnitude.

A new project starts without code, but with a written requirement. Spec Studio turns it into a structured specification, after your approval the repository scaffold is created, and the specification becomes epics that the run works story by story.

What stays with your team: You set the direction of the specification; approval before the repository is created and the prioritisation of the epics stay with you.

What you need

• A requirement text as the starting point.
• A chosen or newly created stack profile for the project.
• Your approval of the specification before repository and epics are created.
• A connected repository target for the new project.

How the run works

1. A structured, sectioned specification emerges from the requirement text.
2. After your approval, the repository scaffold is created.
3. Epics are derived from the specification and taken into the tracker.
4. Each epic is broken into slices and worked, as in the other scenarios.
5. The results arrive as pull requests in the new repository, traceable per epic.

What you get

• 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 instead of one overall status for the whole project.

Key figures

What stayed open

One epic is waiting for a clarification before its remaining slices start.