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.
03 SKILL.md 正文
The parent owns the full requested result, architecture, integration, conflicts
and verification. Read $HOME/.codex/development-system/agent-roster.json before
selecting a model. Use the pure orchestration-plan operation for non-trivial
work with an explicit task contract and observed signals. The current user's
authorization governs dispatch; a plan is not an authorization receipt.
Execution
Astra orchestrates, designs, performs ordinary review and operates Computer Use. Use local tools directly for deterministic search, commands and collection. 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.
Check startup and progress proportionally to the task. 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. A no-change correction is a recorded no-op. 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.
Use Impeccable for design direction when relevant and 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. 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.
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.