harness-read-handover

Load handover documents and generate structured summaries of decisions, risks, and pending actions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Load local handover files and public handover references, then synthesize a clear, structured summary of decisions, risks, and pending work to resume or hand off work.

Core Features & Use Cases

  • Load local handover files from the workspace and public handover references.
  • Generate a concise summary of decisions, risks, pending tasks, and blockers.
  • Produce continuity notes to guide next actions in a new session or branch handoff.

Quick Start

Provide the handover files and generate a concise summary of decisions, risks, and pending work.

Frequently Asked Questions about harness-read-handover

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

FAQPage Schema
How do I summarize a handover document to resume work in a new session?

Summarizing a handover document involves loading local files and public references to generate a structured summary of decisions, risks, pending tasks, and blockers to resume work in a new session.

What is the best way to extract pending actions and blockers from continuity notes?

The best way to extract pending actions and blockers from continuity notes is to synthesize local and public handover documents into a structured summary that clearly identifies outstanding work and project risks.

Can I load both local handover files and public handover references to generate a summary?

Yes, you can load both local handover files from your workspace and public handover references to produce a structured summary of ongoing work and continuity notes.

Does this handover summarization approach identify project risks and decisions?

Yes, this handover summarization approach identifies project risks and decisions by loading source documents and outputting a structured summary that highlights critical choices, blockers, and pending actions.

When do I need a structured summary for a branch handoff?

You need a structured summary for a branch handoff when you must communicate decisions, pending tasks, and blockers clearly to ensure work continuity in a new development session.