harness-local-handover

Generate role-local handover summaries with evidence and unresolved risks.

Updated Apr 18, 2026
One-click install
npx skills add https://github.com/ZhaoyuWu/Website-Wzy --skill harness-local-handover
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-local-handover
Source: https://github.com/ZhaoyuWu/Website-Wzy/tree/main/codex-skills/harness-local-handover
Command: npx skills add https://github.com/ZhaoyuWu/Website-Wzy --skill harness-local-handover

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams create an auditable, role-local handover summary that records completed scope, execution evidence, and unresolved risks for transitions between generator and evaluator phases.

Core Features & Use Cases

  • Record completed scope and files changed during a handover.
  • Attach commands run and key verification results to demonstrate traceability.
  • Document unresolved risks with impact and mitigation strategies for the next phase.
  • Use during /local-handover or local-handover workflow requests to generate consistent handover artifacts.

Quick Start

Produce a role-local handover summary for the current generator pass, including completed scope, evidence, and unresolved risks with mitigation suggestions.

Frequently Asked Questions about harness-local-handover

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

FAQPage Schema
How do I create an auditable handover summary with execution evidence and risk documentation?

To create an auditable handover summary, this skill automates the capture of completed scope, execution evidence, commands run, verification results, and unresolved risks with mitigation strategies. It generates a consistent handover artifact for transitions between generator and evaluator roles.

What is a role-local handover summary and when do I need one?

A role-local handover summary is an auditable record documenting completed scope, execution evidence, and unresolved risks during phase transitions. You need this traceability artifact when shifting work between generator and evaluator roles to ensure accountability.

How do I document unresolved risks and mitigation strategies during a role transition?

To document unresolved risks during a role transition, this skill records identified risks alongside their potential impact and mitigation strategies. This ensures the next evaluator phase receives documented context for any outstanding issues from the generator pass.

Does the local-handover workflow capture commands run and verification results for traceability?

Yes, the local-handover workflow captures commands run and key verification results to demonstrate traceability. It attaches this execution evidence directly to the handover summary, providing an auditable record of completed scope for the evaluator phase.

What's the best way to generate consistent handover artifacts between generator and evaluator phases?

The best way to generate consistent handover artifacts is to apply this skill during local-handover workflow requests. It systematically produces a standardized record of completed scope, execution evidence, and documented risks, replacing manual handover documentation.