Automation Agent: Story-by-story Implementation with arqix

A coding agent (or automation workflow) must execute tasks deterministically, within scope, and with machine-readable diagnostics.

Goal¶

Implement one user story at a time with consistent documentation, trace markers, and verification

loops.

Steps¶

1. Read the plan for a single story (scope in/out, acceptance criteria).
2. Create required docs via templates (doc new) instead of manual file creation.
3. Implement code changes and tests.
4. Add trace markers:
5. arqix:implements REQ-xxxx
6. arqix:verifies REQ-xxxx
7. Run the blessed verification loop (local equivalent of CI):
8. fmt
9. lint
10. trace scan
11. trace coverage
12. Fix only within scope. If ambiguous, stop and report blockers.

Outputs¶

• Story-complete PR/commit: code + tests + docs
• Traceable linkage between REQs, code, and tests
• Deterministic verification outputs

Failure Modes¶

• Non-deterministic reports and noisy diffs.
• Missing defaults (IDs, routing) causing guesswork.
• Diagnostics without source locations.

Related Commands¶

• arqix doc new <kind>
• arqix fmt
• arqix lint run
• arqix trace scan
• arqix trace coverage
• arqix trace check REQ-xxxx (assist)

Automation¶

• just: just verify during the loop, just ci before the PR