一键在 Manus 中运行任何 Skill

technical-design-session

星标6

分支1

更新时间2026年7月22日 13:29

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.

安装

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

在 Manus 中运行

来源

Dankosik

Dankosik/go-service-template-rest

打开 GitHub 仓库查看创作者相关仓库

下载

在 Manus 中运行

Technical Design Session

Must read System / Integration Design and Go Code / Ownership Design; 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.

同仓库更多 Skills

同仓库

go-systematic-debugging

Dankosik/go-service-template-rest

Root cause: Use when a Go bug, flaky test, build failure, hang, deadlock, timeout incident, or production regression needs causal diagnosis. Own the first broken invariant and, only when authorized, the smallest causal fix and replayed proof; Skip when feature implementation, unresolved policy design, broad review, or claim-only verification is primary.

2026-07-266

pre-spec-challenge

Dankosik/go-service-template-rest

Pressure-test: Use when existing research or framing needs a few independent, discriminating questions before specification or planning. Own hidden assumptions, ownership, failure semantics, irreversible consequences, and rollout risk, plus the next owner; Skip when framing is blank, ordinary spec review is needed, or one isolated high-impact approval question is primary.

2026-07-266

spec-clarification-challenge

Dankosik/go-service-template-rest

Approval question: Use when one candidate-spec decision is high-impact, hard to reverse, or explicitly challenged. Own a read-only pressure test with evidence, options, a recommended option, and decision owner; Skip when framing is blank, whole-spec review is needed, or the clarification is low-impact.

2026-07-266

spec-first-brainstorming

Dankosik/go-service-template-rest

Problem frame: Use when a chosen or mostly chosen feature/refactor direction still needs an engineering-ready behavior delta, scope, constraints, assumptions, and readiness decision. Own that frame, its decided defaults, surviving user-owned questions, challenge routing, and next owner; Skip when raw ideation, final design decisions, or task breakdown is primary.

2026-07-266

go-delivery-platform

Dankosik/go-service-template-rest

Delivery platform: Use when CI/CD gates, release trust, drift controls, containers, migrations, or rollout policy needs a decision, or when changed delivery controls need conformance review. Own delivery acceptance and review; Skip when API, data, security, reliability, or pipeline implementation is primary.

2026-07-256

go-test-strategy

Dankosik/go-service-template-rest

Test strategy: Use when accepted behavior needs risk scenarios, proof levels, deterministic oracles, or executable gates, or when changed tests and validation evidence need review. Own proof design and test conformance; Skip when behavior is unresolved, tests must be implemented, or completion claims need validation.

2026-07-256

一键运行任何 Skill

name	technical-design-session
description	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.