A startup step
Loads your current state before any work begins.
Starter Kit · Intermediate
The Context Capture Starter Kit
Files solve the first problem: output that does not sound like you. This kit solves the second, which is that the files themselves go stale, and nobody tells you when.
What this solves
A setup that keeps itself current.
This kit is for the point where you have facts, standards, and a corrections file in place, and you are ready for your setup to stay current instead of waiting for you to remember to update it.
It needs more than a chat window: a tool that can run on a schedule, or at least on startup, and a place for it to write what it captures. If you do not have the files yet, start with The Files-First Starter Kit.
The four pieces
Build them in this order.
A capture routine
Pulls context from email, chat, and meetings into the right project, on a schedule.
A corrections loop
Turns a repeated correction into a rule you approve.
Stale-context prompts
Flags a pane older than a day, or context past a size limit you set.
The basic workflow
Decide once, let it keep running.
- Build the startup step. Load what is live, open, and standing before any work begins.
- Build the capture routine. Pull context from email, chat, and meetings into the right project on a schedule.
- Build the corrections loop. Capture what gets corrected at the end of a session, and let patterns become rules.
- Add stale-context prompts. Flag a pane older than a day, or a session past a size limit, before it costs you a bad draft.
What you end up with
A setup you do not have to refresh by hand.
- Every session opens on current information instead of a recap
- Context from email, chat, and meetings lands in the right project on a schedule
- Repeated corrections become proposed rules you approve instead of feedback you repeat
- A stale session gets flagged before it produces a bad draft