Menu
Produce a compact module brief for a dispatched agent, built from disk, returned as the final message, never written to disk.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Review dimension for naming, idiom, comment debt, and AI tells against the codified per-language and prose standards. Invoked by reviewer agents over one module shard.
Recipe for writing C in the runtime, module placement and the ownership and control-flow discipline. Invoked by writer agents when a C unit is dispatched.
Recipe for writing Clojure, Functional Core / Imperative Shell at the function level (namespaces by domain), native wrappers, and the boundary discipline. Invoked when writing Clojure for the project.
Recipe for writing Elixir, pure functions in modules as the core and GenServer plus OTP as the shell, supervision trees, and NIF discipline for the C and Zig edge. Invoked when writing Elixir for the project.
Recipe for any English the agent produces in this project, commits, comments, docstrings, ADRs, design docs, skill bodies, changelog, error messages, project guides. Optimizes for terse, humanized prose with no em dashes and no AI tells. Invoke for any prose-writing activity.
Recipe for writing Zig, native bodies and edge wrappers, the allocator and lifetime discipline, and the hot-path rules. Invoked when writing or editing any Zig source.
| name | gather-module-context |
| description | Produce a compact module brief for a dispatched agent, built from disk, returned as the final message, never written to disk. |
| user-invocable | false |
Produce the few hundred tokens a dispatched agent needs instead of rediscovering the module. Build from disk, not memory. The orchestrator pastes the return value into its dispatch prompts. Nothing is written to disk.
Sources, in order:
:architecture :modules row
for the module: its responsibility, the files it owns, the
dependency directions that touch it. Detailed contracts live in
references/architecture.md. Pre-build, the row is the module
definition until code lands; mark RECENT: pre-build, no history yet and TESTS: pre-build, no tests yet.ls <module-dir>. The actual files, if the directory exists.
The map can lag the code; note any drift. If the
directory does not exist yet, skip this source and note
SIZES: pre-build, dir not yet created.jj log over the module path (or jj log -r limited to recent
commits touching the dir). What changed recently and why; flags
active work and fresh bug history. Pre-build: empty; say
no history yet.docs/adr/README.md. The decision index, if it exists (it is
created by record-decision when the first ADR lands; do not create
it here). Quote any row whose title touches the module or its
idioms, so dispatched agents know what is deliberate before they
review or edit.wc -l on existing files to surface any approaching the
soft limits (about 800 lines per file, about 200 per function). A
file near the limit is a factoring finding waiting to happen.
Pre-build: nothing to measure.Brief format (keep under about 40 lines):
MODULE <dir>
RESPONSIBILITY: <one line per file, from the map and the code>
BOUNDARY: may include <...>; must NOT touch <other modules, the pure core from the shell, the public API from non-owning modules>
TESTS: <test files> (run: the owning lane)
RECENT: <3-5 one-line commits, or "no history yet">
SIZES: <any file or function near soft limits>
NOTES: <gotchas: native handle lifetimes, store transaction shapes, real-time constraints, validation layers, platform splits, generated files>
Owns the read-only module brief. Module placement and language
discipline are write-<lang>; the dispatch that consumes the brief is
the orchestrator (implement-change, run-review-round). Never
edits source.
The brief, as the final message. Never written to disk.