Turn a request into a SCHEDULABLE task DAG — atomic tasks with real dependencies, not planning prose: challenge scope and pick a planning mode with the user first, explore the real repo so no path is invented, then decompose into atomic TASK-NNN entries — each with a ≤3-file write scope, 2-3 testable acceptance…
Read a feature branch's merge-readiness from its actual git data — measured metrics, not vibes: collect raw git output for the branch vs base, compute branch-health metrics (size class, test ratio, focus, drift, sessions, hotspots), scan the diff for pre-PR artifacts (secrets, .only, conflict markers, debug lines…
Deep-audit ONE Rust crate end to end — read every file, don't sample: enumerate and read the whole crate, run its cargo test, check the existing .ulpi/issues/ .md to avoid duplicates, then write or append evidence-backed findings (correctness, panic, validation, race, data-corruption, coverage gaps) each with severity…
Run 3+ genuinely INDEPENDENT build tasks concurrently on Claude Code's real parallel agent runtime — throughput without file conflicts or fake orchestration. Proves independence (disjoint write scope, no dependency edges) before launching, matches each lane to the best specialized agent, writes a complete…
Diagnose and fix 3+ genuinely INDEPENDENT failures concurrently on Claude Code's real parallel agent runtime — without splitting one root cause into conflicting investigations. Proves the failures don't share a root cause (same dependency/config/migration/deploy across traces) before launching, matches each lane to…
Write and change Rust the way THIS workspace already does it, NOT by generic defaults — a systems-programming reference carrying the real crate boundaries, error model, and conventions for storage engines, binary formats, Arrow/DataFusion, search and vector indexing, async concurrency, testing, and unsafe discipline…
Manage local service credentials WITHOUT ever exposing their values — the secrets CLI adds, rotates, lists, enables, disables, and inspects encrypted integrations (including MCP/agent tooling) through interactive entry, reporting only service names and enablement status. Hard invariant: secret material never enters…
Take one feature request from prompt to reviewed, audited delivery in a SINGLE autonomous pass — one runnable Workflow that plans, reviews the plan, builds task by task, cross-reviews the build, and optionally runs a launch audit, then RETURNS the verified findings rather than looping (the user decides any fix round…
Route the start of substantive work to the right execution path — a lightweight INTERNAL intake pass, not a user-facing command and not a universal constitution. Answers four questions fast: does a more specific skill own this, is specialized agent delegation warranted, what is the minimum context needed to avoid a…
Propagate ONE validated learning from this session into durable AGENT guidance — extract the smallest useful rule, classify its scope (Global / Claude Code Only / Agent-Specific), store it once in the central agent-learnings file, and sync the regenerated ## Learnings section into every live agent definition across…
Propagate ONE validated learning about Claude Code behavior from this session into the project's CLAUDE.md — the MAIN-AGENT memory Claude loads every session, not agent or skill files. Extract the smallest useful workflow/scope/session rule, place it in the correct section (Workflow Rules / Session Management / Scope…
Propagate ONE validated learning about SKILL design or quality from this session into the central skill-learnings file — extract the smallest useful pattern or anti-pattern, categorize it (Structural Patterns / Content Patterns / Anti-Patterns / Skill-Specific), and add it once without touching any actual skill file.…
Autonomous software delivery for Claude Code — 8 lifecycle phase skills (auto-spec → auto-ship) plus the loop/verify/checkpoint/budget primitives, with deterministic enforcement hooks and runnable Workflow templates.
AGENTS.md instructions for ulpi-io/autonomous-engineering, covering agents.md — autonomous engineering skills, what lives here, the deterministic coordinator, the skills (authoring source + discovery) and the contract every skill honors.
Claude Code instructions for ulpi-io/autonomous-engineering, covering claude.md, the collection in one line, core contracts (hold on every platform), workflow-tool backend compatibility (claude-specific) and claude plugin + hook wiring (claude-specific).
Prove a claim before acting on it: spawn N independent skeptics prompted to REFUTE it (optionally through distinct lenses — correctness, reproduction, security, regression, measurement) and keep it only if a majority fails. Fails closed on ties. Use to gate findings before fixing, fixes before committing, and any…
Implement a whole DAG plan autonomously — one approved pass, one clean rollback point per task, never building on a broken base. It requires an approved plan (specced upstream) and a clean git baseline, takes a SINGLE human approval of the plan, then walks the DAG layer by layer: for each task it implements on an…
Make code measurably faster without breaking it: metric + reproducible baseline FIRST, profile to the real hotspots, then per hotspot apply a change and re-benchmark — kept ONLY if the win is real beyond variance AND correctness holds; otherwise reverted. Stops at the target or diminishing returns. Never accepts an…
Turn a spec into a self-reviewed DAG of atomic build tasks: each task gets acceptance criteria, a disjoint write scope (≤3 files), and a slice-scoped validate; dependencies are wired and layered topologically so nothing builds on a missing base. Adversarial critics then attack the graph (cycles, phantom paths…
Review a change across every dimension at once, then keep only the findings that survive an adversarial check — autonomously. It fans out independent reviewers over the diff (correctness, security, performance, maintainability/readability, test adequacy, API/contract & compatibility), dedups their findings, and puts…
Take verified work to shippable — autonomously, with fail-closed gates and a human sign-off on anything irreversible. It runs the pre-launch gate (final validate green, review clean, security/observability/ rollback checks), and a gate that DIDN'T actually run is treated as a blocker, never as clean. Then it prepares…
Reduce a change's complexity WITHOUT changing behavior, provably: find duplication/dead code/over-abstraction in the diff, apply the smallest clarifying edit, then prove behavior preserved (tests green + adversarial semantic check) or REVERT — looping until dry. Respects Chesterton's Fence: never removes code whose…