← ClaudeAtlas

handoff-writerlisted

Write the concrete downstream handoff artifacts for a VDD project once QA and readiness checks have passed.
Gladisintelligible706/vibe-driven-dev · ★ 0 · AI & Automation · score 68
Install: claude install-skill Gladisintelligible706/vibe-driven-dev
# Handoff Writer ## Purpose Write the concrete handoff artifacts that carry a trusted VDD project into downstream execution. This skill is the low-level writing worker for handoff packaging. It should transform validated context into durable, readable artifacts without re-deciding the project. ## When to Use Use this skill when: - the project has completed QA - a go decision exists - the next step is downstream implementation - the orchestrator or handoff manager needs the actual file contents written ## When Not to Use Do not use this skill when: - the project is not ready for handoff - the request is still planning, research, blueprinting, or detail work - the task is only to inspect status or resume context - the input artifacts are inconsistent ## Core Responsibilities This skill is responsible for: - writing the downstream handoff documents - preserving the project summary and implementation entry point - carrying forward active decisions - carrying forward unresolved assumptions - keeping the handoff readable and execution-oriented ## Non-Responsibilities This skill must not: - alter project decisions while writing them out - invent missing readiness - hide blockers or uncertainty - overwrite trusted context with optimistic prose - bypass QA requirements ## Writing Rules This skill should: - keep the handoff concise but complete - preserve the important implementation context - make the next command or next system entry obvious - separate facts, decisi