Task Aging
Unfinished task age and time in the current column, with owner and due-date context; excludes archived and cancelled tasks from active workload.
Complete and revisit work
Preserve a finished outcome when work needs another cycle.
3 stages · 0 approvals
Roles and responsibilities
Process steps
Follow the process from start to finish. Select a step to see who acts and what changes.
Record completion
The move service consumes an Approved TransitionRequests decision once, rechecking current revision, blockers, mandatory checklist policy and destination capacity. Mark Applied only when the move commits. Entering Done stamps CompletedAt and appends one Completed TaskEvents row for Task plus CycleNumber. An approved request with no free slot remains approved but unapplied until it can be safely retried; approval alone is not completion.
Reopen or archive
Board Owner can reopen completed work through an allowed current workflow move with a recorded reason. Preserve the original completion event, increment CycleNumber and start a new work cycle without rewriting earlier timings. Recheck WIP and applicable approval policy for the destination. Archiving removes a task from active lists but preserves its relationships and event history; it cannot be used to remove evidence from an open review.
Review board outcomes
Board Owner reads BoardSnapshots and event-based reports with their time window, timezone and DefinitionVersion. Distinguish completed cycles from reopened work and unfinished aging. An empty result has no measured cycle time. Compare owners’ workload in context; task counts alone do not establish productivity. Viewer receives only the permitted board reports, and Guest has no board-wide analytics or export.
Approvals and controls
0 approvals required in this process
- Reopening follows current workflow, approval and WIP rules.
- A current deadline change cannot rewrite closed-cycle performance.
- Archiving cannot remove evidence from an open review.
Records and postings
| Stage | Records | Effect |
|---|---|---|
| 1 Record completion | TasksTaskEventsTransitionRequests | Freeze completion for this cycle |
| 2 Reopen or archive | TasksTaskEvents | Retain history and begin a new cycle when needed |
| 3 Review board outcomes | BoardSnapshotsTaskEvents | Separate completions, reopens and aging |
Process reports
All reportsCycle Time
Observed elapsed start-to-completion hours by task cycle, including explicit rework cycles and null where an observation is incomplete.
Ownership and Workload
Active task count by accountable owner and priority within board scope; task count is not a productivity ranking.
Board Flow Summary
Dated snapshots by board and reporting window: active work, overdue work, completed cycles and reopened cycles with the definition version.
Due-Date Performance
Compare retained completion events with the due date applicable at that event; later due-date edits cannot rewrite earlier on-time results.
Review Turnaround
Time from current review request to its accepted decision, separating pending, rejected, expired and applied outcomes.
Run by an agent
Agent support
This system owns daily boards, checklists, dependencies, controlled handoffs and scoped collaboration. Customer invoicing, payroll, formal sprint commitments and resource-cost planning are outside its scope. Proto prepares work and explains blocked transitions; it cannot supply independent approval.
# Example after configuration
$ curl -fsSL https://www.erp.ai/skill.md | paste into your agent
› complete and revisit work · record completion on Tasks, TaskEvents, TransitionRequests
✓ The move service consumes an Approved TransitionRequests decision once, rechecking current revision, blockers, mandatory checklist policy and destination capacity.
› complete and revisit work · reopen or archive on Tasks, TaskEvents
✓ Board Owner can reopen completed work through an allowed current workflow move with a recorded reason.
› complete and revisit work · review board outcomes on BoardSnapshots, TaskEvents
✓ Board Owner reads BoardSnapshots and event-based reports with their time window, timezone and DefinitionVersion.
Other processes
3 moreSet up and capture work
Create the board boundary and bring useful work into it.
3 stages · 0 approvals
Collaborate and follow up
Share the right context and keep time-sensitive work visible.
3 stages · 0 approvals