vibe-handoff-to-speclisted

# Vibe Handoff to Spec ## Purpose Prepare a trusted project for downstream structured execution by packaging the right artifacts, assumptions, and active decisions into a clean handoff. This skill exists to close the Vibe Driven Dev pre-execution journey honestly. It should: - confirm that the project is genuinely handoff-ready - collect the artifacts that matter most - summarize active decisions - summarize open and validated assumptions - define the exact next execution entry - avoid pretending the project is more complete than it really is ## When to Use Use this skill when: - QA has been completed - the project has a trustworthy go decision - the system is genuinely ready to leave Vibe Driven Dev - the next step is structured execution through Spec-Kit or a comparable downstream flow ## 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 only to inspect status or resume context - the system is attempting to skip readiness discipline and jump into execution theater ## Required Context Minimum required context: - QA report - go or no-go artifact - architecture baseline - technical detail - assumptions log - project state Helpful optional context: - decision records - analytics outline - execution notes - pack-specific add-on context - downstream execution preferences If required context is missing or inc