ultrawork

Ultrawork for Claude Code

This generated file is the Claude Code-facing runtime skill document. Claude Code slash commands should read this file directly; maintainers edit the source documents listed below instead.

Generated Runtime Composition

Source order:

• ../../docs/skill-core/ultrawork.md
• ../../docs/platforms/claude-code-ultrawork.md

The sections below are already composed for this platform. Do not ask the runtime model to load another platform's runtime document or invocation syntax.

Source: docs/skill-core/ultrawork.md

Ultrawork

Ultrawork is a Markdown-first orchestration loop for moving from idea to verified result with the retained skill chain. Each phase is chosen explicitly from this Markdown workflow — there is no hidden next-step selector. Do not use it for a small concrete fix whose contract surface, baseline evidence, and verification command are already clear; use direct implementation or ralph.

Invariants

U1. Ultrawork orchestrates the retained chain and never replaces it: the
    planning gate uses `ralplan`, the execution handoff uses `ralph`.
    When Ralph is unavailable, Ultrawork may inline the phase procedure but
    remains an orchestrator: repository mutation still dispatches `executor` by
    default under Ralph's need test; inline writes require a recorded LIGHT-tiny
    or dispatch-unavailable fallback and carry the unchanged executor contract
    per Ralph's `## Mode-Gated Agent Dispatch`, and a fired review or audit
    trigger is exempt from the need test and never runs inline.
U2. Approved existing specs or plans may skip earlier phases only when the
    skip reason and source artifact are recorded; a merely relevant plan
    without approval evidence or with mismatched scope goes through the
    planning gate.
U3. requirements_gate: planning must not start until the requirements
    source is recorded. Interview is the only user-facing content approval
    gate for new work; ultrawork never auto-approves the interview spec.
U4. Once ralplan's gates pass, record the plan approval source and
    continue into ralph without a separate Plan Approval Brief prompt;
    pause only on ralplan's named pause conditions (canonical list:
    ralplan `### Ultrawork exception`).
U5. worktree_gate: no source file edit until a `Worktree decision` is
    recorded. Ultrawork's worktree duties are the numbered list in
    `### WORKTREE` below.
U6. The Direction Contract and AC IDs carry unchanged through plan,
    session, packets, and report; each phase records only its delta; a
    phase needing a direction change pauses for explicit user approval.
U7. Markdown at .oh-no/sessions/{sessionId}/ultrawork.md is authoritative.
    No JSON state artifact in v1; any future JSON must be derived and
    non-authoritative. No timer, daemon, or background heartbeat.
U8. Doctor/status runs at entry, resume, pre-execution, pre-merge, and
    pre-final; BLOCKED stops before edits, merge, or final claim.
U9. Escalation routes are fixed: ambiguous requirements -> user or
    `interview`; direction/scope conflict -> user or `ralplan`; failing
    checks or unknown root cause -> `systematic-debugging` (which owns
    `debugger` dispatch); public-contract/security/packaging risk ->
    `code-reviewer` or `verifier`; missing worktree or verification
    evidence -> blocked.
U10. Any scope change, missing authority artifact, failed worktree gate,
     or failed verification transitions to a named non-success outcome,
     never silent continuation.
U11. Final Validation does not repeat Ralph's completed internal gates;
     review-then-verify order holds and an early verifier is stale,
     discarded, and rerun.
U12. The run is invalid unless the ledger shows each named phase gate
     satisfied or a recorded not-required reason; a silently omitted step
     is a named ledger gap, not a pass.
U13. Ultrawork is the only context that may invoke interview/ralplan/ralph
     without their per-step transition question. It skips the between-phase
     "which next skill?" question and the separate plan-approval prompt —
     and skips nothing else: spec approval when requirements are unclear,
     planning gates, scope-change pauses, verification, and final evidence
     all still run.
U14. Maker roles do not self-approve; inline checker fallback is still
     checker output. When a named verifier trigger fires on a
     subagent-capable host, an
     inline check by the maker or accepting agent never satisfies the
     independent verifier audit. Same authorship alone is not that trigger.
U16. Phase-agent authorization, eligibility, and fallback follow
     `## Agent Roles`.
U17. A discovered plan admitted through U2 but lacking an execution
     profile gets the profile set before execution (schema is
     ralplan-owned); execution never starts profile-less.