optflowlisted

# Optflow ## Overview Use this skill to discover repository optimization opportunities and execute selected optimizations end to end: - Discover optimization points first (performance, reliability, maintainability, security, cost, DX). - Prioritize by impact/effort/risk. - Execute in strict sequence with validation and explicit commit policy. - Add BDD behavior specs when requested or when requirements are ambiguous. ## Trigger Cues Trigger this skill when the user asks for one or more of: - Ask to find optimization opportunities in a repository/library. - Ask for optimization roadmap + implementation. - Require test-first optimization delivery and commit (final or per step). - Require behavior-driven delivery (BDD) or acceptance scenarios. ## Workflow ### 0. Discover Optimization Backlog - Scan the repository before planning changes. - Classify findings into: performance, reliability, maintainability, security, developer experience, and cost. - For each finding, record: - symptom and evidence (file/path/metric) - expected impact - effort estimate - risk level - Build a prioritized backlog using impact/effort/risk. - Explicitly mark low-confidence findings as hypotheses. ### 1. Define Ready Criteria (DoR) > See shared delivery base: [`references/delivery-base.md`](./references/delivery-base.md) Additional for optflow: - If implementation is requested and commit style is not explicitly specified, use `per_step` (default). - If user says "per step optimize and