Pricing page: two plans live, annual toggle left
- Asked
- Add a pricing page with Free and Team plans.
- Done
- Both plans render; copy approved by Ana.
- Next
- Annual toggle. The price IDs are in stripe.md.
Use cases / Handoffs
Every task leaves a note: what was asked, what’s done, what’s next. Any person or agent can continue it, on any machine.
Read flie.sh/use-cases/handoffs.md and set it up for this project.Paste into the agent you’re working with now. See what it sets up
An example: your agent writes “Pricing page: two plans live, annual toggle left” in the folder Handoffs.
The problem
memory-bank folders in one study’s corpus: developers already keep an agent’s context in files by hand.
MSR 2026 study of coding-agent configurationGuides tell developers to refresh those files after every session and commit them, so teammates see them.
Cline memory-bank guidePeople ask for a way to share what their agent knows with the person they work with.
r/Claude, August 2026What your agent sets up
# flie.sh/use-cases/handoffs.md Make a folder "Handoffs" with 2026-09-30 short task name.md Every note says what was asked, what’s done, and what’s next.
Plain Markdown on flie’s site. Read the whole recipe.
Handoffs/ README.md the rules 2026-09-30 short task name.md one note per task
Every agent reads the README first. Edit it and you change the rules for all of them.
# AGENTS.md or CLAUDE.md + When you start, read the newest notes in the flie folder "Handoffs" (fld_…); when you finish or stop, leave one there, following its README.
So every future session keeps it current, not just this one.
Who reads it
Starts from the note, not from scratch.
Remember exactly where you stopped.
Takes over without a meeting.
Sees what was done and what’s left.
Read flie.sh/use-cases/handoffs.md and set it up for this project.Free · Every version kept · Install it yourself