Appearance
Briefing
A single command that writes a project briefing an outside AI with no repo access can read cold. It started as a one-off prompt finn pasted into claude.ai to explain the harness, then got turned into a repeatable /briefing command so any repo can regenerate its own briefing on demand instead of someone hand-writing that prompt each time. Reach for it whenever you need to hand a project to an AI (or a person) that has never seen the source.
In Practice
Brief a fresh AI on this repo.
/briefingIt checks for docs that already do this job first: a generated wiki or docs site, a root README or ARCHITECTURE doc, and a changelog or pending marker that tracks staleness. Anything it finds gets treated as a first draft and cross-checked against the pending/changelog file rather than trusted outright. Then it walks the repo for top-level structure, stack, distinct modules, cross-cutting systems, and the real design choices the codebase enforces. It drafts the doc up full, then compresses to fit a token budget, cutting redundant explanation first, then peripheral modules, then nice-to-have detail, never the project's identity, stack, core modules, or core philosophy.
An example outcome. The result lands at BRIEFING.md at the repo root, overwriting any existing one, at the default 10,000 token budget. Naming a different token budget or output path in the invocation makes the command follow those instead of the defaults.
Key Files
commands/briefing.md
The /briefing driver – the whole four step procedure lives in this one command file: find existing docs, explore the source, draft then compress, write the result. It also carries a fallback for small or single-purpose repos, skip the grouping and use a handful of flat sections instead of forcing categories that don't exist.
README.md
The module's own doc – describes what the command does and its one invocation, /briefing, with no flags needed for the default run.
Connects to
- Ships alongside sheet as one of two parts in the commands module, declared in
harness/modules/commands/module.jsonunder thecommandsgroup atlightweight, and installs to a project's.claude/commands/briefing.md. - The commands module carries the shared
USAGE.mdfor both its parts; this part's ownREADME.mdsits beside the command file.