finding-unknownsSurface and resolve a task's ambiguities before, during and after implementation: blind-spot pass, self-interview, reference-driven specs, implementation notes, post-hoc explainer or quiz. Use on non-trivial builds, unfamiliar code or domains, subjective criteria, plans that keep needing rework, or
writing-adrsWrite a lightweight Nygard-style Architecture Decision Record under `docs/decisions/` when a non-obvious decision needs context that won't fit in a code comment and would rot if left only in a PR description. Trigger when the user asks "should I document this", "add an ADR", "why did we do X" referr