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

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:
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
+25 -17
View File
@@ -17,50 +17,58 @@ Do **not** re-read this whole file every turn after the first skim.
## Workflow Orchestration
### 1. Plan only when ambiguity is real
### 1. Interview before implement (default)
- Plan for unclear architecture or when the user asks.
- Skip plan mode for focused, in-scope edits with clear acceptance criteria.
- For bugs/features: short interview first (understanding, gaps, choices + recommended default, scope, proof) — then wait. See `/AGENTS.md` and `.cursor/rules/interview-before-fix.mdc`.
- Do not guess past ambiguity; the user controls the implementation choices.
- Skip only when the user opts out (“just fix it”) or an approved handoff already decided.
### 2. Subagents sparingly
### 2. Plan mode
- Use plan mode when architecture is unclear or the user asks — the interview often replaces a heavy plan for normal bug fixes.
- Skip long planning essays; prefer bullet choices.
### 3. Subagents sparingly
- Default: one agent.
- Subagents only for true parallel search inside allowed paths.
- Never spawn extra review agents unless the user asks.
### 3. Handoff / short sessions
### 4. Handoff / short sessions
Triggers: user says handoff / new chat; thread is long with more major work left; switching objectives.
Action: overwrite `agents-docs/HANDOFF.md` with `Status: active` (Goal, Completed, Changed files, Decisions, Failed approaches, Current issue, Next steps, Commands). Then stop major work and ask the user to open a new chat.
Action: **overwrite** (never append) `agents-docs/HANDOFF.md` with `Status: active` and short sections. Then stop major work and ask the user to open a new chat.
New chat: if handoff is active, read it first; continue Next steps; do not redo Completed work.
New chat: if handoff is active, read it first; continue Next steps; do not redo Completed work. If Next steps still need choices, re-interview — dont invent them.
### 4. Self-Improvement Loop
**When finished:** clear `HANDOFF.md` to `Status: none` with empty sections so the file stays tiny for the next session.
### 5. Self-Improvement Loop
**At session start:** `LESSONS-INDEX.md` only; open matching lesson bodies by tag.
Record a lesson + index line when corrected. Prefer fewer sharp rules (~20).
### 5. CONTEXT.md upkeep
### 6. CONTEXT.md upkeep
Default: `toju-app/CONTEXT.md`. Read `electron/CONTEXT.md` only when touching Electron. Other packages only when in scope.
### 6. ADR upkeep
### 7. ADR upkeep
Only when hard-to-reverse + surprising + real trade-offs. Contract: `agents-docs/AGENTS_ADRS.md`.
### 7. Verification Before Done (behavior first)
### 8. Verification Before Done (behavior first)
Done = asked functionality works. Unit green ≠ done for product asks. Prefer in-scope proof; dont pull e2e/server “just to be sure.”
Done = asked functionality works **as the user confirmed in the interview**. Unit green ≠ done for product asks.
### 8. Demand Elegance (Balanced)
### 9. Demand Elegance (Balanced)
One pause for non-trivial design; skip for obvious fixes.
One pause for non-trivial design; skip for obvious fixes once the user has chosen a direction.
### 9. Autonomous Bug Fixing
### 10. Bug fixing (after interview)
Fix with evidence in default scope. If root cause is clearly `server/` (or similar), say so and ask to expand scope.
Implement the approved plan with evidence in default scope. If root cause is clearly outside scope, say so and ask to expand — dont silently crawl.
---
@@ -72,4 +80,4 @@ Gitea: `git.azaaxin.com/myxelium/Toju`. Branch `<type>/<short-description>`; PR
## Core Principles
- **Simplicity First** · **No Laziness** · **Minimal Impact** · **Cheap Context** · **Default Scope Fence** · **Handoff Beats Fat Context**
- **Simplicity First** · **No Laziness** · **Minimal Impact** · **Cheap Context** · **Default Scope Fence** · **Handoff Beats Fat Context** · **Interview Before Guessing**