solution-optimality-evaluation

What problem does it solve?

This Skill prevents teams from committing to suboptimal algorithms or architecture decisions by forcing explicit justification, alternatives, and quantified evaluation across performance, code quality, and system properties.

Core Features & Use Cases

• Three-challenge design vetting: Requires specific answers to why this approach fits the context, whether it’s the simplest sufficient solution, and what the strongest alternative was and why it was rejected.
• Ten-dimension performance assessment: Evaluates (or explicitly marks N/A with rationale) CPU, memory, network, disk, locks/contension, throughput (TPS/QPS), parallelism, concurrency, response latency, and rendering speed constraints.
• Operational and maintainability guardrails: Applies benchmarks and engineering principles (e.g., back-pressure, tail latency, cache stampede, cognitive complexity, and reversibility) to reduce production risk.

Use case example: Before finalizing a new data-processing algorithm that touches a critical hot path, the builder uses this capability to validate worst-case behavior, tail-latency implications, concurrency safety, and long-term maintainability tradeoffs rather than relying on first-pass plausibility.

Quick Start

Use the solution-optimality-evaluation Skill to challenge a proposed implementation by demanding justification, alternative comparison, and evaluation against CPU, memory, network, and latency constraints before the approach is finalized.