se-optimize

Automates multi-round ML model optimization with a fixed baseline and a reward model.

Updated May 7, 2026
One-click install
npx skills add https://github.com/simonwjackson/pi-software-engineering --skill se-optimize
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: se-optimize
Source: https://github.com/simonwjackson/pi-software-engineering/tree/main/skills/se-optimize
Command: npx skills add https://github.com/simonwjackson/pi-software-engineering --skill se-optimize

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

The se-optimize skill automates metric-driven iterative optimization loops, enabling teams to efficiently compare multiple code/config variants against a reproducible measurement harness and converge on the best performing solution.

Core Features & Use Cases

  • Supports both hard objective metrics and LLM-based judge scores, with baseline/config setup, gated progress, and crash-safe logging.
  • Uses isolated worktrees and persistent experiment logs to enable long-running optimization runs with robust resume and recovery.
  • Facilitates phase-driven workflows (setup, measurement scaffolding, hypothesis backlog, batch optimization, evaluation, and wrap-up) and dependency approvals.

Quick Start

Define an optimization spec and run the optimize loop to compare variants against a fixed measurement harness.

Frequently Asked Questions about se-optimize

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate metric-driven optimization experiments for code variants?

Automate metric-driven optimization experiments by defining an optimization spec and running a measurement loop. The harness compares code and config variants against a fixed baseline using hard metrics or LLM-based judge scores to converge on the best solution.

What is the best way to run batch optimization experiments safely?

Run batch optimization experiments safely using isolated worktrees and a persistent experiment log. This crash-safe setup manages phases from initial scaffolding through evaluation, enabling robust resume and recovery for long-running optimization workflows.

Can I use LLM-based judge scores instead of hard objective metrics for measurement?

LLM-based judge scores are fully supported alongside hard objective metrics for measurement. You can configure the optimization harness to evaluate code variants using either quantitative data or LLM assessments based on your specific evaluation criteria.

How do approval gates work in automated code optimization workflows?

Approval gates in automated code optimization workflows control phase transitions from setup through wrap-up by enforcing dependency approvals and stopping criteria. The orchestrator manages these gates to ensure experiments meet defined scope rules before proceeding.

Why do I need isolated worktrees for running optimization experiments?

Isolated worktrees are needed for optimization experiments to provide crash-safe logging and reproducible measurement environments. They prevent variant conflicts during batch execution and maintain persistent experiment logs for robust recovery of long-running optimization runs.

What are the limitations of using automated experimentation loops for performance tuning?

Limitations of automated experimentation loops include the requirement for a reproducible measurement harness and defined optimization spec. Without clear scope rules, stopping criteria, and dependency approvals, the orchestrator cannot effectively manage the iterative optimization phases.