← ClaudeAtlas

flushlisted

Mid-session housekeeping. The main agent updates .agent-docs/now/{status,work-plan,open-questions}.md + log.md to current reality, then continues working in the same session. Does NOT regenerate handoff.md, does NOT archive, does NOT auto-commit. Use when work has progressed and now/* has drifted but you're NOT ending the session.
armenr/modelmux · ★ 1 · AI & Automation · score 73
Install: claude install-skill armenr/modelmux
# /flush — Mid-session checkpoint (foreground) Stop. File the paperwork. Continue. Stripped-down sibling of `/handoff` for the "we're staying in this session" case. **Foreground execution.** The agent WITH the session context does the work. See "Why not backgrounded" at the bottom. ## When to invoke - After completing a meaningful chunk of work (a commit, an ADR write, a design discussion, a deliverable landed) - When `now/status.md` no longer reflects what's actually true - Before context-switching to a new sub-task within the same session - When the user asks for "checkpoint" / "let's update state" / "flush" / "any paperwork?" ## When NOT to invoke - Before context compaction → use `/handoff` (regenerates `handoff.md` + archives — the cross-session bridge) - Before session-end / `/clear` → use `/handoff` - For trivial updates (single-line edit) — just keep working - Repeatedly with nothing material to flush — skip ## Steps ### 1. Pull current state (cheap) ```bash git log --oneline -5 # recent commits git status -s # working tree ``` If the session touched runtime-facing code, gather minimal verification (a `bun run build` / `bun run lint` / `bun test test/` result you already have; a `the TypeScript language server` reachability output for a wiring claim) — only what's relevant to the chunk. Don't over-fetch. ### 2. Rewrite `.agent-docs/now/status.md` in place Fleeting doc — overwrite, don't append. Target 80-120 lines. Sections: - **TL;DR** (2-3