Use an existing backlog
Preserve the project’s current backlog as a task source without rewriting its history or meaning.
An existing backlog remains a project-owned source of work. TCAF maps it into the canonical project evidence without replacing its identifiers, history or intended meaning.
During adoption
The agent should identify:
- the authoritative backlog file or system;
- task identifiers and current statuses;
- links to specifications, decisions or dependencies;
- completed work that must remain historical evidence;
- open work that can become a future Task Contract;
- inconsistencies that require developer review.
Do not silently normalize terminology or rewrite completed tasks to fit a new template.
Run a backlog task
When the developer selects one item, provide the task source to TCAF through the host adapter or a local input file:
tcaf task --target <project> --input <task-source>Alternatively, supply a precise inline request that identifies the backlog item:
tcaf task --target <project> --request "Run backlog item B-016"The selected item is a source, not yet an implementation authorization. The agent must inspect pertinent project evidence and produce a Task Contract for review.
Preserve backlog ownership
TCAF must not:
- renumber tasks without authorization;
- mark work complete before acceptance;
- delete historical entries;
- merge independent tasks for convenience;
- expand acceptance criteria silently;
- rewrite the backlog while implementing code unless that update is part of the approved scope.
After the task
Update backlog status only after the implementation and evidence have been accepted. Documentation or status reconciliation may be performed as a separate authorized step so that code review is not mixed with administrative changes.