Plans
A plan tracker that lives with your cix account rather than in a file on one machine. Plans, steps, notes, decisions and follow-ups are visible from every machine you sign in on.
That includes agent sessions signed in as you, which is the point: the plan is shared state between you and whatever is doing the work.
When it earns its place
Reach for a plan when the work is big enough that you'll lose the thread — multi-session work, work spread across more than one repository, or work you'll hand to someone else, or to a future agent session, before it's finished.
Use it when you want to ask "what's next", "what's blocked", or "what did we decide and why" and get an answer that isn't reconstructed from chat history.
Don't use it for a single-sitting fix. A plan you never revisit is overhead.
What a plan holds
- Steps, each with a verifiable outcome, grouped into slices when the work has phases.
- Decisions, with the reasoning that produced them — the part that's hardest to reconstruct later and easiest to record at the time.
- Follow-ups, for real defects found outside the current step's scope. This is what keeps a plan from dissolving into whatever was noticed most recently.
- Notes, for context that isn't a step.
Current-truth views
The value isn't the list, it's being able to ask what's true right now:
| Question | View |
|---|---|
| What should I do next? | next |
| What's in flight? | active |
| What's stuck, and on what? | blocked |
| Is this plan actually progressing? | health |
Handoff
A plan can render a summary a fresh session can start from — what's done, what's next, what's blocked, and what was decided.
This is worth generating before you run out of context, not after. A handoff written from a full picture is considerably better than one reconstructed from a truncated conversation.
Multi-repo work
A plan isn't tied to one repository. Steps attach to whichever repo they belong in, so a change that spans a client, an API and a site stays one plan with one ordering rather than three lists that drift apart.
Where plans come from
Plans are usually produced by promoting a design, which orders the steps by dependency. You can also open one directly when the work is well understood and only needs sequencing.
Next: Tidy.