Run a development task

A TCAF task is one bounded unit of engineering work. If the requested outcome is broader than one coherent task, use tcaf plan first.

Start the task

tcaf task --target <project> --request "<requested change>"

Or use an existing task source:

tcaf task --target <project> --input <task-source>

Required sequence

1. Identify the authoritative task source.
2. Inspect only the project evidence and implementation pertinent to the task.
3. Resolve material ambiguity before implementation.
4. Produce a Task Contract with objective, allowed edit surface, preserved areas, acceptance criteria, checks and stop conditions.
5. Obtain developer review and approval.
6. The AI can execute the approved work inside that boundary, using the smallest coherent preservation-first change.
7. Run or report the smallest relevant checks.
8. Present the diff, evidence, limitations and outcome.
9. Wait for developer acceptance before status updates or commit.

The developer remains in control

The developer can edit code directly, replace an approach, clarify the request, stop the AI or perform part of the work manually. Those edits become current repository state and must be re-read before the AI continues.

Scope discipline

A task does not authorize opportunistic refactoring, unrelated dependency changes, broad formatting, silent backlog updates or Git operations.

If new work is discovered, classify it as a clarification, correction, amendment, separate task or blocker instead of absorbing it silently.

Verification

Only executed evidence supports a verified claim. Pending or developer-run checks must remain visible.

If repository or project state changes later outside the current run, use tcaf sync before relying on stale state.