<!-- Prompt library entry · from Chapter 32 of The Product 360 Handbook -->

# Prompt · [Name]

**Owner:** [Name]   **Version:** [v1.0]   **Last reviewed:** [Date]   **Status:** Draft / Tested / In use / Promoted to skill / Retired

## Task
What this prompt does and when to use it:

## Inputs required
- Files or pasted material:
- Connectors (and scope):

## Context to attach
Context pack sections: [brief / personas / metrics / strategy / glossary / house style / other]

## Data classification allowed
Public / Internal / Confidential / Restricted (never)
Approved tools only. Remove personal identifiers where the task doesn't need them.

## Prompt
[Prompt text with [placeholders]]

## Output format
[Structure, length, headings, table columns]

## What good looks like
[Two or three success criteria, written so a colleague could judge them]

## Verification checks (pass or fail)
- [ ] Every number traces to a named source and date
- [ ] Every quote has a source ID and appears verbatim
- [ ] No commitments, dates or scope I didn't provide
- [ ] [Task-specific check]

## Known failure modes
- [What the model tends to get wrong here, and how the checks catch it]

## Test inputs
1. [Real past input, with the output you'd accept]
2.
3.

## Usage log
| Date | User | Check failures | Editing effort | Notes |
|---|---|---|---|---|
| | | | | |

## Promote to skill?
Yes when two or more PMs use it weekly and its checks have been stable for a month.
