Menu
Use when Gormes work needs external library, framework, upstream repo, provider API, or reference-project context before planning or implementation.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | gormes-context-sourcing |
| description | Use when Gormes work needs external library, framework, upstream repo, provider API, or reference-project context before planning or implementation. |
Best context is the smallest verified source slice. For Gormes, prefer source-backed evidence over memory, summaries, or broad documentation dumps.
Use for Gormes tasks involving:
references/go-agent-os comparison;Do not use this to bypass gormes-hermes-parity; Hermes behavior remains the product contract.
./hermes-agent for Hermes behavior;references/go-agent-os/ for Go donor patterns;| Need | Action |
|---|---|
| Find behavior contract | Inspect Hermes source or fixture |
| Find Go implementation shape | Inspect local Go reference donor |
| Avoid context bloat | Quote path + symbol, not whole repo |
| Resolve stale memory | Prefer filesystem and command output |
| External package risk | Check package age, repo activity, and lockfile impact |
Implement one selected repo-scoped Gormes row with tests. Use when next-work says decision=build. Do not use for decision=plan, broad parity audits, or untracked feature ideas.
Shape source-backed Gormes progress rows. Use for decision=plan builder handoffs, row splitting, feature maps, or parity planning. Do not use when decision=build or for runtime code.
Route Gormes work to the smallest repo-local skill chain. Use before substantial planning/building/refactor work, when unsure which Gormes skill applies, or when creating/improving repo-local skills.
Build one selected Gormes behavior with red-green-refactor. Use when the row or reproduced bug defines a test target. Do not use after decision=plan or for broad planning.
Move one bounded cmd/gormes command domain out of root files toward root main.go only. Use when thinning cmd/gormes, burning down loose root files, preserving CLI behavior, or catching refactor regressions during cmd moves.
Use when an agent is unfamiliar with a Gormes code area, a change crosses package boundaries, or a refactor needs a source-backed module map before edits.