keithhegit

Turn a structured intake artifact into a decision-complete plan, task graph, dependency map, owned paths, acceptance checks, expected outputs, and retry assumptions. Use when work spans multiple steps, files, or roles and needs explicit orchestration.

Assemble the final deliverable, orchestration log, vetter report, and concise retrospective for a completed orchestrated run. Use when implementation and review are complete and results need to be packaged clearly.

Assign work packages by role, enforce owned-path boundaries, manage execution state, track retries, blockers, review readiness, and host-driven ledger updates. Use when work is being handed off across phases or subagents.

Bridge OpenSpec change artifacts into Ultra-Orchestrator execution artifacts. Use when a repo follows OpenSpec for proposal, design, tasks, and archive, but execution should remain controlled by Ultra-Orchestrator through TaskManifest, WorkPackage, review, QA, risk gates, and ledger-based orchestration.

Legacy compatibility entry point for the original Ultra Orchestrator flow. Use only when you need the older lightweight stage-based orchestration behavior without the new strict OpenSpec-first control plane.

Primary Ultra Orchestration entry point for strict Codex-controlled engineering runs. Use this single skill for development, bug fixes, OpenSpec work, multi-file implementation, review/QA-heavy tasks, risk-gated work, or any run that needs automatic mode selection, OpenSpec bootstrap, machine-checkable TaskManifest and WorkPackage artifacts, ledger tracking, slice DAG execution, review, QA, delivery evidence, and retro.

Bridge OpenSpec change artifacts into Codex Ultra vNext execution contracts. Use when a repo stores long-lived specs in `openspec/changes` or `openspec/specs`, but execution should still flow through Ultra manifests, work packages, review, QA, ledger tracking, and final delivery rather than replacing Ultra with a separate control plane.

Compatibility and preview alias for the main Ultra Orchestrator strict protocol. Use this single skill to start vNext-style orchestrated runs when users still invoke ultra-vnext-core; it should follow the same run-mode decision, strict OpenSpec preference, ledger, JSON artifact, contract validation, slice DAG, review, QA, delivery, and retro behavior as ultra-orchestrator.

Use when creating, revising, validating, or packaging SCI/arXiv manuscript figures, graphical abstracts, system diagrams, mechanism diagrams, evidence snapshots, image-generation prompts, figure captions, or Overleaf figure assets under claim-evidence constraints.

Use when starting or resuming any SCI paper task in this workspace, including manuscript revision, citation repair, result writing, review preflight, LaTeX editing, arXiv packaging, or multi-agent handoff

Use when finding references, building literature review tables, identifying up-to-date or highly cited papers, comparing research methods, verifying citation quality, mapping references to claims, or converting AI literature notes into SCI-ready bibliography inputs

Use when a manuscript claims novelty, improvement, efficiency, speedup, superiority, reduced cost, better performance, or contribution relative to prior work, baselines, surveys, systems, or benchmarks

Use when converting experiment tables, logs, figures, measurements, HIL outputs, simulations, or appendix data into results, discussion, limitations, or contribution text

Use when a SCI paper task begins from a vague request, reviewer comment, advisor feedback, suspected flaw, manuscript confusion, or multi-step repair need

Use when editing live SCI LaTeX sources, Overleaf exports, arXiv source packages, figures, tables, citations, author blocks, labels, refs, packages, or appendix files

Use when adding, checking, repairing, or interpreting references, citations, related work, official documents, datasets, DOI links, or literature-supported claims in a SCI manuscript

Run Product Design and Frontend Design as one UI/UX collaboration workflow. Use when the user invokes Product Design + Frontend Design, asks for a UI/UX redesign, asks to make an interface more user friendly, designs a plugin panel, or wants a product flow turned into polished frontend UI.