Execute qualquer Skill no Manus
com um clique

Execute qualquer Skill no Manus com um clique

handoff-plan

Estrelas2

Forks0

Atualizado30 de junho de 2026 às 05:40

Capture the just-approved plan after exiting plan mode and hand it to a fresh session — write the plan to a file plus the resume pointer the workflow plugin reads, then tell me to /clear and send `go` to execute it. Use for "/handoff-plan", "hand off this plan".

Instalação

Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.

Executar no Manus

Fonte

CrazyWillBear

CrazyWillBear/my-dotclaude

Abrir repositório GitHub Ver repositórios do creator

Download

Executar no Manus

Ocupações relacionadasSOC

Baseado na classificação ocupacional SOC

Desenvolvedores de softwareInformática e Matemática·SOC 15-1252

SKILL.md

readonly

name	handoff-plan
description	Capture the just-approved plan after exiting plan mode and hand it to a fresh session — write the plan to a file plus the resume pointer the workflow plugin reads, then tell me to /clear and send `go` to execute it. Use for "/handoff-plan", "hand off this plan".
argument-hint	[optional path to an existing plan file]
model	inherit
allowed-tools	Read, Write, Bash

Hand the plan you just approved to a fresh session — no rich handoff doc, the plan is the doc. This is the lighter sibling of /handoff: it captures the approved plan to a file and writes the same resume pointer, so after /clear + go the fresh session reads the plan and implements it from the committed baseline. workflow's resume.sh re-injects the pointer, so the only manual step is one command plus a kickoff word.

When. Run this right after you exit plan mode (ExitPlanMode), while the approved plan is still in context — Claude Code does not persist the plan to a file on its own, so this skill writes it.

Dirty tree — warn, don't block. Unlike /handoff, this does not require committed work (you usually haven't written code yet). But if git status --porcelain shows tracked changes, warn me that they will be lost on /clear (commit them first if I want them) — then proceed anyway. The baseline is the current HEAD regardless.

Steps

