ait plan

Role#

Normally run by the coding agent under the exact scope printed in the repository's generated instructions.

Purpose#

ait plan records versioned Markdown lineage. In sprint mode, one exact open checklist item becomes the Task binding; ordinary documentation can be synced without becoming a Task.

Syntax#

ait plan sync <markdown-file-or-dir> --local
ait plan sync <markdown-file-or-dir> --remote origin

Use only the scope that matches the effective repository configuration. The initial ait task start --from invocation owns exact-file synchronization for its bound sprint item.

Example#

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

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

ait plan sync docs/architecture.md --local

Output#

Sync reports the Plan identity, revision, action, and publication scope. Plan views can inspect items and revisions without changing them.

Failure and recovery#

Do not copy a Plan ID into task start or hide a Markdown checkbox update in a code Snapshot. When remote closeout leaves the checklist update separate, edit the exact bound item and sync that card in the configured remote scope.

Related#

• Core Concepts
• ait task
• Feature Workflow