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.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
The user pointed at one instance of a problem. Treat it as a sample, not the whole problem. Find the principle behind it, find every place that breaks that principle, and fix them all.
file:line.After step 5, ask the user to approve the plan if the change is major. Do not ask in hands-off mode or when the user already told you to proceed without asking.
Hands-off mode is on when the first argument token is the literal handsoff, or when the active task file has **Mode:** hands-off. Strip the handsoff token before reading the criticism. In hands-off mode, follow the handsoff contract and log the decision.
A change is major when it does any of these:
Problem: <general description from step 1>
Principle: <violated principle>
Found: <count> violations
- <file:line> — <what was wrong>
Fixed: <what changed, shared cause first>
Open: <violations left and why, or none>
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.
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.
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.