Claude Skill

capacity-planning-analysis

Use this skill when you need to assess capacity demand, headroom, constraints, and planning assumptions; triggers include capacity planning analysis.

LLM Mart · 0 points · 1 views 0 listing impressions 0 install-command copies
Download naodeng-awesome-qa-skills-skills_en_testing-types_capacity-planning-analysis-9df700b.zip · 13 KB

Install

skills CLI npx skills add https://github.com/naodeng/awesome-qa-skills/tree/main/skills/en/testing-types/capacity-planning-analysis
Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install naodeng-awesome-qa-skills@llmmart
Git git clone https://github.com/naodeng/awesome-qa-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole naodeng/awesome-qa-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Capacity Planning Analysis

When to Use

  • Use this skill when you need to estimate capacity needs and scaling triggers from workload, utilization, and growth assumptions.
  • Use it to review an existing plan, result, or evidence set and produce actionable improvements.
  • Use it when context is incomplete but a bounded first pass is still valuable.

Output Format Options

  • Default to Markdown for review, execution, and incremental refinement.
  • When the user requests tables, CSV, JSON, or ticket fields, preserve risk, evidence, priority, and boundary information.
  • For machine-consumed output, confirm the schema, enums, and required fields first.

How to Use

  1. Read and follow prompts/capacity-planning-analysis.md, including its input contract, execution rules, minimum coverage, and output order.
  2. Add only context that changes the decision: scope, environment, version, constraints, evidence, and success criteria.
  3. Audit the input, then separate confirmed facts, working assumptions, and open questions.
  4. Rank by risk and evidence strength, and produce an artifact that can be executed or reviewed directly.
  5. If information is missing, deliver a bounded first pass and state which conclusions remain unsupported.

Reference Files

  • When calibrating domain outcomes, valid controls, or evidence gaps, read references/domain-decision-example.md for sanitized input, per-item oracles, and reproducible calculations.

  • Always read prompts/capacity-planning-analysis.md; it is the complete execution specification for this skill.

  • For evaluation or regression, read evals/eval.yaml and the relevant cases under evals/cases/.

  • Load references/, examples/, scripts/, or output-formats.md only when those directories exist and the task needs them.

Domain Execution Essentials

  1. For each point record environment/config/instances, workload mix, arrival/completion throughput, latency percentiles, errors, CPU/memory/queues, and window. Trace measurement→SLO→candidate capacity.
  2. Estimate only within measured SLO-acceptable regions. CPU percentage cannot linearly predict throughput; unmeasured points remain candidates constrained by downstream saturation/scaling delay.
  3. Under supplied constant-rate/queue assumptions, scaling-wait backlog=max(0,arrivals−validated service rate)×wait seconds; check backlog latency/recovery, not only totals.
  4. Use measured or explicitly conditional capacity after project-specified instance/dependency failure. Missing failure data cannot establish adequate headroom; margin, growth, cost, and acceptance come from the project.

Core Constraints

  • use ranges instead of false precision when data is missing
  • separate averages from peaks
  • tie capacity conclusions to SLOs and validation
  • Never invent system behavior, fields, data, metrics, or root causes absent from the evidence.
  • Link important conclusions to evidence; mark unsupported conclusions as hypotheses with a verification method.
  • Explain priority using business impact, likelihood, or detectability.

Delivery Checklist

  • Covered: peaks and bursts, concurrency and throughput, resource bottlenecks, safety margin, growth scenarios, degradation, cost, scaling lead time.
  • Separated facts, assumptions, gaps, and recommendations.
  • Gave high-risk items a priority, evidence basis, owner or next action.
  • Defined verifiable decision criteria instead of generic advice.
  • Performed no unauthorized production writes or destructive actions.

Common Pitfalls

  • Listing checks without preconditions, expected outcomes, or evidence.
  • Marking everything high priority and avoiding tradeoffs.
  • Substituting tool names or generic theory for domain reasoning.
  • Refusing incomplete input, or pretending incomplete evidence supports certainty.

Best Practices

  • Start with paths most likely to cause business loss, safety issues, or release blockage.
  • Reduce uncertainty through the smallest verifiable experiment and record reproduction conditions.
  • Make the artifact executable and independently reviewable by another engineer.
