Design Doc Write a lightweight architecture design doc for a decision that deserves thinking before code. Use this when the problem has real ambiguity, tradeoffs, cross-cutting concerns, or future maintenance risk. If the solution is obvious and the doc would only become an implementation manual, say so and recommend or instead. Workflow 1. Ground - Treat the full argument as the design brief unless the user names a feature or path. - Derive a kebab-case slug if no name is given. - Read referenced docs, code, specs, plans, and architecture notes so the design fits the system as it exists. - I…