design-loglisted

# Design Log Maintain `.agents/log/` — a version-controlled journal of product and engineering decisions, tradeoffs, and directions, co-owned by the developer and agents. Entries capture *why* — the reasoning that code and git history cannot recover. Inspired by the [design-log methodology](https://github.com/yoavaa/design-log-methodology). ## Layout - `.agents/log/index.md` — index of all entries - `.agents/log/YYYY-MM-DD-slug.md` — one entry per feature or decision Initialize `.agents/log/` only when the user explicitly asks — by invoking this skill or directly requesting a design log. If `.agents/log/` is absent otherwise, do not create it, even when a plan is approved. When initializing, create `.agents/log/index.md` with the table header from Index Format; create an entry only if the current task records a decision. ## Entry Format ```markdown --- title: Human-readable decision or feature title date: YYYY-MM-DD status: wip | done related_paths: - src/feature-area/ - src/shared/specific-file.ts --- ## Background Context needed to understand the problem. Link related entries as [title](YYYY-MM-DD-other-entry.md). ## Problem What is being solved and why now. ## Questions & Answers Clarifying questions asked and the user's answers. Open questions stay here until resolved. ## Decision The chosen design. Concrete: file paths, type signatures, data shapes. Mark examples with ✅ (do) and ❌ (don't) — the canonical notation for all entries. Use Mermaid diagrams on