Dako's AI Builder Notes
⌘K
中EN
System
Color theme
Changsha HubOffline
大可 Dako
大可 Dako大可 DakoAI Builder · Agent PractitionerTurning AI into working software. Practical notes on agent engineering, vibe coding, and commercial delivery.
Platform links coming soon
Make handoff stop depending on conversation memoryOnly the chatgone when it's replacedbreaks, can't reconnectRealartifactsdocs, code,artifacts, rulesProject statesomeone else can pick upbreaks, and reconnects
The more real the handoff, the less it fears changing people and sessions.

Someone Else Can Pick It Up

Handoff runs on project state and real artifacts, not chat memory. The swap-the-agent test: with only the project left, can it continue?

The more vibe coding you do, the more memory you carry of "where we left off last round" and "why we decided this then." But it lives only in your head, or in old sessions. Once you change people, sessions, or tools, it's all gone. A steady handoff doesn't rely on memory; it relies on real artifacts landed in the project.

After reading, you should be able to answer:

  • Why doesn't "handoff by conversation memory" last?
  • Which "real artifacts" does handoff land on?
  • How do you use the "swap-the-agent test" to check a handoff?

The problem with memory handoff

  • In your head: change the person, and the knowledge resets to zero
  • Stuck in old sessions: change the session/tool, can't find it back
  • Oral / summary style: only a one-line summary survives; the details all drop

Anything that doesn't land in a project file doesn't count as a real handoff.

Land on real artifacts

Handoff must land on these four "visible, clickable" things:

  • Docs / rules: decisions, conventions, pits—written into the repo
  • Code in place: state, comments, structure notes inside the code
  • Artifacts / outputs: stage deliverables, findable and usable
  • Scripts / checks: things a machine can run, not something a person remembers

The swap-the-agent test

A reusable self-check:

Assume at the end of every stage a brand-new AI (or a new person) takes over. Relying only on the docs, code, artifacts, and rules left in the project—can it continue?

  • Yes → your handoff is real; the flow isn't bound to the conversation
  • No → the handoff is still "I thought I remembered"; it needs to be landed

Resume the task, not the session

  • Don't hope to "find back the old conversation"; that's not reliable
  • Rebuild context from a state file + artifacts: which stage, what's next, where the artifacts are
  • Make every stage's input come from "the previous stage's artifact," and output land in "a file/report," not "the chat is over" anthropic-sdlc

Make handoff this good, and vibe coding becomes not just your personal touch but a work practice that passes on. Finally, give the practice a pace: ship at least once a week.

References

  1. The AI-Native SDLC Playbook (Anthropic)