algorithm-design
Algorithm Design
Overview
Use this skill to produce an implementable algorithm decision with explicit correctness reasoning and tradeoff analysis.
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
- Objective, required outputs, and correctness conditions.
- Input constraints (size ranges, distribution, adversarial cases, update/query patterns).
- Resource budgets (latency, throughput, memory) and operational constraints.
- Mutation/concurrency requirements and ordering guarantees.
Deliverables
- Problem model with assumptions, invariants, and edge-case catalog.
- Candidate strategy comparison (pros/cons and applicability bounds).
- Selected algorithm and data-structure decision with correctness argument.
- Risk list and follow-up verification plan.
Quality Standard
- Assumptions are explicit, measurable, and linked to requirement context.
- Correctness argument includes invariant/termination reasoning or equivalent proof sketch.
- Selected and rejected options include complexity and operability tradeoffs.
- Data-structure choices are justified by access/mutation patterns.
- Edge cases and failure modes are identified before implementation.
Workflow
- Formalize the problem, constraints, and success criteria.
- Enumerate candidate strategies at the same abstraction level.
- Evaluate correctness risk, complexity, and implementation/operational tradeoffs.
- Select algorithm and data structures with explicit rationale.
- Define edge-case tests and evidence needed to validate the decision.
Failure Conditions
- Stop when constraints are unknown or contradictory.
- Stop when no candidate has a defensible correctness argument.
- Escalate when feasible options conflict with mandatory resource 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