cs:engineer

--- description: "Cross-role engineering grill : Matt Pocock 7 questions per role × 3 roles (fullstack /frontend /backend ) = up to 21 challenging questions, one per turn, with canonical citations and elimination criteria. Default: ask which lane first;--all runs all 21." argument-hint: "<plan or architecture to grill> [--lane fullstack|frontend |backend |all]" --- #/cs :engineer-grill : Cross-role engineering forcing-question grill Walk the user through the Matt Pocock forcing-question discipline before they lock in 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 1. Detect lane signals in the user’s webprompt s: - Full-stack 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" 2. **If a "--lane <name> " is provided: go through only the 7 questions in that lane. 3. If lane signals score ≥ 3 hits for a single lane: confirm with the user, then go through the 7 questions in that lane. 4. If lane signals are ambiguous OR--lane all :** ask the user: “Full-stack (7 questions about team / stack / scale), Frontend (7 questions about device / rendering / bundle / a11y), or Backend (7 questions about QPS / tenancy / pattern / SLO)? Orall for all 21." ## Lane: fullstack Questions are available atengineering-team/skills/senior-fullstack/references/forcing_questions.md . Summary: 1. Current team size + 12-month headcount? 2. Deployment cadence:per pull request, daily, weekly, quarterly? 3. Customer-facing, internal tool, or marketing site? 4. One-year p50 / p99 traffic forecast? 5. Hiring for the stack or training the team? 6. Year-one monthly cloud + SaaS ceiling? 7. Three verifiable success criteria with numerical targets? ## Lane:frontend Questions are posted atengineering-team/skills/senior-frontend/references/forcing_questions.md . Summary: 1. Primary device and network (mobile-4G / desktop-fiber / low-end Android / corporate)? 2. LCP target in ms (and INP, CLS)? 3. RSC / SPA / SSR / SSG : pick and defend? 4. JS bundle budget per route in KB-gzip? 5.SEO -dependent or behind an authentication wall? 6. Design system source of truth? 7. WCAG target + designated accessibility owner? ## Lane:backend Questions are posted atengineering-team/skills/senior-backend/references/forcing_questions.md . Summary: 1. Read/write ratio + p99 QPS forecast? 2. Tenancy model : single / shared / isolated? 3. Sync / async / event-driven : default + exceptions? 4. Data sensitivity tier : PII / PHI / PCI? 5. Monolith / modular monolith / microservices : team-size justification? 6. RPO + RTO? 7. SLO + named error-budget consumer? ## Guidelines (Matt Pocock, MIT, reproduced verbatim fromengineering/grill-me ) 1. One question per turn. Never bundle questions. Never default to “what do you think?” 2. Always recommend an answer. Format: “Recommended: <answer>, because <one-sentence rationale from cited canon>.” 3. Walk depth-first. Finish one lane before opening another. 4. Surface the kill criterion. If the user's answer triggers it, STOP and resolve the issue before continuing. 5. Track answers. Write to/tmp/engineer-grill-<lane>-<date>.md so the conversation survives compaction. ## After the grill 1. 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 ... 2. Surface the matched profile + named approvers. 3. Recommend the next subskill chain based on the composition map. ## Output expectations - One artifact per lane processed, written to/tmp/engineer-grill-<lane>-<date>.md . - One final digest (≤