Assess a request
Paste an e-mail, a ticket or a note from a meeting; each ask in it is compared with the project: new, already there, partly there, retired before, or in conflict with a number or limit that is written down.
For: Product owner, Solo builder, Founder, Project lead
Reading the result
- New: nothing like it is written down; if you want it, write a Draft record with acceptance criteria, then the work.
- Already there: a requirement covers it. If it was built, a complaint is a defect and a wish to have it different is a change to delivered scope.
- Partly there: close to a requirement but not the same: extend it, or write a new one.
- May conflict: the same subject with a different number or limit ("4 hours" against "one business hour"). Do not build it as asked; change the requirement through a proposal or record the open point.
- Retired before: it was written once and dropped; find out why before bringing it back.
What it does not do
It writes nothing and compares by shared words, so a request in other words than the requirement may show as new: check the related list. Your agent does the same with assess_request and proposes records, changes or work only with your yes.