gsd-handoff-contract

Create runtime handoff documents with roles, criteria, and risks in .agents/runtime.

Updated Apr 9, 2026

Search Tags:#planning #documentation #collaboration #runtime #governance #handoff #mult-agent

Ready to run

npx skills add https://github.com/Sheon-S/ignition-sdk-agent-kit --skill gsd-handoff-contract

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gsd-handoff-contract
Source: https://github.com/Sheon-S/ignition-sdk-agent-kit/tree/main/.agents/skills/gsd-handoff-contract
Command: npx skills add https://github.com/Sheon-S/ignition-sdk-agent-kit --skill gsd-handoff-contract

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Runtime handoff structure, acceptance-criteria framing, and role-to-role contract guidance for multi-agent tasks. Use when work must pass cleanly between planner, supervisor, implementer, reviewer, or resume flows through .agents/runtime/ files.

Core Features & Use Cases

Explicit handoffs: source role, target role, phase id, files to read, outputs produced, acceptance criteria, open risks.
Short but complete handoffs: keep handoffs concise; reference files, not memory; treat missing acceptance criteria as blockers.
Use Case: Facilitates clear transitions between planning and execution phases by persisting handoff details to disk for auditability and resumability.

Quick Start

Create a clean runtime handoff document that records the source role, target role, phase id, files to read, outputs produced, acceptance criteria, and open risks inside the .agents/runtime directory.

Frequently Asked Questions about gsd-handoff-contract

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

FAQPage Schema

How do I standardize role handoffs for multi-agent tasks?▼

Standardize role handoffs by creating a structured runtime document that records source role, target role, phase id, files to read, outputs produced, acceptance criteria, and open risks inside the .agents/runtime directory.

What is a runtime handoff framework for multi-agent collaboration?▼

A runtime handoff framework captures role transitions and criteria for multi-agent tasks, ensuring work passes cleanly between planner, supervisor, implementer, reviewer, or resume flows through verifiable on-disk artifacts.

How do I persist multi-agent task transitions across disk for resumability?▼

Persist multi-agent task transitions by storing handoff details as files in the .agents/runtime directory, referencing them instead of memory to maintain auditability and resumability across phases.

Do I need acceptance criteria for every role transition in multi-agent governance?▼

Yes, acceptance criteria are required for every role transition, and missing acceptance criteria must be treated as blockers to ensure concise, verifiable handoffs between agents.

What open risks should be documented during multi-agent handoffs?▼

Open risks should document potential issues affecting downstream roles, ensuring the target role in planner, supervisor, implementer, or reviewer flows is aware of unresolved problems before proceeding.

Can I use this handoff contract for resume flows after a task interruption?▼

Yes, the handoff contract supports resume flows by persisting role transitions, phase id, and outputs to disk, allowing work to continue cleanly after interruptions.