Reusable Work Brief Prompt
Choose a short source-to-draft brief or a long-task brief with budgets, checkpoints and stop rules. Includes retained v1.1 text.
What this prompt does
Short or long work
Choose the short source-to-draft brief or the longer task contract with budgets and checkpoints.
Source and action boundaries
Name the controlling records, permitted actions and conditions requiring a decision.
Reviewable handoff
Check the actual artifact, preserve missing facts and distinguish finished work from a partial result.
What to provide & what you get
- Input
- One task, ordered sources, intended output and review rules; for long work, add action limits, budget, checkpoints and stop conditions.
- Expected output
- The requested artifact or decision, with actual verification evidence and a clear partial handoff when the task cannot finish.
How to use
- Use the short brief for a bounded draft; choose the long-task version for work across several files or tools.
- Fill the actual sources, outputs and checks. For long tasks, also define the relevant budget, stop conditions and permissions.
- Inspect the resulting artifact and the checks actually run. A written completion statement does not establish that an external action happened.
Check the result: Match the delivered work to the brief and its source records. The current templates do not establish model reliability or provide missing tools.
Short-task brief
v2.0Edit the inputs below, then copy into your AI tool with the requested source material.
Before you start
- Paste into an AI tool that supports the requested text, files or images.
- Provide the bracketed inputs or attach the requested source material.
Long-task brief
Use this version when one deliverable spans several sources or tools and needs budgets, checkpoints, change receipts and stop rules. The text is structure-checked and has not been run in a model.
Retained long-task v1.1 · v1.1
Historical v1.1 text retained unchanged. Its budget and stop additions were checked for structure, not model behavior. The earlier response-only v1.0 case does not validate v1.1 or either current v2.0 brief.
Choose the right brief
Use the short brief when the source facts are already supplied and the job is one draft, extraction or response. Use the long-task brief when the work can diverge across sources, tools or changing requirements. Remove limits and checkpoints that do not serve the actual task.
A filled long-task example
Illustrative source facts: build B-17 has 42 passing unit tests and a staging deployment; its keyboard check is unrun and production is not authorized. These supplied facts require HOLD, not a production release.
One earlier v1.0 response-only run returned HOLD on that frozen case. It did not execute tools or deploy anything. The later v1.1 budget-and-stop additions and the current v2.0 texts have not been model-tested.
OUTCOME
Return a release decision for build B-17 and a list of remaining gates.
SOURCE OF TRUTH
1. ci/build-B-17.json for test status
2. staging/deploy-B-17.json for staging state
3. release-policy.md for required checks
Missing required evidence means HOLD.
DELIVERABLES
A Markdown decision note for the release owner. No deployment.
BOUNDARIES
May inspect supplied records. Requires separate approval for production.
BUDGET AND STOP RULES
Use only the supplied files. Stop after the decision note. Stop immediately
if a required record is missing or the sources conflict.
QUALITY BAR
Name every required check as passed, failed, or unrun; keep staging and
production status separate. Fill the six long-task fields
- Outcome: name the artifact or decision that must exist.
- Source of truth: list controlling files or records and the rule for a missing or conflicting source.
- Deliverables: name the format, destination and intended reader; distinguish a draft from a publication.
- Boundaries: specify authorized actions and any separate approval needed.
- Budget and stop rules: name relevant time, cost or retry limits and when to return a useful partial result.
- Quality bar: connect each check to a concrete failure, such as an unsupported figure, broken calculation or wrong destination.
Read the receipts and final handoff
The long brief requests a brief receipt, useful checkpoints, a change receipt when requirements move, and a final handoff. Check that the account of delivered, verified and unverified work matches the actual artifacts.
The host application still owns tool access, cancellation, permissions and duplicate-action controls. A prompt can ask for accurate reporting; it cannot enforce those controls.
Prepare the source before pasting
Replace every required placeholder and remove irrelevant fields. Keep a retained copy of the facts, dates, exclusions and policy wording used for the work. Use the account and workflow approved for any confidential material.
Compare the output with its source
Check names, numbers, dates, negations, quotations and commitments against the retained source. A final-check instruction helps expose omissions but does not prove correctness.
Keep the historical evidence in scope
The earlier short-brief filled-memo observation and the long-brief v1.0 B-17 response are separate historical cases. They are not tests of either current self-contained v2.0 text, and provide no cross-model accuracy rate.
Choose checks for the deliverable
For a spreadsheet, inspect formulas and recalculated values. For a browser flow, inspect keyboard behavior and the destination state. For a publication, verify its actual public state. Keep stable team rules in project instructions and the current task facts in the brief.
Keep domain-specific legal, medical, financial, privacy and security decisions with qualified owners; the brief does not replace their review.
Use only approved, relevant sources. Return a partial handoff when the stated evidence boundary or budget prevents completion.
Keep in mind
- The short v2.0 and long-task v2.0 texts are structure-checked; neither has a retained run of that exact current text.
- A prompt cannot grant tool access, enforce external permissions, cancel a running operation or prevent duplicate side effects.



