coding-orchestration
Coordinate bounded repository work with Astra decisions, OpenCode Go execution, risk-proportionate review and explicit provider fallback.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- coding-orchestration
- description
- Coordinate bounded repository work with Astra decisions, OpenCode Go execution, risk-proportionate review and explicit provider fallback.
02 资源文件 1
- 参考文档worker-reference.md2.0 KB
03 SKILL.md 正文
For visual work, finish Impeccable, obtain independent Astra visual critique,
resolve its findings, then record final delivery evidence from that candidate.
Working screenshots may support critique. Astra retains live Computer Use;
Luna may prepare bounded scripts or media files, never inherit browser control
merely to reduce model cost. See design-quality and evidence-capture.
The parent owns the full requested result, architecture, integration, conflicts
and verification. Read $HOME/.codex/development-system/agent-roster.json before
selecting a model. Keep the task contract concise. Ordinary bounded work uses
one execution and parent review; use orchestration-plan when ownership,
observed risks or parallel dependencies need an explicit plan. The current user's
authorization governs dispatch; a plan is not an authorization receipt.
Execution
Astra orchestrates, designs and judges acceptance. Use evidence-capture for
recordings and walkthroughs; deterministic host tools run stable batches.
The evidence-preparation route selects Luna for bounded capture scripts and
media preparation. Astra drives novel or ambiguous UI states when needed.
Use local tools directly for deterministic search, commands and collection.
Batch independent calls and overlap independent CI with useful work. Serialize
mutating commands on the same writer/build state. Delegation must shorten the
critical path or add needed independent judgment; do not create handoffs merely
because tools support them.
Delegate bounded implementation to the ordered OpenCode Go-first fast route
when a worker reduces delivery time. Factory/Devin provide declared fallbacks
and Fable help with complex review. Luna is the final worker fallback.
Each worker receives the exact root/revision, owned files, behavior, constraints, focused checks, expected artifact and stop condition. Verify path confinement before writable dispatch. Keep one writer per surface; independent writers may run concurrently only with explicit disjoint ownership and integration owned by Astra. Preserve concurrent work. Reuse the worker when its context is useful.
Use the provider's real CLI argument array from model-route. OpenCode Go is
opencode run --pure --model opencode-go/<model> --variant <effort> --format json.
Never add permission or publication authority inside the pure resolver. Record
the provider's observed model before claiming resolution. Cache typed quota or
availability failures with record-provider-failure --input <observation.json>
and bounded expiry (at most seven days). model-route reads that private host
cache unless an explicit observation packet overrides it. Do not retry an
unexpired quota failure on each task; carry useful work into the next route.
On T3, launch CLI workers through development-system run-worker --input packet.json --json; read worker-reference.md for the packet. Its deterministic
owner watch stops the process group when the turn ends or becomes unreadable.
Other hosts must keep workers attached to their native cancellation lifecycle.
Check startup, then completion or an observed stall; avoid repeated model-driven
polling. A productive worker
does not fail merely because a fixed number of minutes passed.
Review and evidence
Treat simplification, test-value review, correction and objective verification
as responsibilities, not mandatory new conversations. Astra reviews a normal
worker's diff and the objective. Request Fable for observed complex risk or an
explicit independent-review request. Review corrections and remaining risks;
do not restart the whole repository analysis. Structured review is opt-in
(signals.structuredReview: true) or justified by observed risk. Preserve
host-bound correction validation and never close an
unresolved blocker/high finding because a reviewer timed out.
Run focused checks after edits and applicable integration checks once when the candidate stabilizes. Do not create tests that copy implementation details or repeat broad suites without a concrete requirement. File/test counts and styling scores are not quality gates. Verify the public behavior being claimed. After affected checks and required gates pass, continue toward the authorized delivery. Repeat only for relevant changes, failures or unresolved concerns; reuse evidence only while its tested candidate, inputs and environment still apply. Never bypass required hooks/CI. Preserve the check exit code: run the check into a log, then read relevant output separately. A successful trailing output filter can hide a failed test.
Use design-quality with Impeccable when visual quality is acceptance. An independent Astra
finish reviewer satisfies the critique responsibility; the designer reviewing
its own work does not. Reuse that review instead of duplicating it. Use one focused Jakub skill
for the detail being improved. better-interface is for a broad interface
review; do not force it onto every UI change. Prefer existing product tokens
and conventions over generic polish defaults. Show-me or PR Lens can explain
a complex change; ordinary diffs do not require visual artifacts.
Computer Use is opt-in to acceptance and led by Astra. A delegated neutral executor gets only a SHA-256-bound execution plan, authorized origins/paths, actions and opaque inputs; keep the private rubric with the parent. The host validates write authority separately. Capture relevant evidence early and keep runtime/tool failures distinct from product failures. Recording itself does not require another model. Avoid one inference per stable click or frame. One driver owns each session; exchange completed evidence instead of progress chatter. Recover readiness before retrying a failed capture. Respect the repository's allowed browser mechanism.
Report the delivered outcome, checks, remaining limitations and exact release state. Retain requested/resolved models, fallback causes and lane terminal states in the evidence. File installation alone does not prove live influence.
Choose the smallest useful change for user experience, developer workflow and agent comprehension (UX, DX, AX). These are decision criteria, not three new audit stages. Request Astra Low for clear orchestration, Medium for ambiguity and High for difficult judgment. Verify active host effort before claiming it changed; the roster alone cannot change an already-running turn.
04 同仓库更多 Skills
working-backwards
Define a software feature through PRFAQ and staged documents when the user requests working backwards before coding.
flow-implement
Implement a requested software change through verification, corrections, and its authorized delivery endpoint.
development-steward
Run the scheduled, read-only weekly maintenance review for the six explicitly opted-in repositories and prepare one concise private report for Check-in.
grill-with-docs
Run one recoverable interview for functional, visual, or mixed software grills; reuse equivalent answers and offer the shared HTML questionnaire.
global-agent-guardrails
Install, audit, test, or update the Development System's global destructive-command guard for Codex, Claude Code and T3 Code. Use when configuring agent safety hooks or investigating whether dangerous shell operations are blocked.
impeccable
Design or refine frontend UI using project context and a focused design playbook; also handles visual critique and polish.