myxeliumandCursor
d658ab0827
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>
21 lines
920 B
Plaintext
21 lines
920 B
Plaintext
---
|
||
description: Interview the user before implementing fixes; no guessing
|
||
alwaysApply: true
|
||
---
|
||
|
||
# Interview before implement
|
||
|
||
Before writing or changing product code for a bug/feature ask:
|
||
|
||
1. Read the ask (and the one Obsidian bug note if named). Do **not** start a large codebase rewrite yet.
|
||
2. Reply with a **short interview** (bullets only):
|
||
- What you think the bug/goal is (1–2 sentences)
|
||
- What’s missing / unclear
|
||
- Choices (A/B/C) with a **recommended** default
|
||
- Proposed scope (files/areas you will touch; what you will not)
|
||
- How you will prove done
|
||
3. **Stop and wait** for the user’s answers. Do not implement until they approve or choose.
|
||
4. Then implement exactly what they chose — no silent extra scope.
|
||
|
||
Skip the interview only when the user says e.g. “just fix it”, “no interview”, or the handoff already records approved Next steps/decisions and they said continue.
|