myxelium/Toju
1
0
Fork 0
Code Issues 16 Pull Requests Actions Packages Projects 2 Releases 39 Wiki Activity

chore: interview before fixes and keep HANDOFF.md tiny
Queue Release Build / prepare (push) Successful in 1m3s
Details
Deploy Web Apps / deploy (push) Successful in 12m28s
Details
Queue Release Build / build-windows (push) Successful in 32m9s
Details
Queue Release Build / build-linux (push) Successful in 54m12s
Details
Queue Release Build / build-android (push) Successful in 21m27s
Details
Queue Release Build / finalize (push) Successful in 5m11s
Details

Browse Source 
Require a short user interview before implementing bugs/features, and overwrite or clear HANDOFF.md so it never accumulates session history.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
myxelium
2026-07-22 21:49:06 +02:00
co-authored by Cursor
parent 34c32ba64a
commit d658ab0827
8 changed files with 104 additions and 39 deletions
Download Patch File Download Diff File Expand all files Collapse all files
agents-docs/BUG_TRACKER.md
+6 -5
View File
@@ -14,11 +14,12 @@ When the user says e.g. `fix bug "Images and files in chat doesn't load"`:
1. **Resolve one note** under `Log/Bugs/` whose title matches (usually `Bug - <title>.md`). Do not list or read the whole inbox.
2. **Read that note** (Description, Steps, Expected/Actual, Logs). Read attachments only under that bug’s attachment folder if referenced.
3. Acceptance criteria = the note’s Expected Result (plus any clarifying line from the user).
4. **Fix in default repo scope** (`toju-app/` + targeted `electron/` + CI) per `AGENTS.md`. Do not crawl `server/` / `e2e/` / other packages unless the note or user clearly requires it — then ask once.
5. Prove the asked behavior (not only unit-green). Prefer a regression that encodes the note’s failure mode.
6. When done: set that note’s frontmatter `status` to `Resolved` (or `Closed` if the user prefers). Do not rewrite Description / Investigation / Resolution unless asked.
7. Long thread + more work left → write `agents-docs/HANDOFF.md` and ask for a new chat.
3. **Interview before implement** (see `/AGENTS.md` and `.cursor/rules/interview-before-fix.mdc`): restate the bug, list gaps, present choices with a recommended default, propose scope and proof of done — then **wait** for the user. Do not start coding until they answer (unless they said “just fix it”).
4. Acceptance criteria = the note’s Expected Result **plus** the user’s interview answers.
5. **Fix in default repo scope** (`toju-app/` + targeted `electron/` + CI) per `AGENTS.md`. Do not crawl `server/` / `e2e/` / other packages unless the note or user clearly requires it — then ask once.
6. Prove the asked behavior (not only unit-green). Prefer a regression that encodes the note’s failure mode.
7. When done: set that note’s frontmatter `status` to `Resolved` (or `Closed` if the user prefers). Do not rewrite Description / Investigation / Resolution unless asked.
8. Long thread + more work left → write `agents-docs/HANDOFF.md` and ask for a new chat.
Do **not** re-read `BUG_TRACKER.md` every turn after the first use. Do **not** load the stale “open bugs” snapshot as truth — the vault files are source of truth.