golang-how-tolisted

# Plan a Go Skill Workflow This is a planning and routing aid, not a catch-all Go engineering skill. Use it only for an explicit request to select skills, design a reusable Go workflow, or define project guidance. ## Understand the request Inspect only enough project context to distinguish: - the concrete outcome and affected code or artifact; - whether the work is implementation, diagnosis, review, modernization, performance, security, documentation, or release engineering; - frameworks and tools already present in go.mod and repository configuration; - existing repository instructions and verification commands; - risk, external side effects, and whether the user asked for a plan or execution. Do not load every Go skill to discover what might help. Use the available skill catalog descriptions first, then read only the few candidates whose boundaries are relevant. ## Select the smallest useful set Recommend a skill only when it changes decisions beyond ordinary Go competence. Prefer one primary skill; add a second only for a distinct required concern. For each recommendation, state: | Field | Meaning | | --- | --- | | Task slice | The part of the request it owns | | Candidate | The available skill name, if present | | Why | The non-obvious guidance it contributes | | Order | When it should be applied | | Boundary | What remains outside that skill | Avoid stacking broad code-style, naming, testing, security, and performance guidance onto every implementation. Special