ait task
Start Plan-bound work, inspect readiness, and complete the Task through its configured scope.
Audience: Coding agents and maintainers
Role#
Normally run by the coding agent. The user states the desired result and constraints rather than manually driving Task bookkeeping.
Purpose#
ait task binds sprint intent, Change lineage, a feature Line, a managed workspace, and final closeout. In sprint mode, start from one exact taskable Markdown item.
Syntax#
ait task start --from <sprint-card>#<exact-ref> --intent <intent>
ait task audit <task-id>
ait task land <task-or-change-id>Example#
ait task start \
--from docs/sprints/password_visibility.md#login/password-visibility/implement \
--intent "Add accessible password visibility control"The final output includes the Task, Change, and exact cd command. All code work belongs in that printed workspace.
Audit and closeout#
ait task audit reads the Task's readiness and closeout state. ait task land uses the recorded workflow scope. A remote Task must already have a selected Patchset with completed readiness evidence.
Failure and recovery#
If startup partially succeeds, keep the printed identifiers and inspect the Task before retrying. If a workspace is missing, use the worktree recovery surface; do not create a second Task for the same open sprint item unless the original lineage is explicitly resolved.