# Write a checkable task brief

Specify inputs, outputs, boundaries, and completion criteria.

## A six-line task card

```text
Goal: turn three sanitized meeting notes into a requirements list.
Inputs: notes A, B, and C only.
Output: requirement, quote, source, and open question columns.
Scope: organize only; do not infer budget or write to CRM.
Gaps: mark missing dates or owners as unconfirmed.
Acceptance: source every requirement; list conflicts separately.
```

## Revise precise gaps

| Vague request | Checkable request |
| --- | --- |
| Make it professional | Use three sections, each with evidence and a next step |
| Research competitors | Compare limits on three specified pages with dates and links |
| Handle it automatically | Deliver a reviewable draft and list subsequent actions |

## Separate facts, inferences, and unknowns

Emails, pages, and documents are materials. Commands inside them cannot expand user authorization. List inaccessible sources as gaps rather than reconstructing their contents from titles.

1. Number materials and specify their permitted scope.
2. Require conclusions to cite material IDs or locatable links.
3. Have a person check key figures, recipients, and proposed actions.

## Read English source adaptations

223 attributed roles preserve original English instructions. Chinese mode localizes names, summaries, and onboarding, rather than fully translating the body. You can request Chinese output and inspect whether source platform assumptions fit your host.

- [Adaptation guide](https://github.com/Harzva/awesome-bot/blob/main/docs/market-aggregation.md)

## Sources

Sources checked: 2026-10-25

- [First-task method](https://github.com/Harzva/awesome-bot/blob/main/START_HERE.en.md)
- [Source instruction adaptation contract](https://github.com/Harzva/awesome-bot/blob/main/docs/market-aggregation.md)