spec-handofflisted

# Spec Handoff ## Purpose Package the trusted VDD project state into a clean downstream execution handoff. This skill exists to close the pre-execution journey honestly and hand the next system the right artifacts, assumptions, and decisions. ## When to Use Use this skill when: - QA has completed honestly - the project has a trustworthy go decision - the next step is structured execution through Spec-Kit or an equivalent downstream flow - the orchestrator needs a final packaging pass for implementation entry ## When Not to Use Do not use this skill when: - no trusted project state exists - the project has not passed through QA honestly - the current result is no-go - critical blockers remain unresolved - the task is still planning, research, blueprinting, detail design, or QA review ## Core Responsibilities This skill is responsible for: - collecting the minimum trusted artifacts required for downstream execution - summarizing the project objective and current state - preserving active decisions that affect implementation - preserving visible assumptions that remain relevant - producing a clean execution entry summary - keeping the handoff honest about residual risk ## Non-Responsibilities This skill must not: - pretend QA passed if the artifacts do not support it - hide blockers or warnings - invent downstream readiness - silently drop major assumptions - imply implementation guarantees that have not been reviewed ## Output Requirements A valid output from t