german/houseplan-card
1
0
Fork 0
mirror of https://github.com/Matysh/houseplan-card synced 2026-10-03 21:28:59 +00:00
Code Issues Actions 13 Packages Projects Releases Wiki Activity

docs: only product ambiguity goes to the owner

Browse Source 
Agents were escalating technical calls. The owner answers what a person sees
or does and how much user-visible change belongs in an issue; storage, module
layout, naming, test strategy and migration mechanics are settled by the
agents, recorded as assumptions and challenged in review.

Issue: #114
User-Visible: no
This commit is contained in:
Matysh
2026-08-13 12:18:57 +03:00
parent e043974c44
commit 0509e1a008
1 changed files with 22 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files
AGENTS.md
+22 -5
View File
@@ -167,11 +167,28 @@ sections are in `PROCESS.md` §7.1, plus two product ones: which persona meets t
on which surface, at what moment; and what the person sees before and after, in one
sentence without implementation terms.
**Ambiguity is asked, not guessed.** A guess written as fact is the worst kind of
defect: it passes review because it looks like a decision. Ask the owner in one
batched issue comment, each question carrying a proposed default, and put `blocked`
on top of `S3-spec` while waiting. Small or cheap calls are decided and recorded in
an explicit "assumed, change freely" block at the end of the spec.
**Ambiguity is asked, not guessed — but only product ambiguity.** A guess written as
fact is the worst kind of defect: it passes review because it looks like a decision.
The owner answers exactly two kinds of question: **what a person sees or does**, and
**how much user-visible change belongs in this issue**. Behaviour in a boundary case,
which persona wins when two conflict, what counts as acceptable degradation, whether
a neighbouring behaviour is in scope here or becomes its own issue.
Everything a user cannot observe is yours to settle: where state is stored, which
module carries the guard, naming, file layout, test strategy, migration mechanics,
development policy. Decide it, record it in an explicit "assumed, change freely"
block, and let the reviewer challenge it. A technical disagreement between author and
reviewer is settled by the verdict, not by the owner; it reaches him only when the
cycle limit is exhausted.
Split a mixed question instead of escalating all of it. "Where does this state live"
is technical. "Does it survive a page reload and follow the plan across screens" is
product. Ask the second, decide the first.
Ask in one batched issue comment, each question carrying a proposed default, and put
`blocked` on top of `S3-spec` while waiting. A question with a default costs the
owner seconds; one without costs him minutes.
## Gates