Skip to content
CraftFramework.ai logo representing innovative AI-driven design solutions.
  • AboutExpand
    • CRAFT License
    • CRAFT Terms
    • CRAFT Changelog
  • Help CenterExpand
    • CRAFT FAQ
    • Knowledge Base
    • Support
  • Login
  • Sign Up (It’s Free!)
  • Home
  • FrameworkExpand
    • CRAFT Projects
    • CRAFT Cookbooks
    • CRAFT Recipes
    • CRAFT IngredientsExpand
      • CRAFT A.I. Personas
    • CRAFT Multi-Recipe Workflows
  • BlogExpand
    • CRAFT Beta Posts
    • CRAFT Alpha Posts
    • CRAFT POC Posts
  • CRAFT BetaExpand
    • Founding Chef
  • Downloads
  • News
CraftFramework.ai logo representing innovative AI-driven design solutions.

The CRAFT Framework

22
  • Getting Started
    • THE COOKING METAPHOR EXPLAINED
    • CRAFT VS OTHER AI TOOLS
    • WHO IS CRAFT FOR?
    • WHAT IS CRAFT?
    • Core CRAFT Concepts
      • UNDERSTANDING RECIPES
      • UNDERSTANDING COOKBOOKS
      • UNDERSTANDING INGREDIENTS
      • UNDERSTANDING PROJECTS
      • UNDERSTANDING MULTI-RECIPE WORKFLOWS
      • CRAFT GLOSSARY
      • CRAFT NAMING CONVENTIONS
      • READING CRAFT COMMENTS
    • Installation and Setup
      • Getting Started with CRAFT Studio
      • Getting Started with CRAFT Express
      • Getting Started with CRAFT Foundations
      • Choosing Your CRAFT Version
      • Upgrading Between CRAFT Versions
  • Working With CRAFT
    • How to Find the Right Recipe
    • Troubleshooting Common Issues
    • How to Create Your First Project
    • How to Use the Handoff System
    • How to Use the Handoff System
View Categories
  • Home
  • Docs
  • Support and FAQ
  • The CRAFT Framework
  • Working With CRAFT
  • How to Use the Handoff System

How to Use the Handoff System

Richard Ketelsen's avatar
Richard Ketelsen
Updated on December 9, 2025

5 min read

AI Doc Summarizer Doc Summary
AI Doc Summarizer Thinking Thinking

Category: Working With CRAFT
Type: How-to Guide
Reading Time: 7 minutes
Skill Level: Beginner


The handoff system is how CRAFT maintains continuity between chat sessions. Since AI assistants don’t remember previous conversations, handoffs capture your progress, decisions, and context โ€” allowing each new session to pick up where the last one ended.

Think of it like a chef’s prep notes at the end of a shift: what’s done, what’s in progress, and what the next cook needs to know.


What is a Handoff? #

A handoff is a structured snapshot of your work session that includes:

ComponentWhat It Captures
Session SummaryWhat you accomplished and why it matters
Current StateWhere things stand right now
Key DecisionsChoices made and the reasoning behind them
Next StepsWhat to do when you continue
Open QuestionsUnresolved items needing attention

Handoffs are stored in your Chat History file and numbered sequentially: H001, H002, H003, and so on.


When to Create a Handoff #

Always create a handoff when:

  • You’re ending a work session
  • You’ve made significant progress you don’t want to lose
  • You’ve made decisions that affect future work
  • You’re switching to a different task or project

You might skip a handoff when:

  • You completed a quick, self-contained task
  • Nothing from this session needs to carry forward
  • You’re using Express for varied, unrelated tasks

Rule of thumb: If you’d be frustrated re-explaining context in your next session, create a handoff.


How to Create a Handoff #

The Simple Way #

Just ask:

Create a handoff for this session.

or

Save where we left off.

or

I'm done for now. Can you capture our progress?

The AI will generate a structured handoff covering all the essential components.

The Detailed Way #

If you want to guide what gets captured:

Create a handoff that emphasizes:
- The decision we made about [topic]
- The three options we haven't explored yet
- The blocker we identified with [issue]

The Quick Way (Express) #

In Express, handoffs are streamlined:

Quick handoff.

Alice will capture the essentials without lengthy summaries.


How to Continue from a Handoff #

Starting Your Next Session #

  1. Open a new chat with your AI assistant
  2. Upload your CRAFT files (including the Chat History with your handoff)
  3. Tell the AI to continue:
Continue from handoff H003.

or

Load the latest handoff and let's continue.

or simply

Pick up where we left off.

The AI reads your handoff and resumes with full context.

What the AI Does #

When you continue from a handoff, the AI:

  • Reads your session summary to understand what happened
  • Notes the current state so it knows where things stand
  • Reviews key decisions to avoid contradicting past choices
  • Checks next steps to suggest what to work on
  • Flags open questions that need resolution

You don’t need to re-explain your project. The handoff does that for you.


Handoff Best Practices #

Write Handoffs for Your Future Self #

The person reading your handoff is you โ€” but you in the future, possibly after days or weeks away from the project. Include context that seems obvious now but won’t be later.

