ce-optimize

Orchestrate metric-driven iterative experiments with baselines, gates, and durable logs.

Updated Jan 10, 2026
One-click install
npx skills add https://github.com/KingInYellows/yellow-plugins --skill ce-optimize-kinginyellows
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-optimize
Source: https://github.com/KingInYellows/yellow-plugins/tree/main/RESEARCH/upstream-snapshots/e5b397c9d1883354f03e338dd00f98be3da39f9f/plugins/compound-engineering/skills/ce-optimize
Command: npx skills add https://github.com/KingInYellows/yellow-plugins --skill ce-optimize-kinginyellows

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Automate and orchestrate iterative experiments to optimize measurable software outcomes by systematically generating variants, executing them against a consistent harness, and recording results for durable, resumable improvement.

Core Features & Use Cases

  • Orchestrates end-to-end optimization cycles: baseline setup, hypothesis backlog, batch execution, judge-based scoring, and best-in-batch merging.
  • Enforces rigorous data integrity and durability with on-disk experiment logs, crash-recovery markers, and explicit checkpoints.
  • Use Case: You want to minimize a scalar metric (e.g., build time) while ensuring tests stay green, or optimize semantic quality using LLM-based judging with strict spend controls.

Quick Start

Describe an optimization goal and run an initial baseline measurement to begin the iterative loop.

Frequently Asked Questions about ce-optimize

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

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

Automate metric-driven code optimization by orchestrating repeated experiments against a measurable goal, using baselines, gates, and judge scoring to converge on the best solution. The system runs batches and records results for audit and rollback.

What is the best way to run iterative build time optimization with safety gates?

Iterative build time optimization is managed by defining a repeatable harness, seeding a backlog of hypotheses, and running batch experiments serially or in parallel. Strict checkpoints and safety gates ensure tests stay green and enforce reproducibility.

Can I use LLM-based judging for semantic quality optimization with spend controls?

LLM-based judging for semantic quality optimization is supported with strict spend controls. The system orchestrates experiments, applies judge-based scoring to variants, and merges the best-in-batch results while maintaining cost control.

How does crash recovery work for iterative experiment harnesses?

Crash recovery for iterative experiment harnesses relies on durable on-disk logs and explicit checkpoints. These mechanisms enforce data integrity, allowing the optimization loop to resume from the last safe state without losing previous measurement results.

Do I need Python3 to run metric-driven optimization batches?

Python3 is required to run metric-driven optimization batches. The environment uses Python3 scripts to orchestrate the measurement harness, execute variant tests, and record results for durable, resumable improvement cycles.

How do I rollback code variants after a failed optimization experiment?

Rollback after a failed optimization experiment is enabled by durable on-disk logs and explicit checkpoints. The system records all results for audit, allowing you to safely revert variants that fail safety gates or regress metrics.