maintaining-project-context-and-handoff

Reconstructs project state from repository evidence and manages conditional handoffs across session boundaries.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/alsdmlals4-eng/Base --skill maintaining-project-context-and-handoff-alsdmlals4-eng
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: maintaining-project-context-and-handoff
Source: https://github.com/alsdmlals4-eng/Base/tree/main/skills/maintaining-project-context-and-handoff
Command: npx skills add https://github.com/alsdmlals4-eng/Base --skill maintaining-project-context-and-handoff-alsdmlals4-eng

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Long-running game development projects lose continuity when conversations end, sessions change, or work transfers between executors. This Skill rebuilds current project state from the repository at an exact commit SHA instead of relying on past chat history, and governs when and how work is handed off. ## Core Features & Use Cases - Fresh-read resume: Reconstructs project identity, current goal, protected scope, next safe action, and evidence ceiling from the repository's AGENTS.md, decisions, and asset manifest without requiring prior conversation. - Mode-based context management: Supports context-refresh, resume, session-handoff, conditional Codex implementation handoff, legacy Notion migration resume, and post-merge reconciliation modes. - Capability-based executor selection: Continues approved work in the current session when tools allow, and creates a handoff only for an actual capability gap or explicit user request. - Use Case: A new chat opens on a Godot game project. The Skill reads the repository at its exact SHA, rebuilds what is done, what is blocked, and what is verified versus NOT_RUN, then either continues the approved work or produces a bounded handoff contract. ## Quick Start Resume my game project by fresh-reading the repository at its current main SHA and tell me the current goal, protected scope, and next safe action.

Frequently Asked Questions about maintaining-project-context-and-handoff

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resume a project in a new chat without past conversation history?

Use the resume mode, which fresh-reads the project repository at its exact SHA. It reconstructs project identity, current goal, protected scope, next safe action, and evidence ceiling from AGENTS.md, decisions, and the asset manifest, so past conversation is not a required input.

When should work be handed off to Codex instead of continuing in the current session?

Create a handoff only when there is an actual capability gap or an explicit user request for a specific executor. File type or application name alone never forces a handoff; if the current session has the tools to continue approved work, it should continue.

Does this workflow still require Notion as a workspace?

No. The repository is the primary canon, and Notion is only a legacy read-only migration source when unique unmigrated data actually exists. New work does not write to Notion, and old GitHub-plus-Notion dual-canon routes are retired.

What happens if the repository changed after a handoff was prepared?

The drift gate classifies the state as CONTEXT_DRIFT_RECHECK_REQUIRED. The changed owner is identified, the current diff and manifest are read, fields are rebuilt, and only then are mutations allowed; stale SHAs, PIDs, or sessions are never trusted as current truth.

How are unverified tests or runtime checks handled in status reporting?

Anything not actually executed is recorded as NOT_RUN and never reported as PASS. The Skill distinguishes design, implementation, runtime, and human usability evidence ceilings, and READY_FOR_GPT_REVIEW alone does not claim implementation or independent review success.