Command
/cs-backend-review
Backend engineering review — walks the 7 Matt Pocock forcing questions (read/write ratio + QPS, tenancy, sync vs async, data sensitivity, pattern, RPO/RTO, SLO), picks the language + pattern profile, forks into specialists (api-design-reviewer, database-designer,
One command from claude-skills.
shell
$ npx -y skills add alirezarezvani/claude-skills --agent claude-codeShips with claude-skills. Installing the plugin gets this command.
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/cs-backend-review
Context preview
What this command does when you run it.
Backend engineering review — walks the 7 Matt Pocock forcing questions (read/write ratio + QPS, tenancy, sync vs async, data sensitivity, pattern, RPO/RTO, SLO), picks the language + pattern profile, forks into specialists (api-design-reviewer, database-designer,
Stats
Stars23,060
Forks3,139
LanguagePython
LicenseMIT
Ships with claude-skills
Command definition
cs-backend-review.md
--- description: Backend engineering review — walks the 7 Matt Pocock forcing questions (read/write ratio + QPS, tenancy, sync vs async, data sensitivity, pattern, RPO/RTO, SLO), picks the language + pattern profile, forks into specialists (api-design-reviewer, database-designer, migration-architect, slo-architect). Invokes the cs-backend-engineer agent with context fork. argument-hint: "<problem or service to review>" --- # /cs:backend-review — Backend engineering review Use the `cs-backend-engineer` agent (uses `context: fork`) to handle this inquiry: **$ARGUMENTS** ## Forcing-question library Canonical source: `engineering-team/skills/senior-backend/references/forcing_questions.md` (7 questions, one-per-turn, recommendation + canon citation per question). 1. Read/write ratio + one-year p99 QPS 2. Tenancy model (single / shared / isolated multi-tenant) 3. Sync request/response vs async (queue) vs event-driven 4. Data sensitivity tier (public / internal / PII / PHI / PCI) 5. Monolith / modular monolith / microservices (team-size justification) 6. RPO and RTO 7. SLO + named error-budget consumer ## Routing protocol 1. **Walk the 7 forcing questions** in `engineering-team/skills/senior-backend/references/forcing_questions.md`. One per turn. Recommend with cited canon. Track in `/tmp/backend-grill-<date>.md`. 2. **Surface kill criteria** — e.g., "microservices, team size 5" trips (Newman's MonolithFirst). STOP and resolve.
