docs: Add Decision Audit checklist to SESSION-HANDOFF-TEMPLATE
Mandatory checklist before writing handoff prevents 'verbal decision → lost context' failures. Chroniclers must verify: - All decisions documented in task files - No promises without task tracking - No 'supposed to be done' items undocumented If any check fails: STOP, update task docs, commit, THEN handoff. Related: FFG-STD-002 v2.0 Decision Capture Rule Related: NEXT-SESSION-PRIORITY.md documentation process review
This commit is contained in:
@@ -99,11 +99,34 @@ You are continuing the work of those who came before:
|
||||
- Use "checkpoint" to pause for clarification
|
||||
|
||||
**At session end:**
|
||||
- **Complete Decision Audit** (see below - MANDATORY)
|
||||
- Write your memorial (see past Chroniclers for format)
|
||||
- Update handoff documents
|
||||
- Commit everything including memorial
|
||||
- Push all changes
|
||||
|
||||
### Decision Audit (MANDATORY Before Handoff)
|
||||
|
||||
**Before writing handoff documentation, you MUST verify:**
|
||||
|
||||
**Decision Capture Check:**
|
||||
- [ ] Did Michael make any decisions this session that aren't in task docs?
|
||||
- [ ] Did I promise to do something that isn't tracked in a task?
|
||||
- [ ] Are there any "supposed to be done" items that aren't documented?
|
||||
- [ ] Did we discuss adding/removing platforms, features, or requirements?
|
||||
- [ ] Did task priorities or assignments change?
|
||||
|
||||
**If YES to ANY of these:**
|
||||
1. ⚠️ **STOP** — Do not write handoff yet
|
||||
2. Update the relevant task documentation NOW
|
||||
3. Commit: `docs: Update Task #XX - [decision made]`
|
||||
4. Push to Gitea
|
||||
5. THEN write handoff
|
||||
|
||||
**This prevents:** "Verbal decision → lost context" failures where next Chronicler has no record of decisions made this session.
|
||||
|
||||
**See:** FFG-STD-002 Section "Decision Capture Rule" for complete details
|
||||
|
||||
---
|
||||
|
||||
## Michael's Health & Accessibility (NON-NEGOTIABLE)
|
||||
|
||||
Reference in New Issue
Block a user