vibe-handofflisted

Generates complete handoff packages for every transition scenario in a vibe-* project. Five modes: client (project completion), milestone (phase sign-off), dev (new developer onboarding), internal (team handoff between BetaCraft developers), maintenance (handing to client's own dev team). Each mode produces markdown documents plus a single self-contained index.html portal — clean, light-mode, client-readable, combining all docs into one navigable file. Includes delivery doc, feature walkthrough, credentials placeholder, known issues, support guide, sign-off checklist, and roadmap. Reads BRIEF.md, SPEC.md, DECISIONS.md, TASKS.md, ARCHITECTURE.md, CODEBASE.md. Triggers on handoff: client, handoff: milestone, handoff: dev, handoff: internal, handoff: maintenance, prepare handoff, client delivery, project sign-off, onboard new developer, prepare for maintenance, ready to hand over.
aakashdhar/vibe-skill · ★ 7 · Data & Documents · score 68

Install: claude install-skill aakashdhar/vibe-skill

# Vibe Handoff Skill Generates complete, audience-appropriate handoff packages from actual project state — not from templates filled with guesswork. Every document is grounded in BRIEF.md, SPEC.md, DECISIONS.md, TASKS.md, ARCHITECTURE.md, and CODEBASE.md. Nothing is made up. Nothing is left as a placeholder except credentials. Each package produces: - Individual `.md` files for each document (unchanged — for version control and editing) - A single `index.html` portal (new) — a clean, light-mode, elegantly designed web page that combines all documents into one navigable file, optimised for sharing with clients --- ## Five handoff modes | Trigger | Scenario | Primary audience | |---------|---------|----------------| | `handoff: client` | Project completion | Client stakeholder (non-technical) | | `handoff: milestone` | Phase sign-off | Client stakeholder + PM | | `handoff: dev` | New developer joining | Developer taking over | | `handoff: internal` | one developer → another | internal developer | | `handoff: maintenance` | Handing to client's dev team | Client's technical team | --- ## Step 0 — Parse trigger and read context **Detect mode from trigger:** - `handoff: client` → full project completion package - `handoff: milestone` → phase-specific package (which phase? read TASKS.md) - `handoff: dev` → developer onboarding package - `handoff: internal` → internal BetaCraft dev handoff - `handoff: maintenance` → client maintenance team package **If no mode specified:*