# Finish your first small task

Use fictional materials to deliver a checkable short report.

## Choose a learning path

Beginners can start with this exercise. Teams can learn the concepts and arrange handoffs. Developers can go directly to the local snapshot lab. In a reading path, the chapter footer leads to the next chapter on that path. There is no need to download the whole catalogue.

- [Beginner: start this exercise](https://harzva.github.io/awesome-bot/handbook-start.en.html?path=start#exercise)
- [Team collaboration](https://harzva.github.io/awesome-bot/handbook-team.en.html?path=team)
- [Developer: local snapshot lab](https://harzva.github.io/awesome-bot/handbook-agents.en.html?path=developer#local-lab)

Before starting, any existing Agent that handles text can do this exercise; no account purchase is required first. Copy for Agent copies context, download saves a file, and import asks a host to read configuration. These are separate actions. Use the import entry available in your actual host.

## Write a fictional weekly report

Copy the entire “Practice task and materials” block below into your existing text-capable Agent to produce the first weekly report draft. This step needs no download, import, real mailbox or project account. Optionally use Status Report Writer role context, subject to the Agent’s existing instructions.

### Practice task and materials

```text
Write a weekly status draft of no more than 120 words from these fictional records.
Goal: deliver a registration page on Friday.
Record A (Wednesday): form page complete; not tested.
Record B (Thursday): desktop tests passed; mobile tests not started.
Record C (Thursday): copy awaits Alex's approval, expected Friday morning.
Output: goal, verified progress, pending acceptance, blockers, next steps.
Acceptance: cite A/B/C; do not equate page completion with full acceptance; mark missing owners as unconfirmed.
Boundary: draft only. Do not publish or contact anyone.
```

The following is a prepared teaching reference, not an actual Bot run. Wording may vary, but preserve the five items and evidence limits. Numbered citations identify the original records.

### Teaching reference excerpt

```text
Goal: deliver the registration page on Friday.
Verified progress: form complete [A]; desktop tests passed [B].
Pending acceptance: mobile tests not started [B].
Blocker: copy awaits Alex, expected Friday morning [C].
Next: arrange mobile testing (owner unconfirmed), follow up on copy, then review acceptance.
```

Incorrect: “The registration page has passed full acceptance.” Targeted revision prompt: “Revise only this sentence: desktop passed; mobile not started; copy pending. Cite B/C and retain other checked content.”

## Check and revise the result

1. Check all five sections and distinguish desktop from mobile testing.
2. Match completion claims to records; remove unsupported sentences or mark them unknown.
3. Name precise gaps, ask the Agent to revise the draft, and save both the task and result.

## Use your own materials

Replace the goal, records, and acceptance criteria, then try a small sanitized sample. Before reading real files or accounts, confirm tools and task authorization in the host. One successful exercise does not certify every account task.

- [Find Status Report Writer](https://harzva.github.io/awesome-bot/?lang=en&bot=awesome%2Fstatus-report-writer)
- [Choose and import](https://harzva.github.io/awesome-bot/handbook-choose-import.en.html)

## Sources

Sources checked: 2026-10-25

- [First-use guide](https://github.com/Harzva/awesome-bot/blob/main/START_HERE.en.md)
- [Exercise role source](https://github.com/Harzva/awesome-bot/blob/main/data/entries/status-report-writer.json)