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.
80%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./.gemini/skills/cs-backend-review/SKILL.mdUse the cs-backend-engineer agent (uses context: fork) to handle this inquiry:
$ARGUMENTS
Canonical source: engineering-team/skills/senior-backend/references/forcing_questions.md (7 questions, one-per-turn, recommendation + canon citation per question).
engineering-team/skills/senior-backend/references/forcing_questions.md. One per turn. Recommend with cited canon. Track in /tmp/backend-grill-<date>.md.python engineering-team/skills/senior-backend/scripts/backend_decision_engine.py \
--team-size <N> --qps-p99 <N> --read-write-ratio <ratio> \
--tenancy <single-tenant|shared-multi-tenant|isolated-multi-tenant> \
--data-sensitivity <public|pii|phi|pci> \
--pattern <monolith|modular-monolith|domain-bounded-services|microservices|serverless> \
--language-preference <typescript|python|go|rust|java|kotlin|dotnet>slo-architect FIRST — no SLO, no designapi-design-reviewer — API contractdatabase-designer + database-schema-designer — schema + ERDmigration-architect — only if changing existing schemaobservability-designer — golden signals + alertsci-cd-pipeline-builder — pipeline matching cadence targetsenior-security + adversarial-reviewer — before public launchra-qm-team/* — if data sensitivity is PHI / PCI / regulatedcs-karpathy-reviewer — before any commitapi-design-reviewer.Profiles live at engineering-team/skills/senior-backend/profiles/. Four built-in: node-express, fastapi-python, django-monolith, go-or-rust-microservice. Copy one to <your-org>.json and adjust constraints / SLO floor / approver chain.
/cs:fullstack-review — full-stack lens (parent)/cs:frontend-review — for API consumer side/cs:engineer-grill — cross-role 21-question grill/slo-design — explicit SLO design via slo-architect/karpathy-check — Karpathy 4-principle reviewalirezarezvani/claude-skills
5909a72
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.