한국어
☰ Categories

Write a handoff doc for an AI-built project

Produces documentation that is honest about the parts you do not understand.

CategoryDevelopment › Vibe coding
TagsDraftingChecklistDeveloper
Prompt
Write a handoff document for a project built largely with AI assistance.

Sections:
1. What it does, and what it deliberately does not.
2. How to run it — setup, environment, external services.
3. Architecture as actually built, not as intended.
4. *Areas I do not fully understand* — named explicitly, with what I know about each and what I have not verified. This section is the point of the document.
5. Known fragility — what broke before, what is untested, what was patched rather than fixed.
6. Where to be careful, and what to verify before changing it.
7. Decisions made and why, where I know the why.

Rules:
- *Do not present uncertain areas as understood.* A handoff that overstates confidence is worse than no handoff — the recipient will trust the wrong parts.
- Distinguish "tested and works" from "appears to work".
- Do not document intent as if it were behavior. Where I only know what it was supposed to do, say that.
- Be concrete about what the next person should read first.
After pasting, fill in the fields at the bottom (Project · What I understand · What I do not)

What this prompt does

Nobody fully understands AI-built code, including its author. This separates what you know from what you do not, so the recipient knows where to be careful.

More in this category

AI builder
AI-Powered Personal Compliment & Coaching Engine
Anime
Business Engineer Dashboard Creator
Dating Profile Optimization Suite