Ari’s Space*   est. 2026
Skip to content
ari*s space[ a. ]
← Librarytools and plugins / 2026-07-22

Save For Later

Keep decisions, rejections and handoffs in one campaign pack. Give the next main session the full picture and each worker a slice shaped for its task.

8 parts / Hover to explore. Click to read.

Keep decisions, rejections and handoffs in one campaign pack. Give the next main session the full picture and each worker a slice shaped for its task.

Decisions + reasons + rejections
                 |
          campaign record
           /           |
  full campaign      task slice
  main session       worker
                         |
                       receipt
Saved decision != build authority
The main session and workers receive different views of the same campaign record. A saved decision preserves continuity without granting new implementation authority.

You finish a useful brainstorm. You've found the constraint, rejected the tempting wrong approach and agreed what to do next. Then you close the tab.

Tomorrow, you explain it all again. A worker arrives with half the brief and helpfully proposes the thing you spent twenty minutes ruling out.

I got tired of re-teaching the same campaign every morning. SFL, Save For Later, gives those decisions somewhere to live: a project pack that carries the campaign between sessions.

Save the decision while you still know why you made it.

Give each reader the right amount

A person picking up the whole campaign needs the history and the unresolved questions. A worker doing one task needs a much smaller brief.

ReaderWhat they receive
You or the next main sessionThe full campaign pack
A worker or sub-agentA thin slice for its task

The full pack holds status, intent, decisions, open threads, subtleties, handoff notes and the file index. You should be able to skim it and understand where the work stands.

The slice gives a worker its mission, MUST, NEVER, exact needles and paths to open. Enough to do the job without asking it to reconstruct the campaign.

Both come from the same record. Workers can return receipts when you want them. They do not become another author of campaign truth or quietly revise a decision in their own version of the brief.

Keep the same eight sections

A familiar shape makes a pack easier to maintain and easier to resume:

  1. Status: current phase, next action and blockers.
  2. Intent: why this campaign exists.
  3. Decisions: dated locks and rejected approaches.
  4. Open threads: the forks you haven't resolved.
  5. Subtleties: nuance worth promoting, rather than a dump of the chat.
  6. Handoff notes: what someone picking this up needs now.
  7. File index: the paths that carry the work.
  8. Changelog: what changed in the pack.

You can keep this in Markdown by hand. The supplied helper keeps an append-only event log and renders the pack from it, so editing the readable view needn't erase the history behind it.

Put it beside your brainstorm

Start by naming the campaign. Create its pack, or adopt an existing campaign from the design notes you already have.

As you work, promote each locked decision and each rejected approach. Record the reason while it is fresh. When you park the work, put the handoff inside the pack. When a design and implementation plan exist, add their paths to the file index.

The design and plan remain the build contract. SFL carries the continuity around them: the small qualification, the rejected shortcut, the thing the next session would otherwise have to discover again.

A saved decision isn't permission to build

Keep your existing approval boundary. If your brainstorming method requires agreement before implementation, a full pack does not cross that boundary.

The next session should be able to see both what was decided and what is authorised. Those are different pieces of information. Saving a good discussion doesn't make every idea in it an instruction.

What's in the package

The zip contains SKILL.md for harnesses that load Markdown skills, a Python 3 standard-library helper called sfl.py, a demo campaign pack, an example thin slice and installation notes.

The helper supports init, promote, slice and render. Running that local helper needs no cloud account or proprietary runtime.

Get SFL

The download form below unlocks the zip and copyable skill text. It asks for your email and consent to receive updates about SFL and related tools; you can withdraw that consent later.

SFL

Get SFL

Email unlocks the zip and the skill text.

Start with one campaign

Unzip the package and copy its sfl folder into your agent's skills directory. From your project, run python3 path/to/sfl/sfl.py init my-campaign, using the actual path to the helper.

Promote decisions as you lock them. Make a slice when you brief a worker. The package's INSTALL.md has the full steps.

You don't need to preserve every sentence you said. Preserve what the next person needs to act correctly: the decision, its reason, the rejection and the next move.

That is what I wanted to save for later.

[ comments ]

guests welcome. members show first in the list

no comments yet. start the thread_

1 / 10