Task
Work without code: configuration, access, records, operational or documentation steps.
What it is
A task is work that has to happen but does not change code: set up the SMS sender, grant the service access to the calendar, import the clinic list, write the receptionist guide.
Why it matters
Much of what blocks a launch is not code. Tracking it next to the stories makes it visible, owned and checked, instead of remembered the night before go-live.
What goes wrong without it
- Access, configuration and data steps are forgotten until something fails in production.
- Operational changes happen without a second pair of eyes.
What it gives an AI agent
Agents can do many tasks — or prepare them for a person — but some, like granting production access, should need approval. Keeping tasks separate from stories lets the rules differ: approval before, a second check after.
Example: Clinic Booking
| Weak | Strong |
|---|---|
| Calendar stuff. | Grant the booking service read-write access to the clinics' calendar account (needs IT approval). |
How it relates to the rest
- Peer of a story under an epic; subtasks are part of it.
- Can implement a requirement, often a technical or project requirement.
- Planned in a work package.
In Corpole
- Type Task (TK). Workflow: Backlog, Awaiting approval, Ready, In progress, Check, Done.
- Check means a second person checks the result before it is Done.