handoff-execute

Execute handoff briefs with enforced source-read gates, cited plans, and verified retros.

14|1|Updated Jun 14, 2026
One-click install
npx skills add https://github.com/allemaar/open-skills --skill handoff-execute-allemaar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: handoff-execute
Source: https://github.com/allemaar/open-skills/tree/main/skills/handoff-execute
Command: npx skills add https://github.com/allemaar/open-skills --skill handoff-execute-allemaar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Handoff briefs passed between agent sessions often get executed without the receiving agent actually reading the required sources, leading to stale assumptions, re-done work, and unverifiable results. This Skill enforces source-ingestion gates, premise pre-flight checks, and ground-truth retros so a brief becomes auditable work. ## Core Features & Use Cases - Gated source ingestion: Reads every @SOURCES.required entry fully before planning, with ABORT/WARN gates, drift warnings, and did-you-mean hints for missing files. - Premise pre-flight: Reconciles the brief against live git state, cited baselines, and structural claims to detect already-shipped work or drifted assumptions before planning. - Verified execution and retro: Runs the brief's verify commands plus the project gate suite, maps each acceptance clause to a verification result, and writes a structured retro with @GROUND_TRUTH, @GATE_STATUS, and @VERDICT blocks. - Use Case: A session runs /handoff to write a brief for a bug fix; a fresh agent session invokes /handoff-execute <brief-path> and gets a source-cited plan, verified execution, and a canonical retro file. ## Quick Start Run /handoff-execute with the quoted absolute path to a handoff brief produced by /handoff, and the agent will load its required sources, plan with citations, execute, verify, and write the retro.

Frequently Asked Questions about handoff-execute

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

FAQPage Schema
How do I execute a handoff brief in a new agent session?

Invoke /handoff-execute with the quoted absolute path to the brief file. The skill loads the brief, reads all @SOURCES.required entries before planning, executes the plan, runs the verify commands, and writes a structured retro.

What is the difference between handoff-execute and plan-execute?

handoff-execute consumes handoff briefs with @SOURCES blocks and a mandatory retro, while plan-execute handles PLAN.md files with a different schema and no retro requirement. Use handoff-execute only for briefs produced by /handoff.

What happens when a required source file is missing?

In gated mode the skill halts and writes a verdict: blocked retro with a @SOURCE_FAILURES block and a @RESUME_HINT for the originating session. You can re-invoke with --force to proceed in degraded mode, with failures still recorded in the retro.

Does handoff-execute detect work that was already shipped?

Yes. The premise pre-flight runs git log and git status over the brief's scope paths and checks cited baselines and structural claims. If the work already landed or a premise drifted, it halts with a @PREMISE_DRIFT blocked retro.

Where does handoff-execute write the retro file?

The retro is written to $VAULT/Handoffs/{project}/retros/{date}-{slug}-retro.md, or to the brief's output_location override. If the write fails, the retro is emitted to chat with a @WRITE_FAILURE block and the verdict is set to partial.