# Agent Workflow Bundle — Resume or transfer ongoing work

> Self-contained build artifact generated from the canonical public Workflow and its referenced public assets.

## Agent instruction

Use this bundle as the operating procedure for the user’s task. Execute the ordered steps end-to-end and apply each embedded asset where it appears. Do not merely summarize the workflow. Do not claim completion until the workflow’s success signal and embedded verification requirements have been checked.

Everything required by the public workflow is embedded below; do not make the user manually provide the referenced Skill, Prompt, or Template files again.

## Workflow contract

- source: workflows/resume-or-transfer-ongoing-work
- canonical human page: https://wbeen-personal-kb.vercel.app/workflows/#workflow-resume-or-transfer-ongoing-work
- lifecycle: stable
- version: 1.0.0
- intended outcome: The receiving agent resumes without re-deriving settled context and completion claims are verified.
- success signal: The receiving agent starts from the recorded next action and the resulting change is independently reviewable.

### Known limitations

- A handoff cannot preserve unrecorded private state.
- "No account
- history
- persistence
- or cross-agent execution is provided by this site."

## Ordered execution

## Step 1 — execute

**Action:** Record settled context, open questions, and the next executable action

**Why now:** Make transfer state explicit

**Embedded asset:** skills/agent-handoff — Agent Handoff

Transfer an in-progress AI-assisted task to another agent or session without losing decisions, evidence, boundaries, and next actions.

### Inputs

- Current objective and scope
- Decisions already made
- Completed and incomplete work
- Evidence, identifiers, URLs, or artifacts needed to resume
- Known risks and boundaries

### Outputs

- Compact handoff brief
- Verified current state
- Explicit unresolved items
- Next executable action

### Guardrails

- Preserve exact identifiers when they are required for continuation.
- Separate verified state from assumptions or recommendations.
- Do not include secrets, credentials, or unnecessary private source content.
- Do not silently rewrite an unresolved decision as if it were settled.

### Verification

- A new agent can identify what is done and what is not done without asking for a full recap.
- The next action can be executed directly from the handoff.
- Important evidence and constraints are traceable to their source or artifact.

### Source instructions

## What it does

Agent Handoff preserves **operational continuity**, not conversational history. It captures the minimum state another agent needs to resume the same task correctly: objective, decisions, evidence, boundaries, unfinished work, and the next executable action.

## When to reach for it

Use it before switching tools, computers, sessions, or agents, especially when the work already contains decisions that would be costly or risky to rediscover.

## What one run does

1. Restate the objective and current scope.
2. Separate completed, in-progress, and unresolved work.
3. Preserve decisions and exact identifiers that materially affect continuation.
4. Attach or point to the evidence needed to trust the current state.
5. State the next executable action and any stop conditions.

## Common failure modes

- Writing a narrative recap instead of an operational state packet.
- Omitting failed attempts or unresolved constraints.
- Copying excessive private context that the next agent does not need.
- Leaving the receiving agent with several possible next actions instead of one clear continuation point.

## It’s working if

The receiving agent can resume the same task with minimal rediscovery and can distinguish confirmed state from assumptions.

## Where it fits

This is primarily an **Execute**-phase continuity skill. Once resumed work reaches a completion boundary, Evidence-first Review is a natural next step.

## Step 2 — execute

**Action:** Retrieve the existing handoff brief when a compact invocation format helps

**Why now:** Prompt Hotbar remains retrieval-only

**Embedded asset:** prompts/agentic-handoff-brief — Agentic Handoff Brief

Package the current state of a task so another agent (or a future you) can continue without re-deriving context.

### Input required

- task context
- current progress

### Output format

structured markdown brief

### Safety notes

- Strip credentials, internal URLs, and personal identifiers before handing off.

### Source instructions

## Purpose

Work that spans multiple agents or sessions loses context at every boundary.
A handoff brief makes the boundary explicit and cheap to cross.

## When to use

Before ending a working session, or before delegating a task to another agent.

## Inputs

- The task context and whatever progress exists so far.

## Prompt

```text
You are writing an Agentic Handoff Brief.

Summarize the current task so a different agent can continue without asking
questions. Use exactly these sections:

## Goal
## Current state
## Constraints and decisions already made
## Next actions (ordered)
## Open questions

Rules:
1. Be concrete: file paths, names, exact terms — no "as discussed".
2. Strip credentials, internal URLs, and personal identifiers.
3. Keep it under 300 words.
```

## Expected output

A markdown brief with the five sections above, under 300 words.

## Safety notes

- Strip credentials, internal URLs, and personal identifiers before handing off.

## Related resources

- Article: A Prompt Library Is Not Enough

## Step 3 — verify

**Action:** Verify the resumed result and any changed assumptions

**Why now:** Preserve evidence across the transfer

**Embedded asset:** skills/evidence-first-review — Evidence-first Review

Review AI-assisted work against observable evidence instead of accepting a plausible completion claim.

### Inputs

- Claimed result or completion report
- Acceptance criteria or intended outcome
- Available evidence such as source files, tests, screenshots, logs, URLs, or system state

### Outputs

- Verified claims
- Unverified or failed claims
- Evidence references
- Residual risk and recommended next action

### Guardrails

- Never upgrade an unobserved claim to verified.
- Distinguish source evidence from inference.
- Stop and report when required verification access is unavailable.

### Verification

- Every approved claim points to observable evidence or an explicit check result.
- Failed or unavailable checks remain visible in the final review.
- The next action is clear without rereading the full work log.

### Source instructions

## What it does

Evidence-first Review changes the review question from “does this sound finished?” to “what can I actually verify?” It is designed for AI-assisted work where confident completion language can arrive before the underlying state has been checked.

## When to reach for it

Use it at a verification or approval boundary: after implementation, after a migration, before a release, or whenever an agent reports that a task is done.

## What one run does

1. Extract the material claims from the completion report.
2. Map each claim to an observable check.
3. Inspect the available evidence.
4. Mark each claim as verified, failed, or unresolved.
5. Report residual risk and the smallest next action.

## Common failure modes

- Treating a successful command as proof of the entire user-visible outcome.
- Repeating an agent’s own completion summary as evidence.
- Hiding unavailable checks inside a generally positive verdict.
- Expanding scope during review instead of separating follow-up work.

## It’s working if

A reviewer can see exactly why a claim is accepted, what remains uncertain, and what should happen next without reconstructing the whole session.

## Where it fits

This is a **Verify**-phase skill. It pairs naturally with a scoped implementation workflow. A public-safe publishing skill may become a downstream step once that capability is actually published.

## Workflow completion

The workflow is successful when: The receiving agent starts from the recorded next action and the resulting change is independently reviewable.

Report the task result, the evidence used to verify it, and any unresolved limitation. If a required verification step cannot be performed, say so instead of treating the workflow as complete.