wrap

To save project context at the end of a coding session, you can reconcile recent git status and diff changes, then route discoveries into durable files like ARCHITECTURE, DECISIONS, and ROADMAP. This preserves session progress and momentum for future work.

Reconciling git diff changes with sprint documentation involves reviewing the current repository state, triaging open TODOs, and updating sprint files to reflect completed work. This grounds your sprint progress in the actual code that shipped.

Preparing a repository for a fresh start requires archiving completed work, noting priority shifts in PLAYBOOK or PROJECT files, and updating sprint progress. This ensures the next session resumes cleanly with accurate project context.

Yes, session wrap triages open TODOs and updates project documentation by routing discoveries and decisions into specific long-term homes. It requires grounding in the actual repository state to accurately capture what changed during the session.

No, session wrap does not require any specific dependencies to save context. It operates independently to review git status, triage TODOs, and route facts into existing project files like ARCHITECTURE and ROADMAP.

You need to preserve project session context into durable files when closing coding sessions to prevent important decisions and learnings from disappearing. This captures progress and next steps for continuous sprint management.