Resolve the plan content (arg wins, capture by default):
- If $ARGUMENTS is a path to an existing file → Read it and use its contents (the arg always wins when present).
- Otherwise → use the most-recently-approved plan from this conversation, copied verbatim — do not paraphrase, re-summarize, or re-order it.
- If there is neither a path arg nor an approved plan in context → stop, tell me why, and write nothing.
Gather state (Bash) — same keying as /handoff:
- branch = git rev-parse --abbrev-ref HEAD
- toplevel = git rev-parse --show-toplevel — if this is empty (not a git repo), bail: there is nothing to key a handoff to.
- common_dir = git rev-parse --git-common-dir, then canonicalize: common_dir="$(cd "$common_dir" && pwd -P)" — the shared .git, identical from the primary tree and every linked worktree (so a worktree handoff resolves repo-wide)
- head = git rev-parse HEAD
- ts = date +%s
- repo_key = printf %s "$common_dir" | sha1sum | cut -c1-16 — the per-repo key
- dir = ~/.claude/handoffs/$repo_key, then mkdir -p "$dir"
Write the plan file to $dir/<branch-slug>-plan.md — replace every / in the branch with - for the slug. Prepend a single # Plan — <branch> — <date> header line, then the resolved plan verbatim. The -plan.md suffix never collides with /handoff's <branch-slug>.md; re-running overwrites the prior plan for this branch.
Write the resume pointer $dir/.pending.json with the Write tool, as JSON in exactly the workflow schema (this mirrors save-handoff.sh — the cross-plugin script path isn't install-stable, so write it inline). The keyed-dir algorithm must match save-handoff.sh: ~/.claude/handoffs/<sha1(canonical --git-common-dir)[:16]>/ (bash: printf %s "$common_dir" | sha1sum | cut -c1-16), pointer named .pending.json. A drift test enforces this, so don't diverge.
```
{
  "handoff_path": "<absolute path to the -plan.md you just wrote>",
  "branch": "<branch>",
  "git_toplevel": "<toplevel>",
  "git_common_dir": "<common_dir>",
  "baseline_head": "<head>",
  "session_id": null,
  "context_tokens": null,
  "ts": <ts>
}
```
handoff_path points at the plan file you just wrote (in $dir). git_common_dir is the canonical shared .git; resume.sh re-injects only when the new session's common dir matches. git_toplevel records the working tree this was written in — if that's a linked worktree, resume.sh tells the fresh session to EnterWorktree(path=…) it before resuming. This is the same .pending.json /handoff uses, so writing it here overwrites any pending handoff for this branch — the newest one wins.
Tell me what to do, in plain English (this is a multi-step instruction — write it normally even in caveman mode): run /clear, then send go. resume.sh will re-inject an order making reading the plan file the fresh session's mandatory first action, then implementing it from the committed baseline, so nothing is lost. Show the plan file path.

Mais deste repositório

mesmo repositório

pipeline

CrazyWillBear/my-dotclaude

Run one task through the plan→build→review pipeline — a Step-0.5 classify-task call routes the planner/implementer/reviewer models to the task's complexity tier, then the plan is written (planner subagent or inline), the implementer builds it in an isolated worktree, the my-review agent reviews the diff, and findings route by severity (low→issues, medium→triaged fix-list, high→collective replan, critical→own cycle). For single tasks not worth slicing into an issue graph. Use for "/pipeline <issue#|task>", "pipeline this".

2026-07-092

my-review

CrazyWillBear/my-dotclaude

Deep, security-weighted review of your changes or a PR — routes the reviewer model to the change's complexity (opus by default; fable for a complex diff, on ask), then spawns the my-review agent (xhigh reasoning) on that model. Read-only, report-only. Use for "/my-review", "/my-review <PR#>".

2026-07-092

classify-task

CrazyWillBear/my-dotclaude

Classify one task or issue into a complexity tier — trivial, standard, or complex — and emit that tier plus a rationale; consumers resolve the tier's {model, effort} roster via the plugin's resolve-tier.sh. Grounds the call by fanning out 1–3 Explore subagents over the touched codebase areas, then asks you to confirm or override. Use for "/classify-task <issue#|brief>", "classify this task".

2026-07-092

orchestrate

CrazyWillBear/my-dotclaude

Run N rounds of the autonomous issue-solving loop — pick the ready set (blockers closed, skip hitl), fan out parallel implementers in isolated git worktrees, hand the completed branches to a merger that merges in dependency order and resolves conflicts under the done-check, close finished issues, then a reviewer files blocking follow-ups. Use for "/orchestrate", "run the loop", "build the ready issues".

2026-07-072

verify-plan

CrazyWillBear/my-dotclaude

Check whether the plan(s)/PRD(s)/issue-slice(s) under discussion still match the decisions made in this session — a sonnet subagent reads the current session log, later decisions win, and reports drift read-only. Use for "/verify-plan", "does my plan still match what we decided?".

2026-07-072

handoff

CrazyWillBear/my-dotclaude

Capture a rich handoff before /clear — write a markdown handoff doc (work done, in-flight state, next steps, key files, gotchas) plus the resume pointer the workflow plugin reads, then tell me to /clear and send `go`. Use for "/handoff", "hand this off", "save state and clear".

2026-06-302

name	handoff-plan
description	Capture the just-approved plan after exiting plan mode and hand it to a fresh session — write the plan to a file plus the resume pointer the workflow plugin reads, then tell me to /clear and send `go` to execute it. Use for "/handoff-plan", "hand off this plan".
argument-hint	[optional path to an existing plan file]
model	inherit
allowed-tools	Read, Write, Bash

Steps

Resolve the plan content (arg wins, capture by default):
- If $ARGUMENTS is a path to an existing file → Read it and use its contents (the arg always wins when present).
- Otherwise → use the most-recently-approved plan from this conversation, copied verbatim — do not paraphrase, re-summarize, or re-order it.
- If there is neither a path arg nor an approved plan in context → stop, tell me why, and write nothing.
Gather state (Bash) — same keying as /handoff:
- branch = git rev-parse --abbrev-ref HEAD
- toplevel = git rev-parse --show-toplevel — if this is empty (not a git repo), bail: there is nothing to key a handoff to.
- common_dir = git rev-parse --git-common-dir, then canonicalize: common_dir="$(cd "$common_dir" && pwd -P)" — the shared .git, identical from the primary tree and every linked worktree (so a worktree handoff resolves repo-wide)
- head = git rev-parse HEAD
- ts = date +%s
- repo_key = printf %s "$common_dir" | sha1sum | cut -c1-16 — the per-repo key
- dir = ~/.claude/handoffs/$repo_key, then mkdir -p "$dir"
Write the plan file to $dir/<branch-slug>-plan.md — replace every / in the branch with - for the slug. Prepend a single # Plan — <branch> — <date> header line, then the resolved plan verbatim. The -plan.md suffix never collides with /handoff's <branch-slug>.md; re-running overwrites the prior plan for this branch.
Write the resume pointer $dir/.pending.json with the Write tool, as JSON in exactly the workflow schema (this mirrors save-handoff.sh — the cross-plugin script path isn't install-stable, so write it inline). The keyed-dir algorithm must match save-handoff.sh: ~/.claude/handoffs/<sha1(canonical --git-common-dir)[:16]>/ (bash: printf %s "$common_dir" | sha1sum | cut -c1-16), pointer named .pending.json. A drift test enforces this, so don't diverge.
```
{
  "handoff_path": "<absolute path to the -plan.md you just wrote>",
  "branch": "<branch>",
  "git_toplevel": "<toplevel>",
  "git_common_dir": "<common_dir>",
  "baseline_head": "<head>",
  "session_id": null,
  "context_tokens": null,
  "ts": <ts>
}
```
handoff_path points at the plan file you just wrote (in $dir). git_common_dir is the canonical shared .git; resume.sh re-injects only when the new session's common dir matches. git_toplevel records the working tree this was written in — if that's a linked worktree, resume.sh tells the fresh session to EnterWorktree(path=…) it before resuming. This is the same .pending.json /handoff uses, so writing it here overwrites any pending handoff for this branch — the newest one wins.
Tell me what to do, in plain English (this is a multi-step instruction — write it normally even in caveman mode): run /clear, then send go. resume.sh will re-inject an order making reading the plan file the fresh session's mandatory first action, then implementing it from the committed baseline, so nothing is lost. Show the plan file path.