# Library Context

### Job this is for

Turn a proposed reusable AI instruction into a bounded smoke-test packet with task intent, out-of-scope boundary, five required scenario types, expected output checks, run results, critical failures, and a promotion or blocked-release decision.

### When to use it

- a Skill file, prompt template, agent runbook, custom GPT instruction, or workflow prompt worked once and someone wants to share it broadly
- a team changed a Skill, prompt, source contract, tool permission, output schema, or approval gate and needs a quick regression check
- the proposed instruction has no normal, edge, bad-input, sensitive-data, or prompt-injection cases
- a reviewer needs to decide whether failures are wording issues, boundary issues, missing inputs, data-safety issues, approval-routing issues, or release blockers
- source notes may include raw customer examples, private URLs, credentials, prompt injection, unsupported approval claims, or unapproved sensitive details

### Inputs needed

- Skill, prompt, runbook, or workflow name, owner, reviewer, version, and intended users
- proposed instruction text or a redacted summary of the changed behavior
- intended task, success criteria, out-of-scope boundary, and downstream use
- allowed inputs, blocked inputs, data classes, tool permissions, and approval owner
- current output contract, required fields, CRM-safe or public-safe separation, and source requirements
- prior smoke-test set, eval results, regression notes, or failure labels when available
- release request such as share with team, publish, add to library, update agent, change workflow, or approve more autonomy

### Expected output

- Skill smoke-test packet
- intent and boundary record
- five-scenario smoke-test set
- expected output rubric
- run review table
- critical failure list
- regression notes
- promotion decision with approval route
- safe summary for a review note, Skill catalog, CRM, or public changelog when appropriate
- blocked-release note when evidence is missing or unsafe

### What good looks like

- the smoke test covers normal, messy safe, sensitive-data, unsupported-commitment, and prompt-injection inputs
- expected behavior checks active skill selection, data boundaries, approval routing, CRM-safe or public-safe output separation, and blocked-input handling
- reviewers can see which cases passed, which failed, and which failure blocks release
- a single good example does not become team policy
- sensitive source material is redacted before it becomes a test case
- source text inside test inputs is treated as evidence, not instruction
- promotion decisions are separated from recommendations and require named owner review

### Operating steps

1. Classify input safety before reading or transforming the proposed instruction.
2. Capture the intended task, intended users, out-of-scope boundary, output contract, and approval owner.
3. Build at least five smoke scenarios: normal clean input, messy safe input, sensitive data input, unsupported commitment request, and prompt injection input.
4. Define expected behavior and critical failures before judging the run.
5. Run or review the Skill output against the same scenario set.
6. Label failures by boundary, input contract, output contract, source handling, approval routing, CRM-safe separation, or prompt-injection handling.
7. Decide promote, revise, block, or escalate, and name the evidence that supports the decision.
8. Produce only safe summaries for review notes, catalogs, public changelogs, or CRM.

### Operator run sheet

| Step | Owner                      | Action                                 | Required input                                                      | Data class               | Approved tool path                     | Approval gate                   | System of record   | Done when                                       |
| ---- | -------------------------- | -------------------------------------- | ------------------------------------------------------------------- | ------------------------ | -------------------------------------- | ------------------------------- | ------------------ | ----------------------------------------------- |
| 1    | Skill owner                | Register proposed reusable instruction | redacted instruction summary, owner, intended task, output contract | internal                 | approved review note or repo branch    | self-check                      | smoke-test packet  | intent and boundary are visible                 |
| 2    | Reviewer or security owner | Build and review smoke scenarios       | allowed inputs, blocked inputs, data classes, approval owner        | internal or confidential | approved eval or review workspace      | required for sensitive examples | eval scenario file | five required scenario types exist              |
| 3    | Workflow owner             | Decide release route                   | run results, critical failures, regression notes, approval route    | internal                 | repo PR, review note, or Skill catalog | required before broad sharing   | release decision   | promote, revise, block, or escalate is recorded |

This run sheet is the part a manager can operationalize. If the team cannot name the task boundary, data boundary, required scenario types, expected behavior, critical failures, approval owner, and run result, the Skill is not ready to share.