write-strategy-doc

To consolidate scattered architecture notes and ADRs into a strategy document, this Skill collects project context and drafts a centralized source of truth. It structures the document with problem, solution evidence, and unresolved items to clarify decision flows.

The best way to document design decisions and their rationale is using a structured strategy document with problem, solution evidence, and unresolved items. This approach maintains a single source of truth through cross-linking and a validation workflow.

You structure a design strategy document by organizing independent sections into problem, solution with evidence, and unresolved items. This structure clarifies the decision flow and tracks ongoing architectural issues through cross-referencing and validation loops.

Yes, you can cross-link architecture notes and ADRs within a single design strategy document. The Skill enforces a structured approach with cross-references and a validation workflow to maintain design decisions as a unified baseline document.

You need a centralized strategy document when your project has scattered design decisions across architecture notes and ADRs. It targets this fragmentation by guiding teams to a single source of truth through a problem, solution, and unresolved items workflow.