Implementation
After decisions are locked, AuthRight Harness hands work to coding agents. You are not locked into one tool for that step.
A handoff channel is simply the path you pick for that handoff—today either OpenSpec or Agent Plan-mode. AuthRight keeps the identity decisions; the channel turns them into a work package agents can implement.
/auth:to-openspec and /auth:to-plan are two handoff commands for the same locked change—pick one. Neither is a mode of the other (same idea as Decide: /auth:explore vs /auth:change).
| Option | Status | Command | What it does |
|---|---|---|---|
| OpenSpec | Supported | /auth:to-openspec | Propose-first: AuthRight feed/claims + OpenSpec propose → openspec/changes/… when the OpenSpec tool is installed (openspec on your PATH—not AuthRight’s authright) |
| Agent Plan-mode | Supported | /auth:to-plan | Writes .authright/changes/<dir>/agent-plan/ for your editor’s Plan mode |
| Superpowers and similar kits | Planned | — | Possible later options—not in today’s CLI |
AuthRight does not replace these tools, does not run their apply/archive loops, and does not require their packages to install AuthRight.
How handoff fits
AuthRight Harness Handoff (pick one) Coding agents
(decide + contract) → (work package) → (write app code)
↑ │
└────────────── /auth:review ←─────────────────────────┘After Decide confirm and request-match pass, check whether OpenSpec is installed:
- OpenSpec present: pick
/auth:to-openspecor switch the chat to Plan mode and run/auth:to-plan - OpenSpec absent: use Plan mode +
/auth:to-planonly./auth:to-openspecstops without writing underopenspec/changes/(AuthRight will not invent an OpenSpec package for you)
If you exported both ways on the same change, implement from one package for this session (OpenSpec apply or Plan Build)—do not mix the two as the source of truth.
Related
- Commands —
/auth:to-openspecand/auth:to-plan - Reviewing decisions
- Getting started