Groundwork.
For agents

Product, design & engineering

Give your agent
a clear plan.

Write down what your product must do, in one file everyone shares. Groundwork adds that file to your repo, plus small checks that catch the build drifting away from it.

Set up your project Explore the method

Plain files. Your repo. No new framework.

PRODUCT MODEL ACTORS ENTITIES JOURNEYS RULES OPEN QUESTIONS BUILD CHECKS CALL NOTES REQUIREMENTS DECISIONS PRODUCT DESIGN ENGINEERING
4 project tiers 49 files, prompts & commands 6 task guidesBrowse the library

Inside your repo

What goes into your repo

3 things that keep what was asked for, what was agreed, and what got built pointing the same way. Start small and add more later.

CONTRACT.JSON FIELDS RULES JOURNEYS AGREED

One product model

One file that lists what the product holds, what it allows, and the paths people take through it. Product, design, and code all read from it.

Explore the model
PRE-COMMIT STAGED CHANGE COMMIT

Checks at every commit

Small scripts run each time someone commits. They stop mistakes like a colour typed in by hand, or a form that saves data without checking it.

Explore the checks
DECISIONS.MD CALL NOTES CLIENT EMAIL APPROVED

Decisions with a source

Next to each rule, note who agreed to it, when, and why. The next person can find the answer without asking around.

Explore the records

Choose your scope

Start with what
your project needs.

A quick prototype needs less than a product 6 people will work on for years. Pick a tier. Each one includes everything in the tiers before it.

Find your tier
01Prototypes & landing pages1 person · Weeks6 steps02A product with a fixed scope1 to 3 people · Months21 steps03Apps with a shared design system3 to 8 people · A year or more28 steps04Products built for the long term4+ people · Years35 steps

Daily work

Guides for everyday work

Short, step-by-step guides for the job in front of you. Each step says how to tell it is done.

Agree on the product model

Bring requirements and call notes into one agreed source.

5 stepsproductdesign

Create the screen list

Turn the agreed model into a list of screens and journeys.

3 stepsdesign

Build a screen

Build a screen from the agreed fields, stages, and rules.

5 stepsdesignengineering

Handle a change during the build

Decide where a change belongs: the model, the design system, or the code.

5 stepsproductdesignengineering

Add an automated check

Turn an agreed rule into a check the whole team can run.

5 stepsengineering

Report project progress

Prepare a clear progress update with coverage and named gaps.

3 stepsproductdesignengineering

Ready for your agent

Start with one prompt

Paste this into your coding agent, such as Claude Code or Cursor. It looks at your project, picks a tier, and adds the files.

When it is done, it tells you what it added, what it skipped, and why. Read that before you commit.

Project setup
Set this repo up with Groundwork. Read https://ntent.app/llms.txt and pick the tier for this project. Follow its plan exactly. Write every file verbatim. Run each verification step. Report what you installed, what you skipped, and why.

Reads https://ntent.app/llms.txt

Direct access

Files your agent can read

Agents read these addresses instead of the pages. Plans come as JSON and files as plain text, taken from the same files our tests run against.