# Scale Readiness Review

> Reviews code and architecture for scalability bottlenecks, capacity limits, data growth, query cost, queue behavior, and failure modes. Use for higher volume, batch growth, more tenants, larger ledgers, or market-data throughput.

- Skill: `rockclaver/scale-readiness-review` (Agent Skill)
- Install (CLI): `npx skillmds@latest add rockclaver/scale-readiness-review`
- Raw SKILL.md: https://api.skillmd.com/api/skills/rockclaver/scale-readiness-review/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: rockclaver (https://skillmd.com/u/rockclaver)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/rockclaver/scale-readiness-review

---


# Scale Readiness Review

## Workflow

1. **Establish assumptions**: peak req/job rate, batch/file frequency, ledger growth/day, tenant skew, provider limits, retention needs; if unknown, state conservative assumptions.
2. **Inspect hot paths**: N+1 queries, missing indexes, unbounded list/export/reconciliation endpoints, full-table scans in jobs, large locking transactions, sync work belonging in a job, queue jobs missing retry/DLQ/backpressure, stale-truth caches.
3. **Review data growth**: partitioning/archival, pagination contracts, tenant isolation, rebuild paths for derived balances/projections, reconciliation strategy for drift.
4. **Recommend**: covering index/uniqueness constraint, bounded-page batching, outbox/worker for slow effects, idempotency/retry before more concurrency, metrics for queue/latency/failure/drift, a narrow load test.
5. **Verify**: query plans, unit/integration tests for pagination/batching/idempotency, benchmarks for hot functions, load tests where a harness exists, metrics/logs for visibility.

## Output Format

```text
Finding: unbounded reconciliation query can scan all ledger rows.
Impact: batch runtime grows with total history, not daily volume.
Fix: page by posting date and account id; add an index on (...)
Verification: run query plan and reconciliation integration test.
```

## Guardrails

- Do not optimize before the path is proven relevant to scale.
- Do not cache financial truth without freshness/invalidation rules.
- Do not increase concurrency until idempotency/locking is clear.
- Do not propose a rewrite when a bounded query, index, or queue boundary solves it.