メニュー
Deprecated legacy alias retained for audit and rollback. Use pidev-specialised/session-handoff, which owns the canonical continuity capsule and live-state reconciliation contract.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/CleanExpo/skills-library --skill nexus-session-handoff-legacyコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Dispatch the eight operational roles against a task, each grounded in the vault before it reads any code, with a live view of what is running. Use for work that wants several independent lenses at once — map, plan, build, verify, review, security, CI, release — rather than one agent doing everything.
Thin wrapper around the Pi-CEO Hour-1 provisioner. Given a client slug + email, invokes `swarm/inbox/provisioner.py` to spin up the full Linear project + Supabase portal_content + ContextBot Telegram intake bot + welcome email + Phill ping. Use when the user says "onboard {client}", "spin up portal for", "new client setup", or right after `stripe-milestone-invoice` confirms a deposit cleared.
PM-Core — the first autonomous execution agent. Claims the highest-priority agent-ready ticket from the Unite-Group Linear board, clones the repo, implements the fix on a feature branch, runs CI, and opens a PR. Model: claude-sonnet-5 (senior agent tier). Trigger: /pm-core [ticket-id] or autonomous via Hermes cron.
SKILL.md を表示中
| name | nexus-session-handoff-legacy |
| description | Deprecated legacy alias retained for audit and rollback. Use pidev-specialised/session-handoff, which owns the canonical continuity capsule and live-state reconciliation contract. |
| argument-hint | [optional: ticket, branch, PR, feature, repo area, or handoff scope] |
| allowed-tools | Read, Grep, Glob, LS, Bash, Write |
Deprecated: Do not invoke this alias for new work. Use
pidev-specialised/session-handoff. This file is retained temporarily so earlier reports and rollback evidence remain inspectable without colliding with the canonical skill name.
The "1" of the handoff combo: gate the tree green, then write a durable handoff that
/resume-from-handoff (the "2") verifies against and continues from. Run before stopping,
switching terminals, opening a PR, or handing to another agent.
Boundary. This command runs LOCAL verification gates and writes the handoff report + log. It must NOT commit, push, deploy, run migrations, modify tickets, rotate secrets, or touch production — surface those for the user to do after the handoff.
Before writing anything, run the definition-of-done gates:
scripts/handoff-loop.sh # --quick for a fast interim handoff; --full to install deps first
It cleans cache/build bloat, then runs deps → generated-files-current → type → lint →
tests → production build → audits, writing a timestamped healthcheck log to
.handoff-logs/handoff-<ts>.log and printing that path on its last line. A gate whose
toolchain is absent is SKIPPED with a reason, not failed.
If scripts/handoff-loop.sh is absent (another repo), run that repo's detected equivalents
(type-check, lint, test, build, audit) and record the real results the same way.
Phase 0 proves the tree is green. Phase 0.5 proves the session is finished — a green tree can still hide half-done, uncommitted, or never-shipped work. A handoff must never let an unfinished session masquerade as a clean stop. Classify the session into exactly one state and record it in §1 of the report:
merge-gate pre-open checklist (below), then make §8's First command to run the
exact gh pr create (or gh pr ready) command. session-handoff does not open it — opening
a PR here ≈ merging it (see merge-gate), so that stays an explicit user/next-agent action.Make a todo per item. Every item is answered from a this-session tool result, not memory:
git status clean and git stash list empty; nothing staged, stashed, or
uncommitted belongs in the change. (Pulls the merge-gate "Whole" check to the handoff.)gh pr create)Because auto-merge in this estate treats an opened PR as an authorised merge, the ship command
handed off in §8 is only safe when all of merge-gate's Iron-Law conditions already hold —
Whole · Green-on-the-pushed-tip · Dark-by-default · Atomic · Standards-clean · Authority
reconciled. If any is false, the session is WIP, not READY-TO-SHIP: say so and put the fix in
§8. Invoke the merge-gate skill for the full gate; do not paraphrase it here.
User supplied handoff scope:
$ARGUMENTS
If $ARGUMENTS is empty, infer the scope from:
.harness/, skills/, scripts/, tests/, app/, dashboard/, or mcp/ stateInspect what is available without modifying anything:
git branch --show-current
git status --short
git log --oneline -n 8
git diff --stat
git diff --name-only
If safe and useful, also inspect:
git diff
Only run tests if the user specifically asks for verification execution. Otherwise, report the verification commands to run.
Write the handoff to docs/session-handoffs/handoff-<YYYYMMDD-HHMMSS>.md (create the
directory if absent) AND print it to the user — durable on disk is what lets
/resume-from-handoff find it. Follow the 10-section structure in the shared template
references/report-template.md:
Unknown from available context if unclear)Nothing shipped yet. Current work is local/session-only.Start here steps · Do not redo · explicit First command to runIf Phase 0 was BLOCKED, mark the handoff BLOCKED and make §8's first command the gate fix.
End with: Handoff complete. Next safe action: <one sentence>.
/session-handoff (this, the "1") and /resume-from-handoff (the "2") are a pair:
gate-and-write here → verify-and-continue there. The report at
docs/session-handoffs/handoff-<ts>.md and the log at .handoff-logs/handoff-<ts>.log are
the shared contract between them. /resume-from-handoff reads the latest of each and
re-runs scripts/handoff-loop.sh as its own verification gate before resuming — so the tree
is proven green on the way out AND on the way back in.
Phase 0.5 evaluates whether the session is ready to ship; merge-gate owns how the ship
happens safely. session-handoff never opens a PR itself — for a READY-TO-SHIP session it hands
off the exact gh pr create command in §8, gated by merge-gate's Iron Law (opening a PR in
this estate ≈ authorising its merge). Division of labour: session-handoff = the
definition-of-done gate run + the completion classification; merge-gate = the git-merge
boundary and the auto-merge threat around it; ship-chain / ship-it / ship-release = the
idea→ship lifecycle. Invoke merge-gate before running any handed-off ship command.