scalability-playbook

Identify system bottlenecks and generate a phased scaling plan with triggers and cost implications.

Updated Jan 21, 2026
One-click install
npx skills add https://github.com/vecear/Nipponverb --skill scalability-playbook-vecear
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scalability-playbook
Source: https://github.com/vecear/Nipponverb/tree/main/.claude/skills/scalability-playbook
Command: npx skills add https://github.com/vecear/Nipponverb --skill scalability-playbook-vecear

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Identify bottlenecks in the current system and provide a structured scaling plan with triggers and cost implications.

Core Features & Use Cases

  • Bottleneck detection and measurement framework
  • Ordered scaling plan with triggers, phased actions, and cost considerations
  • Load testing, baselining, and capacity planning guidance
  • Guidance for phased rollout from quick wins to architecture changes
  • Use cases: capacity planning for traffic growth, multi-region deployment, or data expansion

Quick Start

Run the scalability playbook to identify bottlenecks and generate an ordered scaling plan with triggers and cost estimates.

Frequently Asked Questions about scalability-playbook

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is a structured scalability plan and how does it help with capacity planning?

A structured scalability plan identifies current system bottlenecks and provides an ordered growth roadmap across phased levels. It helps with capacity planning by defining measurable triggers, actionable steps, and cost implications for increasing traffic, users, and data.

How do I identify system bottlenecks before planning for multi-region deployment or traffic growth?

You can identify system bottlenecks by applying a dedicated measurement framework that uses load testing and baselining. This process highlights performance limits under increasing traffic or data expansion, providing measurable triggers for when scaling actions are required.

What's the best way to create a phased scaling plan with cost implications?

The best way to create a phased scaling plan is to order actions from quick wins to major architecture changes. Each phase should include specific deployment triggers, guardrails for safe rollout, and clear cost estimates to guide capacity planning and growth scenarios.

How do I measure load testing baselines to trigger architecture changes?

You measure load testing baselines by evaluating system performance under simulated growth scenarios to find breaking points. These baselines establish measurable triggers that dictate when to execute specific scaling actions or transition to deeper architecture changes.

Does this capacity planning approach work for both traffic growth and data expansion scenarios?

Yes, this capacity planning approach works for both scenarios by applying a bottleneck detection framework to measure system limits. It generates tailored scaling plans with phased timelines and cost considerations regardless of whether the growth is traffic, users, or data.

When should I avoid quick wins and move directly to major architecture changes for scalability?

You should bypass quick wins and move to architecture changes when load testing baselines show that current bottlenecks fundamentally prevent handling projected traffic or data expansion. The structured scaling plan uses measurable triggers to determine exactly when deeper architectural interventions are required.