Danijel Martinek
756e36c720
The previous layout placed epic folders directly under docs/work/
alongside prds/ and _system/. Tightening: epics now live in their
own docs/work/epics/ subfolder, peer to prds/ and _system/. Same
shape as the existing prds/ bucket.
Final docs/work/ layout:
README.md
prds/<slug>.prd.md
_system/_state.json
epics/<slug>/_epic.md + <story-folder>/_story.md
Renames (git mv preserves history):
- docs/work/binder-wrap-helper/
-> docs/work/epics/binder-wrap-helper/
- docs/work/library-evaluation-policy/
-> docs/work/epics/library-evaluation-policy/
- docs/work/ci-security-and-supply-chain/
-> docs/work/epics/ci-security-and-supply-chain/
Tooling updates:
- state-builder.mjs walks workRoot/epics/ directly; SKIP_FOLDERS
obsoleted (no more sibling folders to filter out).
- dispatch.mjs's findNextTask, tickStoryBulletInEpic, and
flipEpicDoneIfAllStoriesDone all join with "epics" segment.
- prd-ship.mjs's deriveShippingCommits walks workRoot/epics/ and
git-logs docs/work/epics/<epic>/.
- decomposer.prompt.md emits epics under docs/work/epics/<epic-id>/.
- handoff + grill-with-docs glossary references updated.
- Glossary entry for Epic updated.
Reserved future shape: when a task-tracker integration (ClickUp,
Linear) ships, the epics/ subfolder hosts <task-id>-<slug>/
folders. Today it just hosts bare slugs.
37 lines
1.9 KiB
Markdown
37 lines
1.9 KiB
Markdown
---
|
|
name: handoff
|
|
description: Compact the current conversation into a handoff document for another agent to pick up. Use when the user wants to transition work to a fresh session, switch worktrees, or hand off to a subagent.
|
|
argument-hint: "What will the next session be used for?"
|
|
---
|
|
|
|
Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save it to a path produced by `mktemp -t handoff-XXXXXX.md` (read the file before you write to it).
|
|
|
|
Suggest the skills the next session should use, if any. In this repo, the common follow-ups are:
|
|
|
|
- `grill-with-docs` — stress-test the plan before coding
|
|
- `to-prd` — materialize the plan into `docs/work/prds/<date>-<slug>.prd.md`
|
|
- `superpowers:writing-plans` — author the implementation plan
|
|
- `superpowers:subagent-driven-development` — dispatch implementer + reviewer subagents per task
|
|
|
|
## Don't duplicate
|
|
|
|
Reference these artifacts by path or URL rather than inlining their content:
|
|
|
|
- PRDs (`docs/work/prds/*.prd.md`), epics (`docs/work/epics/<epic>/_epic.md`), stories (`_story.md`), tasks (`*.task.md`)
|
|
- ADRs (`docs/decisions/adr-NNN-*.md`)
|
|
- AGENTS.md and CLAUDE.md (the next agent loads these automatically)
|
|
- `_state.json` (orchestrator-derived; the next agent regenerates it from markdown via `pnpm work rebuild-state`)
|
|
- Commit messages, diffs, PR descriptions — link the SHA / PR number
|
|
- Existing plans under `docs/superpowers/plans/`
|
|
|
|
## Do capture
|
|
|
|
- The active **goal** in one sentence
|
|
- **In-flight branch / worktree** and any uncommitted state (e.g. `git status` summary, dangling commits)
|
|
- **Decisions made in conversation** that haven't yet landed in a PRD or ADR
|
|
- **Blockers** and proposed next steps
|
|
- **Skills to invoke first** in the next session
|
|
- If the user passed arguments, treat them as the next session's focus and tailor the doc accordingly
|
|
|
|
Keep the document short — it's a baton, not a thesis.
|