Skill / Your working draft

Builder-exit handover test

Unsaved changes Only in this tab

From builder-exit-handover-test · v1.1 · Original unchanged

The work, in your words.

Purpose

Use when

Inputs

What must someone bring to the work?

Input 1 name

Input 1 description

Required inputText

Method

A clear sequence that someone can follow.

Step 1

## Workflow and roles

Workflow:

Builder:

Operator (runs the normal route):

Decision owner (resolves cases that need judgment):

Support owner (keeps access, instructions and settings usable):

If one person holds more than one role, write that down. It is allowed, but it should be visible.

## Readiness questions

The operator should be able to answer each of these from the workflow’s own notes or screens. Mark each Yes, Partly or No, and say where the answer lives.

1. What starts the workflow?
2. What inputs or source records does it need, and where are they?
3. What does a good output look like? Is there an example?
4. When must the route stop or pass the work to a person?
5. Where is the accepted result or correction recorded?
6. Who has access to the tools and accounts it uses, and who can remove that access?
7. What does it cost each month, and who pays for it?

## Recovery cards

Write one card for each of the three most likely failures.

- Failure:
- Signal (how someone would notice):
- Immediate safe action:
- Escalation owner:
- Where the fix is recorded:

If the only safe action on a card is “ask the builder”, the workflow is not ready.

## Practice cases

Run each case with the operator narrating what they see, what they trust, what they would do and what they would record.

1. A normal case
2. An incomplete case (a missing input or unclear request)
3. An exception that should reach the decision owner

For each case, note every point where the operator needed the builder’s private knowledge.

## Result

- Ready to run without the builder
- Ready with named fixes, to be retested on [date]
- Not ready; keep the builder involved until [condition]

Fixes to make, each with an owner and a date:

Signed off by (decision owner):

Output

Quality checks

Limitations

Package details

Summary

Package name

Lowercase letters, numbers and hyphens. Used only for the package folder.

Ask for a change AI unavailable

What would you like to refine?Context for a future request

No profile selected. Nothing is sent. Manual editing remains available.

Design review: candidate comparison

A labelled synthetic candidate demonstrates review and stale-change protection. No model is called.

Inputs

Method

Sample