AGENT SKILL

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

03 SKILL.md 正文

For visual acceptance, use design-quality; it owns the critique sequence. Use evidence-capture for the final walkthrough.

Rápido → bien → barato

Optimize elapsed time to the complete usable functionality, including corrections and required delivery. Correctness comes next; cost is third. Choose the route expected to finish sooner, even when its model costs more. A quick first draft that creates more rework is not a faster delivery. Preserve the requested behavior, data boundaries and authorization while shortening the critical path.

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.

Bounded worker entry

A dispatched worker with an exact root, owned task and checks starts with that packet. Lifecycle and provider selection are completed parent responsibilities; load only task-specific references and report blockers to the parent. Resolve skill aliases to their declared roots rather than appending r0/r1 to a path.

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. The fast-implementer Codex alternative uses Luna Max with priority. Other Luna roles use their installed TOML effort with priority. Astra handles independent review when needed. OpenCode Go and Codex are the only active providers.

The parent resolves provider routing once per dispatch. A selected worker executes its assignment and returns a concrete blocker to the parent when unable to proceed; it does not restart provider selection. Prefer native Codex agent lifecycle for Codex workers and existing host tool composition; add infrastructure only for an observed missing capability.

Mark provider selection and lifecycle routing as completed parent responsibilities in the worker packet. The worker uses its supplied root and task-specific references; it does not rediscover the global workflow from the parent cwd.

Each worker receives the exact root/revision, owned files, behavior, constraints, focused checks, expected artifact and stop condition. Start a fresh worker with that bounded packet and source pointers; inherit full history only when a specific dependency requires it. Receive completion events and recompute ready work from dependencies, ownership and available capacity. 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 an independent Astra reviewer 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. A new test is optional: name the failure it catches and how failure leads to correction. Choose the quickest adequate existing check, runtime probe or focused test. Lint, React Doctor, Impeccable and reviewers answer different questions; select by the claimed behavior instead of stacking every tool. 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. Feature orchestration requests Astra xHigh at normal/default speed, a provisional choice from the full-flow pilot. Select lower effort for simple work. Read specialist effort and sandbox from the installed TOML; escalate observed difficulty, not every role. Astra requests default speed and Luna priority. Verify active host settings before claiming they changed; start a new session to load installed defaults. The roster cannot reconfigure a running turn.

04 同仓库更多 Skills