Overview

The Doomsday skill implements a rigorous end-of-session protocol to securely snapshot work, update docs, and hand off context for the next session. It treats the current project state as if a rebuild is required from scratch, ensuring every change is persisted and documented. Through four phases, it saves files, synchronizes documentation, preserves a brain dump, and prepares commit-ready records.

How This Skill Works

It runs through four phases: Phase 1 forces saves all code blocks and buffers to their files and creates any missing files. Phase 2 updates essential docs (README.md, PROJECT_STATUS.md, and user/dev docs), creating them if absent. Phase 3 builds a SESSION_HANDOFF_[DATE].md with rationale, gotchas, and next actions. Phase 4 templates a Git commit message and provides exact commands to stage and commit safely, without executing the commit.

When to Use It

• When the user asks to end the session or shut down and wants to preserve context for the next time
• When finishing a coding session to prepare for a handoff to a teammate
• When the project state must be saved and documented before a rebuild or deployment
• When API or UI changes require updated developer or user documentation
• When there are blockers or half-baked changes that should be clearly flagged and preserved before proceeding

Quick Start

1. Step 1: Force-save all code blocks, text buffers, and conceptual changes to their respective files and create any missing files
2. Step 2: Update READMEs and status/user docs; ensure the current state and recent changes are reflected
3. Step 3: Create SESSION_HANDOFF_[DATE].md with Why, Gotchas, and Next Actions; then prepare a Git commit plan with explicit stage and commit commands

Best Practices

• Force save every code block, text buffer, or conceptual change to its file; avoid relying on memory
• Create any new files that were discussed but not generated, ensuring a complete artifact
• Synchronize documentation by updating README.md and PROJECT_STATUS.md, and adjust user/dev docs if needed
• Preserve context through a SESSION_HANDOFF file with Why, Gotchas, and Next Actions
• Provide Git commit prep guidance with exact stage and commit commands, but do not auto run the commit

Example Use Cases

• You complete a major refactor and want to hand off to a teammate with full context and updated docs
• You are finishing a coding session and need a safe record of changes before shutdown
• You prepare for a sprint handoff by updating status docs and API documentation
• Before a server restart or rebuild, you save all work and create a brain dump for future reference
• You document blockers and half baked ideas to avoid deploying broken code

Frequently Asked Questions