WORKFLOW / THREE CLIs
GUIDANCE-FIRST WORKFLOW
The director-mode and session-relay core skills keep bundled fallbacks in plugin-only installs. Same-provider work uses native resume; cross-provider continuation begins a new receiver-native session with an unreviewed-by-default packet.
BOUNDARY / NATIVE CONTROLS
Director Mode Lite adds no hidden approval layer, deny rule, forced workflow, or implicit permission change. director-open is a separate trusted-workspace choice.
METHOD / EVIDENCE
Use the smallest stage that moves the task forward, then make the evidence visible before continuing.
State the goal, relevant context, constraints, done-when evidence, and unresolved questions.
Artifact: a reviewable task briefAsk one CLI to inspect only the files and documentation needed for the next decision.
Artifact: cited files and current behaviorImplement the smallest coherent change that can satisfy one acceptance outcome.
Artifact: focused diffUse repository tests, lint, type checks, build, and review requirements—not a generic success label.
Artifact: commands and observed outputCompare evidence with done-when. Continue only when another bounded step is justified.
Artifact: explicit decision and remaining riskPORTABLE / BRIEF
The brief is intentionally small enough to survive a CLI handoff without dragging an entire transcript behind it.
EXAMPLE / PLAIN TEXT
Paste or adapt this brief in any supported CLI. Add repository paths and real commands before implementation.
Goal: Add one observable behavior.
Context: List the files, docs, and failing evidence that matter.
Constraints: Preserve public APIs and native CLI safety controls.
Done when: Name the tests, lint, build, and diff evidence required.
Open questions: Record uncertainty instead of hiding it.ADAPTERS / NATIVE SURFACES
Keep durable guidance in the native project surface and task details in the active prompt.
| CLI | DURABLE GUIDANCE | SESSION USE | VERIFY WITH |
|---|---|---|---|
| Claude Code | CLAUDE.md and installed Claude assets | director-open claude or native launch | Project checks + diff |
| Codex CLI | AGENTS.md and installed Codex assets | director-open codex or native launch | Project checks + diff |
| Grok Build | .grok agents and compatible assets | director-open grok or native launch | Project checks + diff |
HANDOFF / SESSION-RELAY
session-relay creates director-handoff/v2, reads v1, records multi-hop lineage with --parent, and compares packet evidence with the live worktree through status --json. Packets default to review_status: unreviewed; validate and status do not mark them reviewed.
.director-mode/bin/director-doctor --json --no-probe
.director-mode/bin/director-relay create \
--from claude --to codex \
--goal "Finish one bounded outcome" \
--summary "Verified state only" \
--next "First concrete next step" \
--verification "Command and observed result"
# Later hop: repeat create with --parent
.director-mode/bin/director-relay validate
.director-mode/bin/director-relay status --json
.director-mode/bin/director-relay continue --to codexSummarize verified facts, changed files, checks run, results, and remaining uncertainty.
Remove speculation, secrets, irrelevant transcript, and unsupported success claims; record review explicitly only after doing it.
Stay with native resume for the same provider, or start a new native session when crossing providers.
The receiving CLI checks current files, Git state, and evidence before continuing.
DECISION / HUMAN-REVIEWABLE
Stopping is a normal outcome, not a failure of automation.
Done-when evidence is present and review found no blocking issue.
The goal remains valid, but evidence exposes a bounded correction.
A different CLI or fresh session has a clear advantage and receives an inspected handoff.
Authority, context, evidence, or user intent is insufficient.