Skip to content

v0.1.5 — the comment outranks the verb

Choose a tag to compare

@priyanshuN priyanshuN released this 27 Jul 15:29

From the first real review through the tool: 9 discuss / 1 fix, and every discuss carried a comment that was an answer — the premise is wrong, that module is out of scope, that cannot happen while the route is assigned.

The instructions defined discuss as "stop and bring it back to the human before acting", so an agent following them faithfully would have gone back and asked nine questions that had just been answered in front of it.

Four verbs collapsing into one is the tell: the verb was not where the human put the information — the comment was — and the tool was reading the wrong field.

What changed. discuss now means "the human has something to say about this before you act", and the MCP instructions state plainly that the comment is the substance while the verb only says how to file it. A discuss with a comment is an answer; only an empty one means stop and ask. They also name what these comments overwhelmingly are — corrections from someone who knows the system — and say the right response is to withdraw the finding and check whether the same correction invalidates its neighbours, rather than defend it or re-raise it later.

Deliberately not a fifth verb. "Rejected" is the disposition the data shows, but skip-with-a-comment and discuss-with-a-comment already express it, decisions is the public contract shared by the schema, the stored cards and the tool shapes, and one card is one data point.

npm i -g @triago/cli

Instructions and wording only — no schema, card-format or API change.