dsh-decision-log

Working with AI to build software, the biggest pain is rarely the code itself. It is the context break: start a new conversation, switch tools, and every architectural choice from the previous session evaporates. Three months later you stare at a Redis cache and cannot remember why it was chosen over Memcached. Handing the project to a colleague leaves you at a loss for words when asked why the code was written that way. dsh-decision-log exists to fix exactly this. Every important decision you and your AI make, complete with context and rationale, is written into a plain Markdown file (.dsh/DECISIONS.md) inside your project.

The core workflow is deliberately simple. Say a short phrase or type /log-decision, and the plugin records the decision, background, alternatives, and reasoning into the file. At the start of every new conversation it automatically injects a compact summary (capped at 2000 characters) so the AI walks in already aware of what was decided. Decisions logged by the AI default to a pending state until you confirm or reject them, preventing unauthorized changes. The file is local, git-friendly, and readable by any AI tool, so your decision memory follows the project rather than any single vendor ecosystem.

Who is it for? Developers who work with AI across multiple sessions, tools, or team members and want to stop re-explaining the same context over and over. Two seconds of effort per decision buys back hours of future explanation, onboarding, and rework. The plugin makes no network calls, touches no source code, and stays invisible until you ask for it.