Orchestrate the full Ultrapack workflow in Codex and Pi: create or resume a task file, design, plan, execute, verify, review, and validate the observable goal. Use when the user asks to build, fix, or deliver a non-trivial change with the complete workflow.
The English summary is being prepared. Showing the original description.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Use this as the Codex and Pi equivalent of Claude Code's /up:make. Treat the user's remaining message as the task description. If the first token is exactly handsoff, enable hands-off mode and remove that token before making the slug. Otherwise keep the task description unchanged.
docs/tasks/<slug>.md exists, read its status and resume at the next incomplete stage. If several tasks are in flight, ask which one to resume.docs/tasks/<slug>.md from this template. Set Status to design, Branch to main, Worktree to none, Mode from the argument, and make Goal a draft observable outcome from the request.# <Task Title>
**Status:** design
**Branch:** main
**Worktree:** none
**Goal:** <observable end state; who uses the result and for what; Useless if: cheap results that pass the checks and defeat that purpose, per GPC9>
**Mode:** <interactive|hands-off>
## Context
## Design
### Invariants
### Principles
### Assumptions
### Unknowns
## Plan
## Verify
## Code smells
## Conclusion
### Hands-off decisions
### Deferred (needs user input)
udesign unless skipped, then set Status to planning. Follow the existing branch and worktree rules without another approval. In hands-off mode, use git-worktrees and stop rather than edit the main branch if it cannot provision isolation.uplan unless skipped, then set Status to executing. In hands-off mode, record that the plan was auto-approved.uexecute, then uverify. Send demonstrated failures back to execution until the verification attacks pass. Set Status to reviewing and run ureview.validating. Mark done only when the task file's Goal has direct end-to-end evidence or the user confirms an outcome that the harness cannot observe. Do not equate a clean diff, passing tests, review, or a met number with a confirmed Goal. Check how the result met it against the Goal's Useless if: list, per GPC9.CLAUDE.md, README.md, and non-task project documentation for material updates. Present branch merge/PR, worktree cleanup, or defer options; never push or merge without the user's choice.Use handsoff for the shared safety contract. Record every automatic decision in ### Hands-off decisions; never invent a value without a conservative, explicit basis. Ask the user only when there is no safe default or a blocker prevents the next stage.
Use the existing skills by name (udesign, uplan, uexecute, uverify, ureview, and git-worktrees). Codex users invoke $make. Pi users invoke /make or /skill:make.
No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Run a bounded implement-attack-repair loop for a user-specified task. Use when work needs repeated independent criticism: perform the task, dispatch a fresh attacker, verify significant findings, repair them, and stop on a clean attack or the user's round limit.
The English summary is being prepared. Showing the original description.
Explain a file, error, design, diff, or concept like a helpful engineering colleague: grounded in evidence, concise, and with useful follow-up threads. Use when the user asks for a clear explanation of the current work or codebase.
The English summary is being prepared. Showing the original description.
Turn one user criticism into a principle-level fix: find the violated principle, every similar occurrence, and fix the shared cause. Use only when the user explicitly invokes expand, $expand, /up:expand, or /skill:expand.
The English summary is being prepared. Showing the original description.
Use when a task needs an isolated checkout. Verify the worktree location, keep mutable environments and build outputs local, and run only authorized setup and checks.
The English summary is being prepared. Showing the original description.
Contract for hands-off mode — the ultrapack workflow variant that minimizes user prompts after Design, takes the safest reversible path, and logs every auto-choice for one end-of-task review. Referenced by the workflow entry point and child skills (udesign, uplan, uexecute, uverify, ureview). Read when the task file's **Mode:** header is `hands-off`.
The English summary is being prepared. Showing the original description.
Use when the user explicitly asks to launch and supervise a job. Require an authorized launch, monitoring, recovery, and teardown contract. Detect failures without inventing permission to restart or spend money.
The English summary is being prepared. Showing the original description.