coding-orchestration
Choose delegation, ownership, and verification for non-trivial repository execution with a pinned task contract.
- License 许可
- MIT
- 最近更新
- 2026-11-14
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- coding-orchestration
- description
- Choose delegation, ownership, and verification for non-trivial repository execution with a pinned task contract.
02 资源文件 7
- 参考文档references/execution-continuity.md3.0 KB
- 参考文档references/execution-contract.md3.4 KB
- 参考文档references/host-dispatch.md2.7 KB
- 参考文档references/jev-advisory.md2.8 KB
- 参考文档references/jev-governance.md428 B
- 参考文档references/spec-ticket-contract.md3.2 KB
- 参考文档worker-reference.md885 B
03 SKILL.md 正文
Coding orchestration
Optimize rápido → bien → barato: reach the complete usable result quickly, correct it with focused evidence, and keep measured cost and complexity low. Preserve behavior, data boundaries and authorization.
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.
Resolve the run
The model selected when the conversation starts remains the orchestrator. It chooses workers within the user's provider, quota and capability limits and integrates their results. A roster or native profile is a recommendation, not runtime identity or a provider chain. A restricted family stays restricted for every descendant; report a missing browser or vision capability instead of substituting a different family.
Before a worker starts, pin one execution contract. It names the objective or ticket, root and revision, owned paths, expected observable behavior, mode, authorization and endpoint, enumerated checks, evidence receipt, stop conditions, and the required completion report. Read the execution contract for the compact packet fields.
Use exact instructions by default: give ordered actions, expected observations, checks and stops using the execution contract. Outcome delegation is an explicit, reasoned exception for a bounded implementation decision; record why a recipe would be premature and keep the same acceptance requirements.
The method is model-agnostic. Preserve the acceptance standard when capability or availability changes: reduce packet size and simultaneous decisions, supply concrete examples and observable checkpoints, then correct from the returned evidence. A model label never proves capability or acceptance. If an essential capability is unavailable, retain the gap and continue independent work; do not silently substitute a provider or promise equivalent results from every model.
Execute with useful ownership
The parent owns decomposition, architecture, integration, conflicts, verification, findings and the terminal state. Jev advises this parent; native host tools perform the work. Execute the repository's local canonical recipe; a skill does not migrate a product's form or other domain architecture to match its own examples.
Use deterministic tools directly and batch independent reads. Keep one writer per surface. Parallel workers are allowed only for disjoint paths with no shared dependency sequence. Start them from the same pinned contract and receive completion events. Do not send repeated unchanged status requests or poll a worker when no new event or observation exists. Reuse a worker for a focused correction while it owns the same surface; verify termination before transferring ownership.
Every worker packet includes the exact root and branch or revision, owned surface, settled routing, relevant references, constraints, focused checks, expected receipt and known failures when resuming. Workers preserve unrelated edits and return changed paths, commands, results and remaining gaps. A clean diff, first implementation or passing lint does not close unverified behavior.
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.
UI acceptance and evidence
For visible work, resolve fixture identity, role, organization and useful entities once before the main pass. Give a neutral browser executor exact action inputs and the values to record; the parent retains the acceptance rubric and judges the resulting values. Use the authorized browser mechanism and one driver per session.
When visual quality matters, complete Impeccable and independent capable critique first, resolve material findings on this candidate, then call evidence-capture for final media. A screenshot or copied file proves neither live harness influence nor product acceptance. Backend-only work does not need a visual workflow.
Finish
Continue through implementation, focused checks, corrections and the authorized endpoint. Separate source, local runtime, PR, Preview, production and acceptance. Report the candidate, actual observed model/tool identity, changed paths, checks, evidence references and remaining gaps. If blocked, name the concrete dependency and finish independent work; a timeout or missing receipt cannot become a passing result.
Close every task
Every task that changed files ends with a report:
- Write the concise packet (
flow-implement/references/completion-report.md) with the sections Veredicto, Qué cambió, Verificación real (pasó / falló / no se alcanzó, con evidencia), Pendiente, Preguntas al margen and one Jardinero line: "un error visto dos veces se propone como regla dura al nivel más alto: código > lint/CI/guard > regla/skill". - 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.
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.
For host-specific CLI dispatch, read host-dispatch. For interruption or ownership recovery, read execution-continuity. T3 packet details are in worker-reference.
For nontrivial delivery and benchmark results, default to a readable HTML report with passed/failed/not-reached behavior, timing, evidence and limitations. Markdown is supplementary. Publish sanitized report assets through the user-authorized temporary tunnel and state its actual lifetime conditions; keep secrets and raw transcripts outside the served directory. A post-deadline report cannot convert a failed timed run into success.
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.