Audit bead fields, acceptance criteria, and deliverables before subagent handoff.
npx skills add https://github.com/azigler/dotfiles --skill handoff-azigler
Please help me install this Agent Skill. Skill: /handoff Source: https://github.com/azigler/dotfiles/tree/main/agents/skills/handoff Command: npx skills add https://github.com/azigler/dotfiles --skill handoff-azigler
It prevents the next agent from inheriting an incomplete or ambiguous outcome by forcing a structured verification of bead readiness before the orchestrator proceeds.
Read your bead contents, then run the handoff checklist and include tests/lint/project gate results and, when applicable, runtime verification evidence in your final handoff message before committing.
High-intent search queries and answers about installing and using this skill.
Subagent handoff readiness is verified by auditing completed bead fields, checking acceptance criteria status, and validating deliverables based on bead type before the orchestrator proceeds. This structured verification ensures the next agent inherits a complete outcome.
Agent handoff verification is the process of auditing a subagent's completed bead fields, acceptance criteria, and deliverables to prevent the next agent from inheriting incomplete or ambiguous outcomes during session transitions or wave dispatching.
To run a handoff checklist, read your bead contents, apply bead-type-specific readiness rules for specs, decisions, tests, and implementations, then include tests, lint, project gate results, and runtime verification evidence in your final handoff message.
Commit readiness checks should be performed during subagent wrap-ups before a final commit and during orchestrator-level sanity checks prior to offboarding when transitioning sessions or dispatching the next wave of agents.
If a bead is missing design decisions or notes for continuity, the handoff verification will fail the readiness check, preventing the orchestrator from proceeding until the incomplete or ambiguous fields are resolved.
Yes, mandatory bead readback is required to field-by-field acceptance verification, bead-type-specific readiness checks, and runtime verification evidence for user-facing implementation artifacts.
dangelesVerify task completion against acceptance criteria and generate a verification report.
mistakeknotAutomate Git commit, push, bead closing, and synchronization for session closure.
aziglerFix identified bugs with mandatory regression guard tests.
storyblokAnalyze code changes to generate a structured QA review plan.
