systematic-optimization

Guides systematic problem-solving from quantified baselines through root-cause analysis to verified structural fixes.

3|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/ooooooooooooooooooop/personal-ai --skill systematic-optimization-ooooooooooooooooooop
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: systematic-optimization
Source: https://github.com/ooooooooooooooooooop/personal-ai/tree/main/skills/systematic-optimization
Command: npx skills add https://github.com/ooooooooooooooooooop/personal-ai --skill systematic-optimization-ooooooooooooooooooop

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Recurring failures, inefficiency, and quality issues often get patched with temporary fixes that inevitably resurface. This Skill enforces a complete, domain-agnostic optimization methodology that quantifies baselines, finds true root causes, and implements structural mechanisms that cannot be bypassed instead of relying on conventions people forget to follow. ## Core Features & Use Cases - Nine-step methodology: quantified baseline, full problem enumeration, root-cause classification (missing constraint / unenforced constraint / unenforceable constraint), structural solution design, industry solution research, trade-off synthesis, decision-gate plan confirmation, implementation, and measured verification. - Constraint layering: every solution is labeled as system-level (enforceable), process-level (checklist gates), or convention-level (documentation only), with explicit upgrade triggers when convention-level fixes recur. - Verification triad: confirms changes actually took effect via artifact evidence, runtime loading, and observed behavior, then closes the loop by comparing metrics against the original baseline. - Use Case: When a long-running agent workflow keeps stalling despite documented rules, use this Skill to quantify token waste and hang frequency, trace the root cause to unenforceable conventions, and implement broker-level automatic reclamation with budget enforcement. ## Quick Start Use the systematic-optimization skill to analyze why this process keeps failing, quantify the baseline, find the root cause, and propose structural fixes with measurable verification.

Frequently Asked Questions about systematic-optimization

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

FAQPage Schema
How do I fix a problem that keeps recurring despite existing rules?

Recurring problems usually mean the constraint lives at the convention layer, where rules exist in documentation but nothing enforces them. Classify the root cause, then upgrade the fix to the system layer with hard validation, automatic reclamation, or budget limits that cannot be bypassed.

What is the difference between a temporary fix and a structural solution?

A temporary fix relies on human memory, such as manual cleanup or remembering to check something, and will recur. A structural solution embeds the constraint into the system itself, like required parameters, automated gates, or enforced budgets, making the failure impossible to repeat.

How do I verify that an optimization actually took effect?

Use the three-part verification: confirm the artifact changed via file hash or version, confirm the running system loaded the new code or config, and trigger the behavior once to observe the new outcome. Then compare metrics against the original baseline.

When should I not use a systematic optimization process?

Skip it for single-point small fixes, which belong to minimal-implementation workflows, and for read-only reviews that produce no solution. The full methodology is designed for systemic, recurring, or cross-cutting problems that justify root-cause analysis.

How does this methodology relate to DMAIC or PDCA?

The nine steps map directly onto DMAIC, the Toyota eight-step method, and PDCA. Its additions are quantification-first baselining before any conclusion, and constraint layering that explains why fixes recur when they depend on people remembering rules.