borghei/Claude-Skills / workflow/handoff
handoff
UnverifiedPackage in-progress work into a self-contained context doc or a background agent's prompt. Use when handing work off, switching off a task, or delegating to a fresh or background agent.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 8.9 KB |
| assets/handoff_template.md | markdown | 1.3 KB |
| assets/sample_background_handoff.md | markdown | 1.7 KB |
| references/background-agent-handoff.md | markdown | 4.7 KB |
| scripts/handoff_context.py | script | 6.8 KB |
assets/sample_background_handoff.md
View on GitHub# Handoff: Add --dry-run to the exporter CLI
**From:** interactive session **To:** background agent **Date:** 2026-11-08
**Assumptions:** none
## Goal & done-state
`exporter --dry-run` prints what would be written and writes nothing. Done when the flag
exists, `tests/exporter/test_main.py` covers both modes, `make test` and `ruff check src`
pass, and a draft PR is open against `main`.
## Current state
- [x] Done: flag parsed in `src/exporter/main.py` (`build_parser()`), commit `a1b2c3d`.
- [~] In progress: write path skips output when the flag is set; `test_writes_file` passes, no dry-run test yet.
- [ ] Untouched: README usage section.
## Next steps (in order)
1. Add `test_dry_run_writes_nothing` in `tests/exporter/test_main.py`; expect no file in `tmp_path`.
2. Print the target path and row count in dry-run mode from `src/exporter/main.py`.
3. Add the flag to the README usage block.
4. Run `make test` and `ruff check src`; open a draft PR titled `feat(exporter): add --dry-run`.
**Start here:** step 1 — write the failing test first.
## Decisions already made (don't relitigate)
- Dry-run prints to stdout, not stderr — matches the existing `--verbose` output.
## Abandoned paths (tried, ruled out)
- Bare `pytest` — fails on import; use `make test` (sets `PYTHONPATH=src`).
## Stop and report when
- Any test outside `tests/exporter/` fails.
- The change needs a new dependency or touches `src/importer/`.
## Report back
- Draft PR link plus a three-line summary as the PR description; nothing else.
## Suggested skills
- tdd-guide — the red-green loop for step 1 and 2.
- code-reviewer — two-axis review of the branch before opening the PR.
## Key locations
- Branch: `feat/exporter-dry-run`
- Spec: `docs/specs/exporter-dry-run.md`
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |