Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

/cs:engineer-grill — Cross-role engineering forcing-question grill — measured AI agent skill | DecimalAI

alirezarezvani/csengineer-grill-cross-role-engineering-forcing-question-grill

SkillScore55Maintained

Cross-role engineering grill — Matt Pocock 7 questions per role × 3 roles (fullstack / frontend / backend) = up to 21 forcing questions, one per turn, with canon citations and kill criteria. Default: ask which lane first; `--all` runs all 21.

by alirezarezvani

Links this skill to your agents and keeps it current with the author’s updates.

Automatic

Coding pack

decimalai skills pull alirezarezvani-csengineer-grill-cross-role-engineering-forcing-question-grill

Get this skill — curl · raw file

curl -fsSL https://app.decimal.ai/s/alirezarezvani-csengineer-grill-cross-role-engineering-forcing-question-grill/SKILL.md

Raw file: /s/alirezarezvani-csengineer-grill-cross-role-engineering-forcing-question-grill/SKILL.md ↗ · machine-readable summary at /s/alirezarezvani-csengineer-grill-cross-role-engineering-forcing-question-grill.json ↗

In productionGlobal

how this skill behaves on real traffic · last 30 days

No production data for this skill yet — usage numbers appear here once agents start running it.

Anonymized aggregate across every org using this skill — proof from real production use, not a demo.

Does this skill help? · Benchmark: with vs. withoutsign in to run this on your agents

22 test cases from the publisher’s eval.yaml · each run twice on gemini-3.6-flash — with the skill injected, then without · last run 3h ago

—+5% tokens0% turns55% of whole cases pass with skill (12/22)

Test case	Without → With	Effect	Δ tokens	Δ turns
case-04	✗→✓	▲ Improved	18%	0%
case-05	✗→✓	▲ Improved	208%	0%
case-06	✗→✓	▲ Improved	115%	0%
case-07	✗→✓	▲ Improved	12%	0%
case-11	✗→✓	▲ Improved	-7%	0%

Showing 5 of 22 cases

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v4 — 8/3/2026

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

alirezarezvani / claude-skills

.gemini/skills/cs-engineer-grill/SKILL.md

View on GitHub ↗

License MITImported 8/3/2026Version v1

Skill contents

SKILL.md

/cs:engineer-grill — Cross-role engineering forcing-question grill

Walk the user through the Matt Pocock forcing-question discipline before they lock any engineering decision. This is the grill-with-docs pattern (canon-anchored, recommended answers, kill criteria) applied across the three engineering role lanes.

$ARGUMENTS

Routing protocol

Detect lane signals in the user's prompt:

Fullstack signals: "scaffold", "stack", "Next.js + Postgres", "monorepo", "deploy", "team size", "budget", "cadence"
Frontend signals: "React", "Next", "Remix", "Vite", "Astro", "bundle", "LCP", "INP", "CLS", "a11y", "WCAG", "Tailwind", "design system"
Backend signals: "API", "REST", "GraphQL", "database", "Postgres", "MongoDB", "schema", "migration", "QPS", "tenancy", "SLO", "Kafka", "queue", "microservice", "monolith"

If --lane <name> is supplied: walk only that lane's 7 questions.
If lane signals score ≥ 3 hits for one lane: confirm with the user, then walk that lane's 7 questions.
If lane signals are ambiguous OR --lane all: ask the user: "Fullstack (7 Qs about team / stack / scale), Frontend (7 Qs about device / rendering / bundle / a11y), or Backend (7 Qs about QPS / tenancy / pattern / SLO)? Or all for all 21."

Lane: fullstack

Questions live in engineering-team/skills/senior-fullstack/references/forcing_questions.md. Summary:

Team size today + 12-month headcount?
Deployment cadence — per-PR, daily, weekly, quarterly?
Customer-facing, internal tool, or marketing site?
One-year p50 / p99 traffic forecast?
Hiring against the stack or training the team?
Year-one monthly cloud + SaaS ceiling?
Three verifiable success criteria with numeric targets?

Lane: frontend

Questions live in engineering-team/skills/senior-frontend/references/forcing_questions.md. Summary:

Primary device + network (mobile-4G / desktop-fiber / low-end Android / corporate)?
LCP target in ms (and INP, CLS)?
RSC / SPA / SSR / SSG — pick and defend?
JS bundle budget per route in KB-gzip?
SEO-dependent or auth-walled?
Design-system source of truth?
WCAG target + named a11y owner?

Lane: backend

Questions live in engineering-team/skills/senior-backend/references/forcing_questions.md. Summary:

Read/write ratio + p99 QPS forecast?
Tenancy model — single / shared / isolated?
Sync / async / event-driven — default + exceptions?
Data sensitivity tier — PII / PHI / PCI?
Monolith / modular monolith / microservices — team-size justification?
RPO + RTO?
SLO + named error-budget consumer?

Discipline (Matt Pocock, MIT, preserved verbatim from `engineering/grill-me`)

One question per turn. Never bundle. Never default to "what do you think?".
Always recommend an answer. Format: "Recommended: <answer>, because <one-sentence rationale from cited canon>".
Walk depth-first. Finish a lane before opening another.
Surface the kill criterion. If the user's answer trips it, STOP and resolve before continuing.
Track answers. Write to /tmp/engineer-grill-<lane>-<date>.md so the conversation survives compaction.

After the grill

Run the lane's decision engine with the seven answers:

Fullstack → python engineering-team/skills/senior-fullstack/scripts/fullstack_decision_engine.py ...
Frontend → python engineering-team/skills/senior-frontend/scripts/frontend_decision_engine.py ...
Backend → python engineering-team/skills/senior-backend/scripts/backend_decision_engine.py ...

Surface the matched profile + named approvers.
Recommend the next sub-skill chain based on the composition map.

Output expectations

One artifact per lane walked, written to /tmp/engineer-grill-<lane>-<date>.md.
One final digest (≤ 250 words) summarizing the matched profile per lane + the three highest-leverage next actions.
Never auto-approve a stack change, schema migration, or architecture choice.

Related commands

/cs:fullstack-review, /cs:frontend-review, /cs:backend-review — single-lane deep dives
/karpathy-check — Karpathy review before commit
/cs:grill-bizops, /cs:grill-commercial — sibling cross-domain grills (BizOps + Commercial v2.8.0)

Want to see if alirezarezvani/csengineer-grill-cross-role-engineering-forcing-question-grill would activate on your phrasing? Try it before you install — no LLM call, no signup.

Other measured skills in the registry, with their headline benchmark lift.