From traces
Quick statistics on recent session traces — command counts, error rates, files modified
How this skill is triggered — by the user, by Claude, or both
Slash command
/traces:trace-statsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Quick overview of recent session activity from `~/.claude/traces/`.
Quick overview of recent session activity from ~/.claude/traces/.
ls -t ~/.claude/traces/*.jsonl 2>/dev/null | head -10session_end entry (last line with "type":"session_end")## Session Traces (last N sessions)
| Date | Commands | Errors | Files Modified | Error Rate |
|------|----------|--------|----------------|------------|
| ... | ... | ... | ... | ...% |
Today: N commands, N errors, N files modified
Trace directory: ~/.claude/traces/ (N files, Nk total)
If no trace files exist, say so and suggest installing the traces plugin.
npx claudepluginhub artmin96/forge-studio --plugin tracesGuides collaborative design exploration before implementation: explores context, asks clarifying questions, proposes approaches, and writes a design doc for user approval.
Creates structured, bite-sized implementation plans from specs or requirements before writing code. Useful for breaking down multi-step tasks into testable steps with file structure and task boundaries.
Synthesizes the current conversation into a structured spec (PRD) and publishes it to the project issue tracker with a ready-for-agent label, without interviewing the user.