oprogramadorreal/optimus-claude / skills/handoff
handoff
VerifiedCompacts the current conversation into one self-contained, tool-agnostic handoff document at docs/handoffs/<slug>.md so any fresh agent or teammate can resume the work from that file alone. References pushed artifacts by path or URL, inlines anything not on the remote, and redacts secrets and PII. Re-running on an existing handoff offers enhance or overwrite. Writes one project artifact and, when needed, a private scratchpad backup; never commits.
| File | Kind | Size |
|---|---|---|
| README.md | markdown | 2.0 KB |
| SKILL.md | skill md | 10.1 KB |
| agents/openai.yaml | config | 198 B |
README.md
View on GitHub# /optimus:handoff
Compacts the current conversation into a single self-contained, tool-agnostic Markdown document
under `docs/handoffs/` so a fresh agent — a new session, a different AI tool, or another developer
on a different machine — can resume the work by reading only that file.
## When to run
- A working conversation is getting long and you want a durable summary before context is lost.
- You're pausing work that you (later) or someone else will pick up.
- You're handing the work to a teammate, another machine, or a different AI agent.
## What it does
- Writes `docs/handoffs/<slug>.md` capturing the current state, the decisions and rationale behind
the work, any open questions, and relevant files/artifacts — plus a goal and next steps when the
conversation makes them clear.
- References committed artifacts (PRDs, plans, ADRs, issues, commits) by path or URL; inlines
anything not yet pushed so it survives on another machine.
- Scans prose, inlined content, and references for secrets and PII before writing and again on readback; redaction reduces exposure risk without guaranteeing every secret is detected.
- Re-running on the same topic lets you enhance the shared doc (merge new context) or overwrite it.
## Usage
/optimus:handoff
/optimus:handoff finish the migration tests
Arguments are optional: if you pass them, they're recorded as the next session's focus. Without
arguments, the document captures what happened and why, and records a focus or next steps only
when the conversation makes them clear.
## Output
A Markdown file at `docs/handoffs/<slug>.md`. Commit it (e.g. with `/optimus:commit`) so other
machines and teammates can pull it. The document is tool-agnostic — any AI agent can resume from it.
## Notes
- Writes one project handoff artifact and, when needed, a private scratchpad backup of the previous version; it never commits.
- In a multi-repo workspace, the document is written at the workspace root and paths are qualified
by repo name.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |