orchestrate-work
Coordinate or resume repository delivery with a pinned task contract and supported governed 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 supported governed 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.
Govern the full feature
Read Jev governed execution once for non-trivial work. Keep the selected parent. Use fast research, Astra planning, a different fresh Astra plan review, bounded writers, independent deep review and actual behavior evidence. Jev supplies a required judgment at each lifecycle boundary; code enforces the applicable gate. Tiny unrelated deterministic work stays 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 the installed governance gates without inventing another coordinator.
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 the governed executor for the routes it supports; native descendants need their own observed binding. 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.
Test and review boundaries
The default test-change policy has allowedChanges = []. Do not add, modify or delete test files, or generate one test per form or feature, until the parent closes a reviewed exception. The shared runtime check is findTestPolicyViolations({root, baseRef, policyPath: "config/test-change-policy.json"}), which returns a violation array. An exception identifies path, SHA-256 or null for an authorized deletion, reason, issue and reviewed content. Report a real evidence gap to the parent instead of widening scope.
Use the smallest adequate checks and preserve their exit codes. Independent review derives its oracle from the accepted objective and public interface. Green tests, counts and coverage do not override weakened assertions or an unproven requirement.
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.
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.