Files (awesome-qa-skills)
  • agents
    • openai.yaml 316 B
      Loading…
  • evals
    • cases
      • basic-success.yaml 867 B
        Loading…
      • domain-method-regression.yaml 1.5 KB
        Loading…
      • edge-incomplete-input.yaml 908 B
        Loading…
      • edge-risk-priority.yaml 867 B
        Loading…
      • phase-1-project-context.yaml 4 KB
        Loading…
    • fixtures
      • check-domain-decisions.sh 95 B
        Loading…
      • check_domain_decisions.py 3.8 KB
        Loading…
      • domain-oracle.json 215 B
        Loading…
    • eval.yaml 652 B
      Loading…
  • prompts
    • capacity-planning-analysis.md 4.8 KB
      Loading…
  • references
    • domain-decision-example.md 1.6 KB
      Loading…
  • SKILL.md 4.6 KB
    ---
    name: capacity-planning-analysis
    description: Use this skill when you need to assess capacity demand, headroom, constraints, and planning assumptions; triggers include capacity planning analysis.
    license: PolyForm-Noncommercial-1.0.0
    metadata:
      version: "1.0.0"
      compatibility: ""
      author: "Awesome QA Skills contributors"
      language: "en"
      category: "testing-types"
      source: "https://github.com/naodeng/awesome-qa-skills"
      license-url: "https://polyformproject.org/licenses/noncommercial/1.0.0"
    ---
    
    # Capacity Planning Analysis
    
    ## When to Use
    
    - Use this skill when you need to estimate capacity needs and scaling triggers from workload, utilization, and growth assumptions.
    - Use it to review an existing plan, result, or evidence set and produce actionable improvements.
    - Use it when context is incomplete but a bounded first pass is still valuable.
    
    ## Output Format Options
    
    - Default to Markdown for review, execution, and incremental refinement.
    - When the user requests tables, CSV, JSON, or ticket fields, preserve risk, evidence, priority, and boundary information.
    - For machine-consumed output, confirm the schema, enums, and required fields first.
    
    ## How to Use
    
    1. Read and follow `prompts/capacity-planning-analysis.md`, including its input contract, execution rules, minimum coverage, and output order.
    2. Add only context that changes the decision: scope, environment, version, constraints, evidence, and success criteria.
    3. Audit the input, then separate confirmed facts, working assumptions, and open questions.
    4. Rank by risk and evidence strength, and produce an artifact that can be executed or reviewed directly.
    5. If information is missing, deliver a bounded first pass and state which conclusions remain unsupported.
    
    ## Reference Files
    
    - When calibrating domain outcomes, valid controls, or evidence gaps, read [references/domain-decision-example.md](references/domain-decision-example.md) for sanitized input, per-item oracles, and reproducible calculations.
    
    - Always read `prompts/capacity-planning-analysis.md`; it is the complete execution specification for this skill.
    - For evaluation or regression, read `evals/eval.yaml` and the relevant cases under `evals/cases/`.
    - Load `references/`, `examples/`, `scripts/`, or `output-formats.md` only when those directories exist and the task needs them.
    
    ## Domain Execution Essentials
    
    1. For each point record environment/config/instances, workload mix, arrival/completion throughput, latency percentiles, errors, CPU/memory/queues, and window. Trace measurement→SLO→candidate capacity.
    2. Estimate only within measured SLO-acceptable regions. CPU percentage cannot linearly predict throughput; unmeasured points remain candidates constrained by downstream saturation/scaling delay.
    3. Under supplied constant-rate/queue assumptions, scaling-wait backlog=max(0,arrivals−validated service rate)×wait seconds; check backlog latency/recovery, not only totals.
    4. Use measured or explicitly conditional capacity after project-specified instance/dependency failure. Missing failure data cannot establish adequate headroom; margin, growth, cost, and acceptance come from the project.
    ## Core Constraints
    
    - use ranges instead of false precision when data is missing
    - separate averages from peaks
    - tie capacity conclusions to SLOs and validation
    - Never invent system behavior, fields, data, metrics, or root causes absent from the evidence.
    - Link important conclusions to evidence; mark unsupported conclusions as hypotheses with a verification method.
    - Explain priority using business impact, likelihood, or detectability.
    
    ## Delivery Checklist
    
    - [ ] Covered: peaks and bursts, concurrency and throughput, resource bottlenecks, safety margin, growth scenarios, degradation, cost, scaling lead time.
    - [ ] Separated facts, assumptions, gaps, and recommendations.
    - [ ] Gave high-risk items a priority, evidence basis, owner or next action.
    - [ ] Defined verifiable decision criteria instead of generic advice.
    - [ ] Performed no unauthorized production writes or destructive actions.
    
    ## Common Pitfalls
    
    - Listing checks without preconditions, expected outcomes, or evidence.
    - Marking everything high priority and avoiding tradeoffs.
    - Substituting tool names or generic theory for domain reasoning.
    - Refusing incomplete input, or pretending incomplete evidence supports certainty.
    
    ## Best Practices
    
    - Start with paths most likely to cause business loss, safety issues, or release blockage.
    - Reduce uncertainty through the smallest verifiable experiment and record reproduction conditions.
    - Make the artifact executable and independently reviewable by another engineer.
    

Comments (0)

Sign in to join the conversation.

No comments yet.

Reviews (0)

No reviews yet.