technical-design-sessionlisted

Design closure: Use when the root technical-design phase needs end-to-end system/integration and Go-ownership decisions through review, repair, and its stop rule. Own phase orchestration and accepted design readiness; Skip when implementation or delegated placement-only authoring is requested.
Dankosik/go-service-template-rest · ★ 6 · API & Backend · score 75

Install: claude install-skill Dankosik/go-service-template-rest

# Technical Design Session Must read [System / Integration Design](../../../docs/spec-first-workflow/phases/system-integration-design.md) and [Go Code / Ownership Design](../../../docs/spec-first-workflow/phases/go-code-ownership-design.md); together they own design decisions, the review trigger, disposition, and stop rules. Close the material flows and changed responsibilities needed by the accepted outcome, then close mechanism and Go ownership together. Apply root self-review and use independent review only when triggered. Carry dispositioned concerns forward; seek fresh review only after `FAIL` repair or material candidate change.