cross-harness-continuation

Hand off coding tasks between AI agents by enforcing a shared continuity contract and Git-based baseline verification. This preserves context and design consistency, preventing decision-drift when switching tools like Claude Code and Codex on the same codebase.

A continuity contract is a shared JSON schema that tracks baseline commits, scope, and design decisions. It ensures subsequent agents respect the existing Git baseline, accepted invariants, and previously rejected approaches during incremental implementation.

Prevent destructive whole-file overwrites and out-of-scope edits during agent handoffs by applying safety guardrails built into the continuity workflow. These guardrails enforce strict adherence to the established Git baseline and shared contract.

Yes, you can switch from Claude Code to Codex to finish a feature. The continuity skill ensures the new agent respects the existing Git baseline, accepted design invariants, and previously rejected approaches without losing context.

Yes, Git-based baseline verification is required to manage context preservation across agents. The shared continuity contract relies on baseline commits to enforce design consistency and prevent out-of-scope edits during sequential handoffs.

Avoid using a shared continuity contract when your workflow does not require strict architectural context preservation or when tasks are fully isolated, as the schema enforces explicit replan authorization for any architectural changes.