btseytlin/ultrapack

btseytlin/ultrapack

Skill Claude CodeCodex

Part of up

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.

btseytlin/ultrapack

Skill Claude CodeCodex

Part of up

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.

btseytlin/ultrapack

Skill Claude CodeCodex

Part of up

Use when a task needs isolation from the current workspace. Picks a worktree directory via a fixed priority order, verifies it's gitignored, creates the worktree, auto-detects project setup, runs baseline tests.

btseytlin/ultrapack

Skill Claude CodeCodex

Part of up

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…

btseytlin/ultrapack

Skill Claude CodeCodex

Part of up

Use to babysit a long-running process (training run, batch job, migration, deploy) on a remote pod or locally while the user is away. Defines a launch contract, gates on immediate crash, polls for stability, triages anomalies as recoverable (fix + resume) or not (tear down + notify). Auto-triggers when the user asks…

btseytlin/ultrapack

Skill Claude CodeCodex

Part of up

Orchestrate the full Ultrapack workflow in Codex: 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.

btseytlin/ultrapack

Skill Claude CodeCodex

Part of up

Extract durable, non-obvious lessons from the current dialogue and route them to project guidance, memory, documentation, or the active task conclusion. Use when the user asks to reflect on a session or preserve learnings.

btseytlin/ultrapack

Skill Claude CodeCodex

Part of up

Break a failed implementation loop by tracing attempts, identifying the real blocker, and proposing a materially different direction before further changes. Use when repeated fixes or investigations are not converging.

btseytlin/ultrapack

Skill Claude CodeCodex

Part of up

Produce a compact, zero-context handoff for the current Codex work and, after user confirmation, save it to the active task conclusion or a new task summary file. Use when the user asks to preserve progress for a later session.

btseytlin/ultrapack

Skill Claude CodeCodex

Part of up

Use when implementing deterministic, reusable code where regressions would warrant a CI red light. Enforces RED-GREEN-REFACTOR. Applicability rule and skip conditions inside.

btseytlin/ultrapack

Skill Claude CodeCodex

Part of up

Manually test the latest change with one realistic positive case and one adversarial negative case, capturing evidence before any further fix. Use when the user asks for a quick confidence check or wants to test a recent implementation.

btseytlin/ultrapack

Skill Claude CodeCodex

Part of up

Use on any bug, test failure, or unexpected behavior before proposing a fix. Enforces four-phase root-cause investigation — reproduce, pattern-match, hypothesize, fix — with a hard rule against symptom patches.

btseytlin/ultrapack

Skill Claude CodeCodex

Part of up

Use before any creative work — features, components, behavior changes. Turns an idea into a validated spec with explicit tradeoffs and unknowns, and splits scope into multiple tasks if it's too large. Output is the ## Context and ## Design sections of the task file.

btseytlin/ultrapack

Skill Claude CodeCodex

Part of up

Use when writing or editing documentation — project docs, CLAUDE.md, READMEs, SKILL.md, docstrings, inline comments. Auto-triggers on .md files and docstring edits. Enforces lead-with-why, kill stale content, lists over tables, no aspirational sentences.

btseytlin/ultrapack

Skill Claude CodeCodex

Part of up

Use to implement an approved plan. When the plan declares ### Interface graph, derives waves by topo-sort over [blocks] IF edges only — non-blocking IF edges (the default) put producer and consumer in the same wave, since the IF declaration is sufficient context. Edits inline when only one implementer would fire…

btseytlin/ultrapack

Skill Claude CodeCodex

Part of up

Use after design to turn a validated spec into a lean implementation plan. Outputs the ## Plan section of the task file — files, line numbers, class/method names, invariants, test strategy, order. Ends with a scope-creep / simpler-way check.

btseytlin/ultrapack

Skill Claude CodeCodex

Part of up

Use after verify passes for the future maintainer's audit — sit in the chair of the person who'll touch this code in 3-6 months and ask "what will bite us later?" at the decision level. Surfaces wrong abstractions, load-bearing-but-unobvious shapes, next-change traps, drift from surrounding code; raises a Scope flag…

btseytlin/ultrapack

Skill Claude CodeCodex

Part of up

Use after execute to attack the change and demonstrate how it's broken. Default stance — the change is broken; prove and demonstrate it. Builds an attack checklist (happy-path / negative / invariant / interface hypotheses), runs each freshly, smokes the end-to-end, writes a short summary to the task file's Verify…