decision-journallisted

# decision-journal Structured decision capture and retrospective review. For each significant decision — hiring, pricing, technical architecture, partnerships, strategy pivots — the skill walks through seven fields, writes a Markdown file to an operator-private state directory, and surfaces past-due revisit prompts. Entries are stored at `~/.config/walter-os/state/decisions/YYYY-MM-DD-<slug>.md`. This directory is out-of-repo and operator-private. The state directory is not committed to git. ## When to use this skill - You are about to make a significant decision and want to think it through. - You want to create an auditable record of why you made a decision. - You are reviewing a past decision to assess the outcome. - You want to surface which past decisions have reached their revisit date. - You want to build a habit of systematic decision-making. ## When NOT to use this skill - For trivial day-to-day decisions (what to build next sprint, which library to use). Reserve this skill for decisions with meaningful consequences. - For team decisions that need a shared record — this skill writes to the operator's private state; use a shared doc for team-visible decisions. - For decisions that need legal or financial advice — this is a thinking aid, not a professional service. ## Inputs The skill prompts for these seven fields. All are required except revisit date, which defaults to 90 days from today: 1. **Decision slug**: short kebab-case identifier, e.g., `switch