# Pocket Product Delivery Checklist
## MCP Opportunity & Offer Kit

Use this before releasing a self-serve kit or handing over a configured pilot. Mark each item **Pass**, **Revise** or **Not applicable**, and keep evidence for anything that matters to acceptance.

**Product/version:** [name and version]  
**Reviewer:** [person]  
**Review date:** [date]  
**Intended buyer:** [specific audience]

## Promise and package

- [ ] The product description names a concrete result and the audience it serves.
- [ ] The included files match the description.
- [ ] Prerequisites, supported tools and setup effort are clear.
- [ ] Examples are labeled fictional where applicable.
- [ ] The package makes no unsupported earnings or performance claim.
- [ ] Support boundaries and usage terms are stated clearly.

## First-use experience

- [ ] A start page tells the buyer which file to open first.
- [ ] A worked example shows a completed result.
- [ ] Every placeholder is easy to identify and replace.
- [ ] Instructions explain what to do with missing information.
- [ ] Downloaded files open successfully and links resolve.
- [ ] Another person can complete the first useful step without an explanation from the creator.

## Connection quality, if the product includes an integration

- [ ] The server or service comes from the intended provider.
- [ ] Required account and permissions are documented.
- [ ] The workflow uses only the approved source and task scope.
- [ ] Valid input, no matches, invalid input and unavailable access have expected results.
- [ ] Restricted information remains restricted.
- [ ] Source content is treated as information, not as authorization to perform unrelated actions.
- [ ] The final assistant output preserves source links, dates and uncertainty.
- [ ] A manual fallback or recovery step is available.

## Delivery and ownership

- [ ] Acceptance criteria are visible beside the deliverable.
- [ ] Open issues have an owner and next action.
- [ ] Maintenance responsibilities are named.
- [ ] The change log records the current version and relevant updates.
- [ ] Access is closed or retained according to the agreement.
- [ ] The buyer knows how to request support or a scope change.

## Release decision

**Ready to release:** [yes/no]  
**Unresolved issues:** [issue, owner, date]  
**Evidence reviewed:** [example, test record, walkthrough]  
**Next review date:** [date]

### Suggested buyer handoff note

“Your [product] is ready. Start with [file]. The included example shows [result], and the worksheet helps you create your own version. This release covers [scope]. The known limitation is [limitation and recovery step]. For help within the included support period, use [channel].”
