stowlisted

# stow Sweep this conversation for durable knowledge that only exists in chat right now, and file it through the user's explicit instructions, the project's existing local conventions, or the private `.stow-notes.md` fallback in the current directory. The goal is to leave the next session a compact, current operating map, not an accumulating journal: every durable finding lands on disk, and every file this skill touches comes out more accurate, not merely longer. Entries are tiered and decay between passes, and stale material retires to a local archive instead of being deleted. Everything files to a local destination by default; an external system such as an issue tracker is reached only through the explicit-instruction rule in step 3. ## What it does 1. **Sweep the conversation for uncaptured durable knowledge.** Read back over the session and look for: - User preferences: a working-style, tooling, formatting, or approval preference the user stated in passing rather than through a config file. - Project facts: build, test, deploy, architecture, or convention facts about the current project that would help anyone (or any agent) working in it later. - Operational gotchas: a sharp edge, workaround, recurring mistake, or non-obvious cause discovered while working here. - Standing decisions: a choice made this session that should outlive it, such as an approach settled on, an option ruled out, or a convention agreed to. - Undone next steps: anything left open