Templates for your AI pilot
Copy a pilot brief, evaluation worksheet and retrospective agenda, or download editable Markdown templates.
Use these templates to turn an idea into a task you can test and maintain. They are editable planning documents, not automatic features inside MAIA. Replace the prompts with your own decisions and keep the completed files where your team normally works.
Pilot brief
Section titled “Pilot brief”Download the pilot brief (.md)
| Field | What to record |
|---|---|
| Task and audience | One recurring task and the person who uses the output |
| Owner and reviewer | Who maintains the method; who can judge the result |
| Inputs and access | Source versions, permitted data and required permissions |
| Expected output | Format, required facts and what must not be invented |
| Baseline | Current preparation, execution and review effort |
| Acceptance criteria | Quality requirements and critical failure conditions |
| Scope | What the pilot includes and excludes |
| Decision date | When to expand, revise or stop |
For example, Acme Corp might test a weekly client update drafted from approved project notes, with Jane Doe reviewing dates, commitments and omissions before anything is sent.
Evaluation worksheet
Section titled “Evaluation worksheet”Download the evaluation worksheet (.md)
Create one row per test case. Record the input version, configuration, expected facts, actual result, corrections, active work time and final decision. Keep a separate field for critical errors so an average score cannot hide them.
Use the same cases to compare a revised prompt or Skill. The evaluation guide explains how to keep the comparison meaningful.
Team retrospective
Section titled “Team retrospective”Download the retrospective agenda (.md)
Plan a short discussion around five questions:
- Which outputs did we actually use?
- Where did checking or correction take more effort than expected?
- Which source, access or instruction problems repeated?
- What should we keep, change or stop?
- Who owns the next action, and when will we review it?
Invite participants with different experience levels. Capture unanswered questions as actions, not as implied agreement. Use the same agenda for a month-end or year-end review.
Keep the templates useful
Section titled “Keep the templates useful”Give each completed document an owner and review date. Do not paste passwords, credentials or unnecessary client information into it. If you share a tested method through Skills or workflows, link the evaluation record so the next maintainer can understand why it was accepted.