Skip to content
Development
Skill

/trace

Save where the session stands before ending it, so next can resume it in a clean context. Also reads or records project progress.

From plugin
arsenal
2310 skills4 agents

Claude Code

$ npx -y skills add mirkobozzetto/arsenal --skill trace --agent claude-code

SKILL.md

trace.SKILL.md
name: trace
description: Save where the session stands before ending it, so next can resume it in a clean context. Also reads or records project progress.
argument-hint: "[save] | [done <what> --files a,b --id id --status shipped] | [--read n]"

Trace

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 (no argument, or `save`)

1. Gather, without asking: this conversation; `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. 2. Show at most five lines: done, not finished, planned. 3. Ask only what the context cannot answer, one question per message, in plain text and the conversation language, then wait:

  • what to continue next session, with your suggestion;
  • anything to remember that you may have missed: a decision, an approach

that failed. Skip a question the conversation already answers. Usually none is needed. 4. Write it: `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. 5. End with « Tu peux /clear. » in the conversation language, then the resume command as the last line: `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.

Other modes

  • `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.

Execution policy

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.

Read more
@mirkobozzetto
Ships witharsenal

Portable workflow skills and controlled runtime for Pi, OMP, Codex, and Claude Code

2310 skills4 agents
Get the whole plugin

Stars on GitHub

Momentum

stars in total
23
Star history of mirkobozzetto/arsenal on GitHub, a chart by star-history.com

Other skills on arsenal.

arsenal

arsenal

Use when the user invokes Arsenal, needs help choosing an approach, or wants an end-to-end task handled with the installed…

brief

brief

Write a product brief and its task list when the user requests a product specification. Never implement it.

issue

issue

Create, update or resume a GitHub or Linear issue as durable resolution memory when requested.

nap

nap

Session nap in Claude Code - save where the session stands with trace, clear it, and resume it with next, with no question and no…

next

next

Start a session from what was left - trace saves, briefs, proposals, review reports, issues - and ask what to continue. Never…

propose

propose

Design a concrete technical proposal with evidence and tradeoffs when a decision needs design. No implementation or automatic…

More skills from other plugins.

brainstorming
Auto-invoked

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…

@obra@obraInstall Skill
ask-matt

ask-matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

skills10d309k
@mattpocock@mattpocockInstall Skill
accessibility
Auto-invoked

accessibility

Design, implement, and audit accessible UI to WCAG 2.2 Level AA across Web, iOS, and Android — semantic ARIA roles and labels,…

ecc11d293k
@affaan-m@affaan-mInstall Skill
compiler-commit

compiler-commit

Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits…

react1d252k
@facebook@facebookInstall Skill

Questions about trace.

Which coding agents can use trace?
trace installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.