# AI Project Handoff — A Context Pack for Your Next Coding Session

## Document Directory

This paste contains 4 documents:

- [README.md](https://marke.st/p/01M33QDS0Z7SFR09CZDNT9H945/README.md) ← (current)
- [HANDOFF.md](https://marke.st/p/01M33QDS0Z7SFR09CZDNT9H945/HANDOFF.md)
- [prompts/resume.md](https://marke.st/p/01M33QDS0Z7SFR09CZDNT9H945/prompts/resume.md)
- [context.json](https://marke.st/p/01M33QDS0Z7SFR09CZDNT9H945/context.json) (code)

---

## README.md

# Give the next session a head start.

**AI WORKFLOWS / HANDOFF KIT / MARKDOWN + JSON**

> A reusable context pack for handing a project to another developer or coding assistant. The project below is fictional. Status, paths, and decisions illustrate a good handoff; they are not claims about a real repository.

## The problem

A long conversation is not a handoff. The next session needs the current objective, the decisions already made, what is actually verified, and the smallest useful next step—not every abandoned idea.

This example follows **Pocket Atlas**, an imaginary reading-list app. Its next milestone is deliberately small: export saved links as Markdown.

| Open this | You get |
|---|---|
| [HANDOFF.md](HANDOFF.md) | A filled-in handoff with scope, invariants, risks, and acceptance criteria |
| [prompts/resume.md](prompts/resume.md) | A copyable prompt for resuming work without restarting the design |
| [context.json](context.json) | The same important state in a machine-readable structure |

## The five-minute handoff

```text
OBJECTIVE       Export the reading list as Markdown
CURRENT STATE   Design agreed; implementation still pending
DO NOT CHANGE   Storage format, authentication, deployment
NEXT STEP       Add and test a pure Markdown serializer
DONE MEANS      Empty lists, Unicode, and special characters tested
```

### Facts are not plans

Use explicit labels rather than letting confident prose imply certainty.

| Label | Meaning | Example |
|---|---|---|
| **Observed** | Backed by a named artifact | A command ran and its output is attached |
| **Decided** | A design choice, not proof of implementation | Export is generated in the browser |
| **Proposed** | Open for review | Add an export preview later |
| **Unknown** | Must be checked | Browser download behavior in the target environment |

## A useful acceptance checklist

- [ ] Export preserves the saved-item order.
- [ ] Titles containing brackets do not break Markdown links.
- [ ] Empty lists produce a clear, valid document.
- [ ] Export does not send the reading list to a third party.
- [ ] The handoff includes exact commands and actual results after work finishes.

## Try this pattern

Copy the handoff into your own project, replace the fictional details, and publish the resulting document set. Keep review notes beside the implementation plan instead of hiding them in a chat transcript.

**Important:** Never put API keys, private customer material, or real access tokens into a public handoff. A repository path is not evidence that a file exists; verify it.

---

*An original fictional example published with [Marke.st](https://marke.st). Turn Markdown, code, and AI output into a link worth sharing.*