Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Workspace Handoff Checklist

ASecurity

Use this skill when a Mission Control work item is complete or awaiting review and an operator needs a factual handoff draft with outcome, evidence, unresolved risk, next owner, and next action.

2 stars
0 votes
0 copies
0 views
Added 9/23/2026
ai-agents

Security Analysis

A100/100

Scanned 9/23/2026

Install to Claude Code

$npx -y skills add jaydubya818/MissionControl --skill workspace-handoff-checklist --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Workspace Handoff Checklist?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Workspace Handoff Checklist
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jaydubya818-workspace-handoff-checklist/badge)](https://www.skillsdirectory.com/skills/jaydubya818-workspace-handoff-checklist)

More formats (shields.io, HTML) on the badges page.

Download with Pro
Files
SKILL.md
---
name: workspace-handoff-checklist
description: "Use this skill when a Mission Control work item is complete or awaiting review and an operator needs a factual handoff draft with outcome, evidence, unresolved risk, next owner, and next action."
version: 0.1.0
owner: software-factory
risk: low
capabilities:
  - agent-operations
  - handoff
---

# Workspace Handoff Checklist

## Purpose

Produce a concise, factual operator handoff for a completed or review-ready Mission Control work item. Preserve uncertainty rather than filling gaps with assumptions.

## Required inputs

Collect the following before drafting:

1. Work-item identifier and current state.
2. Confirmed outcome or current decision.
3. Evidence references, such as a task, run, test output, document, or PR.
4. Unresolved risk, blocker, or explicit confirmation that none is known.
5. Named next owner and the single next action.

When an input is absent, write `Needs confirmation` for that field. Do not infer a status, URL, owner, approval, or completed action.

## Workflow

1. Confirm whether the work item is complete, awaiting review, or otherwise active.
2. Extract only facts supported by the provided work-item context and evidence.
3. Identify gaps, contradictions, or unverified claims and label them `Needs confirmation`.
4. Draft the handoff using the required format.
5. Self-check that all five required sections are present and that the draft does not change task state, request approval, send a message, create a commit, or deploy anything.

## Required output format

```markdown
## Handoff — <work-item identifier>

**State:** <complete | awaiting review | active | Needs confirmation>

**Outcome:** <confirmed result or Needs confirmation>

**Evidence:**
- <verified reference>

**Unresolved risk:** <known risk, blocker, or No known unresolved risk>

**Next owner:** <named person or role, or Needs confirmation>

**Next action:** <one explicit action, or Needs confirmation>
```

## Examples

### Complete evidence

Input: `SFRL-073 is awaiting review. The local lint passed at 92/100. Draft import created version 0.1.0. Product Owner must decide whether to publish.`

Output:

```markdown
## Handoff — SFRL-073

**State:** awaiting review

**Outcome:** The candidate skill passed local structural lint and was imported as draft version 0.1.0.

**Evidence:**
- Local `skill-lint` result: 92/100
- Registry draft: `software-factory/workspace-handoff-checklist` v0.1.0

**Unresolved risk:** Registry evaluation is a structural proxy until an external agent runner is connected.

**Next owner:** Product Owner

**Next action:** Review the evaluation evidence and decide whether to publish the draft.
```

### Missing evidence

Input: `The task may be done, but no test output or owner was supplied.`

Output:

```markdown
## Handoff — Needs confirmation

**State:** Needs confirmation

**Outcome:** Needs confirmation

**Evidence:**
- Needs confirmation: no test output or source reference was provided.

**Unresolved risk:** Completion cannot be verified from the supplied context.

**Next owner:** Needs confirmation

**Next action:** Attach the relevant task and test evidence before review.
```

Attribution

jaydubya818jaydubya818
View sourceMore from jaydubya818 →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1074701 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

693621 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

691 votes

math-skill

A comprehensive mathematical reasoning skill for AI assistants — handles arithmetic to research-level problems with rigorous step-by-step reasoning, systematic verification, and transparent uncertainty handling

381 votes
View all in ai-agents →