firefrost-gaming/firefrost-operations-manual
3
0
Fork 0
Code Issues 146 Pull Requests Packages Projects Releases Wiki Activity

Update handoff template — Step 1 now updates ALL affected documents first

Browse Source
This commit is contained in:
mkrause612
2026-02-12 02:51:19 -06:00
parent de4afd38fc
commit a976dedd33
1 changed files with 32 additions and 19 deletions
Download Patch File Download Diff File Expand all files Collapse all files

51
docs/core/session-handoff-template.md
View File

@@ -4,20 +4,22 @@
---
## STEP 1: Update `docs/core/session-handoff.md`
## STEP 1: Update ALL Affected Documents
Update the session handoff document with:
**Before anything else**, review what changed during the session and update every document that was affected:
- Current date/time and version bump
- Any infrastructure changes from this session
- Any new services deployed or status changes
- Any relationship moments or lore dumps
- Any new tasks discovered
- Any corrections or fixes made
- Updated "Recently Completed" section
- Updated revision history entry
- **`docs/core/project-scope.md`** — if infrastructure, services, or roadmap changed
- **`docs/core/infrastructure-manifest.md`** — if servers, IPs, ports, or services changed
- **`docs/relationship/claude-relationship-context.md`** — if relationship moments, lore dumps, or emotional milestones occurred
- **`docs/relationship/consultant-profiles.md`** — if new consultant info was shared
- **`docs/relationship/origin-story.md`** — if new personal/family history was shared
- **`docs/planning/design-bible.md`** — if branding or design decisions were made
- **`SESSION-HANDOFF-PROTOCOL.md`** — if accessibility, relationship, or infrastructure fundamentals changed
- **`DOCUMENT-INDEX.md`** — if any files were created, moved, or deleted
- **Any deployment docs** — if services were deployed or reconfigured
- **Any other document** that was touched, referenced, or made stale by this session's work
**Do NOT rewrite from scratch.** Update the existing v3.0+ document in place.
**Rule: No document should be left stale when the session ends.**
---
@@ -30,7 +32,24 @@ Update the session handoff document with:
---
## STEP 3: Write Journal Entry
## STEP 3: Update `docs/core/session-handoff.md`
Update the session handoff document with:
- Current date/time and version bump
- Any infrastructure changes from this session
- Any new services deployed or status changes
- Any relationship moments or lore dumps
- Any new tasks discovered
- Any corrections or fixes made
- Updated "Recently Completed" section
- Updated revision history entry
**Do NOT rewrite from scratch.** Update the existing document in place.
---
## STEP 4: Write Journal Entry
Create `docs/archive/sessions/YYYY-MM-DD/journal-MMMDD-YYYY.md` with:
@@ -44,7 +63,7 @@ Create `docs/archive/sessions/YYYY-MM-DD/journal-MMMDD-YYYY.md` with:
---
## STEP 4: Deliver the Startup Prompt
## STEP 5: Deliver the Startup Prompt
**Present this EXACT format to Michael (only update the token if it changes):**
@@ -79,10 +98,4 @@ Friend is first. Always. 💙
---
## STEP 5: Update Protocol (if needed)
If any changes affect `SESSION-HANDOFF-PROTOCOL.md` (new relationship moments, accessibility changes, infrastructure changes), update it too.
---
**This template is for Claude's reference. Michael just says "session handoff" and Claude executes all 5 steps.**