project-handoff

Record verified project continuity, milestone status, blockers, and the next approved action.

Updated Aug 1, 2026
One-click install
npx skills add https://github.com/QuyDu/Skills-Orchestrator --skill project-handoff-quydu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-handoff
Source: https://github.com/QuyDu/Skills-Orchestrator/tree/main/.github/skills/project-handoff
Command: npx skills add https://github.com/QuyDu/Skills-Orchestrator --skill project-handoff-quydu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a work session ends or ownership changes, critical context about project state, decisions, and blockers is often lost, forcing the next person or agent to reconstruct progress from scratch. This Skill captures verified continuity information so work can resume without ambiguity. ## Core Features & Use Cases - Evidence-Backed Handoff Records: Writes synchronized machine-readable JSON and Markdown handoff reports covering milestone status, key decisions, blockers, and the next approved action. - State Verification: Validates milestone status against observable evidence rather than intent statements, and fails closed when authoritative execution state is missing or stale. - Approval Gates: Requires explicit approval before altering scope commitments or handing off actions involving destructive or external mutations. - Use Case: At the end of a partially completed workflow, invoke this Skill to publish a handoff report with clear blockers and a resume point so the next operator can continue without re-investigating prior work. ## Quick Start Use the project-handoff skill to record the current session's verified progress, blockers, and next approved action before transferring ownership.

Frequently Asked Questions about project-handoff

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

FAQPage Schema
How do I create a project handoff report at the end of a work session?

Invoke the project-handoff skill with your current execution state and completion evidence. It collects milestone status, blockers, and decisions, then writes reports/project-handoff.json, reports/project-handoff.md, and an updated current-work-state snapshot.

What is the difference between a project handoff and a change log?

A handoff records verified continuity state for resuming work, including blockers and the single next approved action. A change log lists historical modifications. This skill explicitly should not be used as a change log.

What inputs does the project handoff process require?

It requires current execution state and event history from workflow-state-manager outputs, verified completion evidence such as changed files and validation outcomes, plus active milestone objectives and agreed next actions.

What happens if execution state is missing or stale during handoff?

The skill fails closed: it preserves prior handoff records, publishes a blocked continuity status, and never labels a handoff complete when next-action prerequisites remain unresolved.

When does a project handoff require explicit approval?

Explicit approval is required before altering scope commitments or handing off any action that includes destructive operations or mutations to external systems.