Instead of: “Decided on option B”
Write: “Decided on option B (the modular approach) because it allows incremental testing”

Be Specific About Next Steps #

Vague next steps lead to confused future sessions.

Instead of: “Continue working on the document”
Write: “Next: Add the methodology section, then review the introduction for tone”

Capture Decisions with Rationale #

You’ll forget why you made choices. Record the reasoning.

Instead of: “Using blue for headers”
Write: “Using blue (#3182CE) for headers โ€” matches brand guidelines and tested well for accessibility”

Note What Didn’t Work #

Failed approaches are valuable context. Your next session shouldn’t retry them.

Attempted approaches that didn't work:
- CSV export crashed on files >10MB
- The formal tone felt too stiff for this audience

Handoff Depth by Version #

Different CRAFT versions handle handoffs differently:

VersionHandoff StyleBest For
FoundationsGuided, with learning progress trackedNew users building CRAFT skills
ExpressStreamlined, essentials onlyQuick tasks, minimal overhead
StudioComprehensive, with full project contextMulti-session projects

Managing Multiple Handoffs #

Handoff Numbering #

Handoffs are numbered sequentially within each project:

  • H001, H002, H003โ€ฆ and so on

The most recent handoff is always at the top of your Chat History file โ€” reverse chronological order means the latest context is immediately visible.

Referencing Past Handoffs #

Sometimes you need to reference an older handoff:

What did we decide in H005 about the navigation structure?

The AI can look back through your handoff history.

When Handoffs Get Long #

If your Chat History file grows large with many handoffs, you can:

  • Archive older handoffs to a separate file
  • Summarize multiple handoffs into a “checkpoint” handoff
  • Keep only the most recent 5-10 handoffs active

Troubleshooting #

“The AI doesn’t remember our previous session.”
Make sure you uploaded the Chat History file containing your handoff. Each new chat starts fresh โ€” continuity only comes from the files you attach.

“The handoff is missing important context.”
When creating handoffs, be explicit about what matters:

Create a handoff. Make sure to capture the decision about [specific topic].

“I have multiple handoffs and I’m confused.”
Always continue from the most recent handoff (highest number). If you need to go back to an earlier state, specify:

Let's restart from H003, ignoring H004 and H005.

“My handoff is too long/short.”
Request the length you need:

Create a detailed handoff with full context.

or

Create a brief handoff โ€” just the essentials.

What’s Next #

Now that you understand handoffs:

  • How to Create Your First Project โ€” Set up a Studio project with proper handoff structure
  • Understanding Projects โ€” How projects and handoffs work together
  • CRAFT Naming Conventions โ€” How handoff files are named and versioned

Last Updated: December 2025

How to Create Your First ProjectHow to Use the Handoff System
Table of Contents
  • What is a Handoff?
  • When to Create a Handoff
  • How to Create a Handoff
    • The Simple Way
    • The Detailed Way
    • The Quick Way (Express)
  • How to Continue from a Handoff
    • Starting Your Next Session
    • What the AI Does
  • Handoff Best Practices
    • Write Handoffs for Your Future Self
    • Be Specific About Next Steps
    • Capture Decisions with Rationale
    • Note What Didn't Work
  • Handoff Depth by Version
  • Managing Multiple Handoffs
    • Handoff Numbering
    • Referencing Past Handoffs
    • When Handoffs Get Long
  • Troubleshooting
  • What's Next

Share This Article :

  • Facebook
  • X
  • LinkedIn
  • Pinterest

Was it helpful ?

  • Happy
  • Normal
  • Sad

Follow CRAFT on Social Media:

Build-in-the-open updates — recipes, releases, and notes

X X GitHub GitHub Bluesky Bluesky Mastodon Mastodon LinkedIn Hugging Face Hugging Face DEV DEV

All images on CRAFTFramework.ai are generated with AI tools (Midjourney, DALL-E, Gemini, and others) and are owned by CRAFTFramework.ai. These images cannot be used without consent. CRAFT™️ is a trademark of CRAFTFramework.ai.

Licensing: The CRAFT™️ language specification (formal grammar, comment system, structural rules) is released under the Business Source License (BSL) 1.1. You can freely use and explore the language for non-commercial purposes. For commercial use of the language, contact licensing@craftframework.ai. On January 1, 2029, the CRAFT™️ language will automatically transition to an open source Apache 2.0 license. Content (recipes, cookbooks, documentation) is licensed separately — see CRAFT License for the full terms.

Privacy Policy
  • Home
  • Framework
  • Blog
  • CRAFT Beta
  • Downloads
  • News

© 2026 CRAFTFramework.ai , All Rights Reserved.

  • Home
  • Framework
    • CRAFT Projects
    • CRAFT Cookbooks
    • CRAFT Recipes
    • CRAFT Ingredients
      • CRAFT A.I. Personas
    • CRAFT Multi-Recipe Workflows
  • Blog
    • CRAFT Beta Posts
    • CRAFT Alpha Posts
    • CRAFT POC Posts
  • CRAFT Beta
    • Founding Chef
  • Downloads
  • News