Jeden Skill in Manus ausführen
mit einem Klick

Jeden Skill in Manus mit einem Klick ausführen

handoff

Sterne12

Forks1

Aktualisiert21. Mai 2026 um 09:29

This skill should be used when the user wants to "hand off", "create a handoff", "wrap up for the next session", "pass this to another agent", "continue from a handoff", "pick up where I left off", "resume a previous session", "load a handoff", or mentions handoff documents, session continuity, or task continuation.

Installation

Mit Codex oder Claude installieren Kopieren Sie diesen Prompt, fügen Sie ihn in Codex, Claude oder einen anderen Assistant ein und lassen Sie die Skill-Seite prüfen und installieren.

In Manus ausführen

Quelle

florianbuetow

florianbuetow/claude-code

GitHub-Repository öffnen Creator-Repositorys ansehen

Download

In Manus ausführen

Verwandte BerufeSOC

Basierend auf der SOC-Berufsklassifikation

Leitungssekretäre und Führungskräfte-AssistentenBüro- und Verwaltungsberufe·SOC 43-6011

SKILL.md

readonly

name	handoff
description	This skill should be used when the user wants to "hand off", "create a handoff", "wrap up for the next session", "pass this to another agent", "continue from a handoff", "pick up where I left off", "resume a previous session", "load a handoff", or mentions handoff documents, session continuity, or task continuation.
disable-model-invocation	true

Handoff

Create or continue from structured handoff documents for seamless task continuity across sessions.

Routing

Step 1: Determine Intent

From the user's message, determine whether they want to:

Create a handoff — they want to capture the current session's context for a future agent or session.
Continue from a handoff — they want to resume work from an existing handoff document.

Step 2: Route

Create — Follow the handoff:create workflow.
Continue — Follow the handoff:continue workflow.

Invoke the appropriate subskill. Do not duplicate their logic here.

Mehr aus diesem Repository

gleiches Repository

clean-code

florianbuetow/claude-code

This skill should be used when the user asks to "check clean code", "review code cleanliness", "find code smells", "is this function too long", "are these names clear", "review my error handling", "check my tests", or "clean up this code". Also triggers when the user mentions Clean Code, Uncle Bob, Robert Martin, meaningful names, function length, comment rot, F.I.R.S.T. tests, or names a dimension directly ("naming", "boundaries", "concurrency"). Supports auditing all nine dimensions at once or focusing on a single dimension.

2026-07-2312

agent-guardrails-analyze

florianbuetow/claude-code

Scan Claude Code chat session logs for recurring agent anti-patterns (hedging, stalling, skipping, false completions, preference-asking, dismissing, cosmetic, caveats, flagging) and produce a ranked report with frequency counts, example excerpts, and suggested guardrail rules. Use when user asks to "analyze sessions for anti-patterns", "find bad patterns in logs", "what anti-patterns am I seeing", "agent-guardrails analyze", or wants data-driven guardrail recommendations.

2026-07-1912

agent-guardrails-install

florianbuetow/claude-code

Install agent behavioral guardrail rules into a project's .claude/ directory. Generates a Stop hook bash script and configures settings.local.json. Includes nine battle-tested rules (no-guessing, no-stalling, no-preference-asking, no-false-completion, no-skipping, no-dismissing, no-cosmetic, no-caveats, no-flagging). Use when user asks to "install guardrails", "set up agent guardrails", "add behavioral hooks", "agent-guardrails install", or wants to enforce assistant discipline.

2026-07-1912

agent-guardrails-test

florianbuetow/claude-code

Test installed agent guardrail hooks by sending trigger phrases through the stop hook script. Checks hook installation first, then runs two test phrases per rule. Use when user asks to "test guardrails", "verify hooks", "check guardrail patterns", "agent-guardrails test", or wants to confirm hooks are working.

2026-07-1912

agent-guardrails-update

florianbuetow/claude-code

Re-analyze Claude Code session logs against existing agent guardrail rules to measure effectiveness, catch false positives, identify missed anti-patterns, and refine regex patterns. Use when user asks to "update guardrails", "refine guardrail rules", "check guardrail effectiveness", "agent-guardrails update", "tune guardrails", or wants to improve existing behavioral rules based on real usage data.

2026-07-1912

product-spec

florianbuetow/claude-code

Use when the user wants to write a "product spec" or "product specification", frame a "product bet", or define a falsifiable hypothesis before building. Also triggers on "replace the PRD", "retire the PRD", "the PRD is too long / too vague", "tighten this spec for an engineer or agent", "what's the bet", "what problem are we solving", "acceptance criteria", "success criteria", "kill / scale / graduate thresholds", "measurement plan", or when scoping a feature's problem, bet, success behaviors, and evaluation before any behavioral spec. Part of the spec-dd workflow; precedes /spec-dd:spec.

2026-06-2912

name	handoff
description	This skill should be used when the user wants to "hand off", "create a handoff", "wrap up for the next session", "pass this to another agent", "continue from a handoff", "pick up where I left off", "resume a previous session", "load a handoff", or mentions handoff documents, session continuity, or task continuation.
disable-model-invocation	true

Handoff

Create or continue from structured handoff documents for seamless task continuity across sessions.

Routing

Step 1: Determine Intent

From the user's message, determine whether they want to:

Create a handoff — they want to capture the current session's context for a future agent or session.
Continue from a handoff — they want to resume work from an existing handoff document.

Step 2: Route

Create — Follow the handoff:create workflow.
Continue — Follow the handoff:continue workflow.

Invoke the appropriate subskill. Do not duplicate their logic here.