orchestrate-work
Coordinate or resume repository delivery with a pinned task contract and bounded native workers.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- orchestrate-work
- description
- Coordinate or resume repository delivery with a pinned task contract and bounded native workers.
03 SKILL.md 正文
Orchestrate work
Optimize rápido → bien → barato: deliver the complete usable result, correct it with focused evidence, then reduce measured waste. The model selected when the conversation starts owns orchestration and the parent integrates the run.
Coordinate the full feature
Read Jev advisory execution once for nontrivial work. Keep the selected parent. Use fast research, Astra XHigh planning, a different fresh Astra XHigh plan review, bounded writers, independent final review and actual behavior evidence. Jev advises at useful routing and correction decisions; the parent records the decision and executes through native tools. Classification failure does not globally block work. Tiny deterministic edits stay direct.
Pin the target
Recover the objective or ticket, latest correction, exact root, branch or revision, current changes, authorized endpoint and final review surface. Make done observable through required behavior, enumerated checks, resolved findings, evidence and the endpoint. Do not restart settled planning or stop at a first draft.
Before any delegation, pin the execution contract:
- owned files or module surface and one writer;
- exact instructions by default, or a recorded reason for a bounded outcome exception;
- expected public behavior and observable values;
- authorization, stop conditions and terminal state;
- focused checks, required gates and completion receipt.
Read the packet fields when composing a worker handoff; this reference owns the execution protocol. Use its ordered actions, expected observations and receipt. Adapt packet size and checkpoints to actual capability while preserving the acceptance standard. On model, quota or session change, use execution continuity to preserve work, authorization and evidence and transfer ownership safely.
Use the repository's local canonical recipes and domain architecture. A workflow skill does not migrate forms or other product structures. Use Jev advice without adding global execution gates.
Dispatch supported workers
Choose currently available workers within the user's provider, capability and quota constraints. A roster or profile does not establish runtime identity. Use native host tools and completion events; record actual observed identity. An unsupported route remains a capability gap. Design, visual judgment and Computer Use require their actual capabilities; report a gap instead of silently substituting a family.
Delegate only when it shortens the critical path or supplies independent judgment. Start parallel packets only for disjoint ownership and explicit dependency order. Receive completion events, reuse the same worker for a focused correction, and avoid repeated unchanged status calls or polling without a new event or observation.
The parent retains decomposition, integration, conflicts, acceptance and the terminal state. A worker packet states the root, revision, owned surface, settled routing, behavior, checks, evidence shape, stop conditions and expected receipt. Preserve unrelated edits.
Writer packets: Done when: is executable (command plus expected
observation); the writer retries up to 3 times and the coordinator reruns it.
Outcome: is optional.
Automated tests and evidence
No automated tests anywhere: do not create, run or restore them; delete them
when found (check-no-tests and the guard enforce this). Every task includes
real verification without being asked: computer use, browser, and the
repository's verification CLI and feature map. Report passed / failed / not
reached with evidence.
Headroom transport evidence
Headroom is an explicit same-account per-invocation option. Keep the existing Codex binary and CODEX_HOME, preserve caller arguments, and request lossless, cache-conservative operation. Provider cache reuse can still change request bytes; do not promise byte identity. Keep native usage from the parent and every actual descendant separate from proxy counters, and separate requested model or tier from observed identity. Use launch/completion events instead of polling. Proxy counters and token deltas are descriptive; without complete controlled evidence, do not claim Headroom caused savings.
UI and benchmark evidence
Resolve fixture identity, role, organization and useful entities once. A neutral browser executor receives exact action inputs and values to record; the parent keeps the acceptance rubric and judges the resulting values. Complete Impeccable and independent capable critique, resolve material findings, and then capture final media.
Finish
Inspect the integrated diff against the full objective, correct material findings and run the named final checks after changes settle. Report candidate, actual model/tool identity, receipt, checks, links and remaining gaps. Keep source, local runtime, PR, Preview, production and acceptance claims separate.
Close every task
Every task that changed files ends with a report:
- Write the concise packet (
flow-implement/references/completion-report.md): at most 600 characters with the result, then the sections## Qué se hizo(real verification marked pasó / falló / no se alcanzó, with evidence),## Hallazgos(a mistake seen twice proposed as a hard rule at the highest level: código > lint/CI/guard > regla/skill),## Qué sigueand## Detalle, in that order. No tables unless"allowTables": true. - Render it with
development-system document --input <packet> --json. - Serve it with working-backwards
reader-live.mjs --tunnelfrom a per-report copy directory. - Put the URL in the final answer.
When the user asks for the answer in the chat only, write no document and open no tunnel. A Stop hook asks once when files changed and no report was produced. If a report is truly not useful, say why in one line.
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.