Save where the session stands before ending it, so next can resume it in a clean context. Also reads or records project progress.
The English summary is being prepared. Showing the original description.
See how to installReview the instructions the agent will receive before you install.
Run at the end of a session the user wants to close, before /clear. It
leaves a dated save that next offers to resume. Trace never resumes work
itself. Resolve scripts/trace.cjs from this skill's directory.
save)git log since the last save
(node scripts/trace.cjs saves --all gives its date); git status --short; planned work: briefs (docs/brief/*/brief.md) and proposals
(docs/proposals/*/PROPOSAL.md) not shipped or superseded, review reports
(docs/review/*/report.md) with unchecked points, and open issues from
gh issue list --label arsenal --state open when gh answers.node scripts/trace.cjs save --done "…" --left "…" --next "a ; b" --remember "…" --planned "…". One line per field, in the conversation
language, specific: paths, branch, task ids, issue numbers, commands.
Omit an empty field. The save closes older open saves on the same
branch (superseded): carry into it whatever they still left.next in the harness syntax
(/next:next in Claude Code, /skill:next in OMP and Pi, $next in
Codex).The save is private: the script adds the ledger to .git/info/exclude and
it never enters a commit.
done "<what>" [--files a,b] [--id id] [--status shipped]: one intent
entry. shipped only with evidence.--read n: print the last entries, then stop. Do not reopen the work
they describe.The Stop hook logs files moved and commits made each turn, with no model
call. It records activity, not delivery: never upgrade wip to shipped
without evidence. Keep this cross-session ledger distinct from a ship run's
trace.md; do not copy events between them.
Work solo. Ask before any subagent or reviewer, even in auto mode. No hidden advisor, nested delegation, model retuning, repeated successful checks, or progress spam. Stop when the save is written. User stops and scope changes override pending steps.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Use when the user invokes Arsenal, needs help choosing an approach, or wants an end-to-end task handled with the installed Arsenal skills.
The English summary is being prepared. Showing the original description.
Write a product brief and its task list when the user requests a product specification. Never implement it.
The English summary is being prepared. Showing the original description.
Create, update or resume a GitHub or Linear issue as durable resolution memory when requested.
The English summary is being prepared. Showing the original description.
Start a session from what was left - trace saves, briefs, proposals, review reports, issues - and ask what to continue. Never resume or implement automatically.
The English summary is being prepared. Showing the original description.
Design a concrete technical proposal with evidence and tradeoffs when a decision needs design. No implementation or automatic reviewer.
The English summary is being prepared. Showing the original description.
Deep code review driven by a short interview. Read-only reader agents analyze the chosen scope per angle, the lead verifies every finding, and each point is routed to the skill that fixes it. Never edits the code.
The English summary is being prepared. Showing the original description.