Groundwork.
For agents

Task

Agree on the product model

Bring requirements and call notes into one agreed source.

5 stepsproductdesign
Give this to your agent
Bring requirements and call notes into one agreed source.

Fetch https://ntent.app/r/task/agree-one-model.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/agree-one-model.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

    Gather the source material

    Collect the requirements, emails, and call notes. Keep each one as it arrived, without tidying it up first, so you can always point back to what was actually said.

    Success check: Nothing that arrived still lives only in a chat thread or somebody’s memory.

  2. 02

    Start with the file

    Start one JSON file. List the things the product deals with (entities, like an order or a user), what each one holds (fields), the states it moves through (stages), and the paths people take (journeys). Only cover the part you will build next. Add more later.

    uses Product intent model · contract.json

    Success check: The coverage check runs and prints a number, even if the number is small.

  3. 03

    Say which document wins

    Sometimes 2 documents disagree. Decide in advance which one wins, for example the signed spec over an old email, and write that order in the model.

    uses Source priority

    Success check: 2 sources conflict and the resolution takes 30 seconds.

  4. 04

    List the open questions

    Anything nobody has decided yet becomes an open question. Note which screens it affects, and get an answer before building those screens.

    1 lines
    Are there any open questions that affect [ACTOR] screens? For each one, tell me which screens it blocks and what I should mark as TBD instead of designing around it.

    Success check: Each open question names the screens it blocks.

  5. 05

    Record rule approvals

    For each rule someone approves, write down who, when, and their exact words.

    uses Rule approvals

    Success check: You can answer "who agreed to that" without opening your email.