Groundwork.
For agents

Task

Report project progress

Prepare a clear progress update with coverage and named gaps.

3 stepsproductdesignengineering
Give this to your agent
Prepare a clear progress update with coverage and named gaps.

Fetch https://ntent.app/r/task/check-progress.json and follow it. Stop and ask me at any step that says to, and do not decide something on my behalf that the plan says is mine to decide.

Reads https://ntent.app/r/task/check-progress.json

The steps

Here so you can follow along, or do it yourself. Your agent gets the same list from the plan above.

  1. 01

    Run the coverage check

    It prints 3 numbers, each measuring something different. Declared field presence: is the field in the code’s types? Fixture key presence: is it in real data saved from the server? UI source mentions: do the screens for that entity mention it? Report each under its own name. None of them proves a journey works. A field kept off screen on purpose is a decision, not a gap. And say what the number is out of: an entity with no screens mapped to it is not counted.

    uses Contract coverage · check-contract-coverage.mjs

    Success check: You have a percentage per entity under its layer name, the fields not declared, the entities not measured, and a dash rather than a number wherever nothing was there to measure.

  2. 02

    Read the journeys

    Click through each journey yourself, including what happens when things go wrong. Write missing screens and broken rules in its gap field. Only mark a journey built once you have seen it work with realistic data. When you do, add a note: the date, who tried it, the commit, and the proof, either a test command or a sentence starting "manual:". The check will not accept built without that note, or while a question the journey depends on is still open.

    Success check: Every journey marked built carries who exercised it, when, at which commit and against what, and every other one names its gap.

  3. 03

    Say it in one sentence

    Give the declared-field percentage and what it is out of, the named gaps, and how many journeys are in each state. Say whether it is ready to ship in a separate sentence. A percentage tells you how much is written in code, not whether it works.

    1 lines
    Run the coverage check and summarise the gaps. For each gap, tell me whether it is unbuilt, built but never seen with real data, or collected and never shown on a screen.