design-decision-audit
Design Decision Audit
Overview
Use this skill to audit a design document before implementation. The job of this skill is to find missing or weak design decisions, explain the risk, and propose targeted additions.
This skill does not directly edit the design document unless the user explicitly asks for that in a later step.
Inputs
Required input:
- A design document path, design document content, or both
Optional input:
- Extra context paths such as related design docs, implementation plans, or requirement notes
Language Strategy
More from freeacger/loom
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
23writing-clearly-and-concisely
Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.
22test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
22executing-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
22systematic-debugging
Use when debugging bugs, test failures, build failures, performance regressions, or unexpected behavior and you need root-cause investigation before proposing fixes. Trigger on requests to debug, investigate why something broke, or find the source of a technical issue.
22finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
20