algorithm-complexity-analysis
Algorithm Complexity Analysis
Overview
Use this skill to quantify whether candidate approaches can meet performance and resource constraints at expected scale.
Scope Boundaries
- Use this skill when the task matches the trigger condition described in
description. - Do not use this skill when the primary task falls outside this skill's domain.
Inputs To Gather
- Candidate algorithms and dominant operations.
- Input-scale assumptions (current, expected, and stress ranges).
- Resource budgets (latency targets, throughput targets, memory limits).
- Runtime context (I/O patterns, cache behavior, concurrency contention).
Deliverables
- Complexity report with worst-case, average-case, and amortized bounds (as applicable).
- Memory and auxiliary-space analysis, including peak usage assumptions.
- Budget-fit assessment and scalability breakpoints.
- Recommendation with residual risk and monitoring triggers.
Quality Standard
- Complexity claims are tied to explicit assumptions and units.
- Dominant operations and constants relevant at target scale are identified.
- CPU, memory, I/O, and contention effects are addressed where applicable.
- Analysis states confidence level and uncertainty sources.
- Decision includes conditions that would invalidate the current choice.
Workflow
- Define workload model, scale assumptions, and performance budgets.
- Derive formal bounds for each candidate's critical operations.
- Evaluate real-world cost drivers (constants, I/O, cache, contention).
- Compare candidates against budgets and identify breakpoints.
- Publish recommendation, residual risks, and re-evaluation triggers.
Failure Conditions
- Stop when workload/scale assumptions are missing.
- Stop when dominant cost drivers are unmodeled.
- Escalate when no candidate can satisfy mandatory budgets.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9