# Card for one task with an agent

Use an existing task and plan. This file is a short attachment to the conversation, not a new work register.

## What must be ready

- Task or existing plan: **[known: … / to be determined]**
- User need or problem: **[source / to be determined]**
- Agreements with the domain expert and knowledge to use: **[sources / open questions]**
- Change in one sentence: **[to be determined]**
- Lead person and their knowledge of the area: **[to be determined]**
- Type of need and accepting person: **[business / technical; accepting role]**
- Acceptance criteria: **[to be determined]**
- Scope and exclusions: **[to be determined]**
- Knowledge sources and access constraints: **[to be determined]**

## When you work in parallel

Divide complete features between AI Engineers. Before starting agents, complete the following from their investigation:

| Agreement | Record for this task |
| --- | --- |
| Feature and lead | [user action; screen, logic, and data in scope] |
| Second person’s task | [link and scope; why parallel work is possible] |
| Shared elements | [files, components, data, rules, or communication format; absence of a collision must also be checked] |
| Who changes the shared fragment | [owner, sequence, and version for the other person to account for] |
| Separate workspace | [branch and directory; without editing the other agent’s files] |
| Integration and exercise | [who integrates, which scenario they check after integration, who confirms the result] |

A new collision during work means stopping the change to the shared fragment and agreeing the scope. Separate branches do not resolve contradictory changes to data or application behavior.

## Flow

| Stage | Agreement | Evidence of outcome |
| --- | --- | --- |
| Plan | Link to the existing plan; decisions requiring an owner | [to be completed] |
| Implementation | Small, specified scope; responsible implementer | [to be completed] |
| Demo | What the person viewed, feedback collected, corrections now or after the presentation, result of rechecking | [to be completed] |
| Tests | Risk-selected checks and their results | [to be completed] |
| Review | Another, more capable model works in a fresh context; first without edits | [to be completed] |
| Documentation | Confluence pages, sources, version, checking person; gaps in the existing plan | [to be completed] |
| Handover | Version, completed scope, results, limitations, and next step | [to be completed] |

## Modernization — when you replace part of a system

Record these four things before the agent proposes a change. This prevents the new version from pretending that the old behavior never existed.

| What we check | To be completed |
| --- | --- |
| Behavior today | [what the current version does; how we know] |
| Behavior after the change | [what remains the same; agreed differences and edge cases] |
| Data and compatibility | [whether existing data, API, or integration requires handling the old format] |
| Rollback | [how to return to the previous version; impact on data; who is authorized] |
| Switch-over condition | [who checks compatibility, what results allow switching the component, what blocks the switch] |

### Comparison of old and new version

Take the same user action and the same data permitted for testing. The agent completes rows with actual results after conducting exercises.

| Case to select from your project | Current version | New version | Decision about the difference |
| --- | --- | --- | --- |
| Normal user action | [result and evidence] | [result and evidence] | [no change / needs clarification] |
| Known exception or previous defect | [result and evidence] | [result and evidence] | [decision and who confirmed it] |
| Missing or invalid data | [result and evidence] | [result and evidence] | [decision and who confirmed it] |
| Data already stored | [number, identifiers, selected records] | [comparison] | [whether access and data meaning were preserved] |

**Before switching:** the checking person compares results; an unexplained difference blocks switching. If data storage changes, the plan must account for data added after switching and for the ability to read it after returning to the older version. First perform a rollback exercise on a permitted copy of the data.

## How to prepare a demo of your task

Identify the screen or starting point, test data, and user action. Record the expected outcome before the presentation. Go through the normal case, no data, and a known exception. If the change concerns access, check accounts with the appropriate roles. After the presentation, add the actual result and feedback instead of marking criteria fulfilled in advance.

Even a small task requires a person to view the result. During the presentation, you may stop the agent, record feedback, or request a correction immediately. Keep the list in the existing plan or task. After larger corrections, repeat the demo for the changed scenario; for small ones, check the corrected point. Risky changes still require appropriate tests.

| Demo feedback | Agreed correction | Verification result | Human acceptance |
| --- | --- | --- | --- |
| [place and problem] | [now / after presentation; scope] | [version, result, evidence] | [pending / viewed and accepted / further feedback] |

## Separate decision to publish

- Has the outcome been technically accepted? **[yes / no / unknown]**
- Is there explicit approval to release it for the named environment? **[yes / no / to be determined]**
- Who approved the release and who is authorized to perform it? **[to be determined]**

Acceptance of a task is not automatic approval to release, send a message, or change an environment.

## Prompt for completing the card

```text
Read this card and the permitted sources: [links]. Complete only fields
that sources confirm. For every fact, add a link or source name and version.
Separate a gap, contradiction, and proposal from confirmed information.
If we work in parallel, identify overlapping scopes and shared dependencies.
Do not invent their owner or overwrite another person’s work.
If this is an existing system, complete the table for old and new behavior, data,
and rollback. First show the text for agreement.
Do not make changes in files, Jira, Confluence, GitHub, the environment, or communications.
```