Handoff
Create a compact continuation record for another session or agent.From its SKILL.md
npx -y skills add yyqqCoding/engineering-flow-skills --skill handoffAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.5 KB, as published. Nobody here has run it
Handoff
Capture the minimum durable state another session needs to continue safely.
Gather current facts
- Re-read version-control status and relevant diff.
- Read the authoritative requirement/design documents.
- Check the latest verification output rather than relying on memory.
- Identify blockers, unresolved decisions, and unrelated work that must be preserved.
Produce the handoff
Before returning, verify that all eight items below are explicit. State None for an empty category rather than omitting it, especially blockers, unresolved decisions, and unrelated changes.
Include:
- Objective and accepted behavior
- Current implementation state
- Key files and authoritative documents
- Decisions already made and their reasons
- Commands run and their latest results
- Remaining tasks in dependency order
- Known risks, blockers, and unverified areas
- Version-control state and unrelated changes to preserve
References support the handoff facts; they do not replace them. Briefly summarize each existing decision and its reason even when linking the source, and reference existing documents, commits, diffs, and test output instead of copying their full contents.
Write to the requested path when one is provided. Otherwise return the handoff in the response without creating a repository file silently.
What ships with it: 1 file
237 B alongside SKILL.md
agents/
- openai.yaml237 B
Gives 0 of the 12 instructions most agent orchestration skills give
Counted across 848 of the 1,300 authors here whose files we hold, read 2026-09-06
- Dispatch one agent per independent problem domainin 56 of 848, across 42 files
- Run full test suite after integrationin 55 of 848, across 42 files
- Verify fixes do not conflictin 40 of 848, across 32 files
- Review each summary when agents returnin 40 of 848, across 31 files
- Write a handoff document summarising the current conversationin 30 of 848, across 25 files
- Reference existing artifacts by path or URLin 26 of 848, across 24 files
- Give each agent a specific scopein 19 of 848, across 10 files
- Give each agent a clear goalin 19 of 848, across 10 files
- Include a suggested skills section in the documentin 18 of 848, across 16 files
- Tailor the doc to the user argumentsin 18 of 848, across 15 files
- Issue all subagent dispatches in the same responsein 17 of 848, across 11 files
- Use git worktrees for isolationin 17 of 848, across 8 files
Said here and by no other author read
- Re-read version-control status and relevant diff
- Read the authoritative requirement or design documents
- Check the latest verification output
- Identify blockers and unresolved decisions
- Verify that all eight items are explicit
- State None for an empty category
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.