Feature Workflow

Scenario#

The feature example matches the interactive Demo: add an accessible password-visibility control while preserving the login API and keyboard behavior.

The user supplies the request. The coding agent carries the repository workflow.

Scope the work#

The agent writes one sprint card with one exact taskable item.

# Password Visibility [plan-ref: login/password-visibility/root]

- [ ] Add the accessible control and focused tests. [ref: login/password-visibility/implement]

It then starts the bound Task from that exact item.

ait task start \
  --from docs/sprints/password_visibility.md#login/password-visibility/implement \
  --intent "Add accessible password visibility control"

The output supplies the Task, Change, and workspace path.

Implement in the bound workspace#

The agent enters the printed path, updates the control and focused tests, and runs the repository-owned validation. AIT does not guess a framework or invent a test command.

src/LoginForm.tsx
tests/LoginForm.test.tsx
3 tests passed

Record the result#

After the checks pass, the agent records the code state.

ait snapshot create --message "Add accessible password visibility control"

Remote-backed work then uses the guided readiness command until the selected Patchset has the required CI, attestation, review, and policy evidence.

ait workflow ready <change-id> --apply

Complete and verify#

The agent finishes with the Task command from the generated repository instructions, then verifies Task, workspace, Line, and sprint-item closeout.

ait task land <task-or-change-id>
ait task audit <task-id>

Use the Interactive Demo to watch the same flow, or open the ait task reference for command details.