Command
/cs-fullstack-review
Fullstack engineering review — walks the 7 Matt Pocock forcing questions, picks the profile, forks into POWERFUL specialists (api-design-reviewer, database-designer, slo-architect). Invokes the cs-fullstack-engineer agent with context fork.
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-fullstack-review
Context preview
What this command does when you run it.
Fullstack engineering review — walks the 7 Matt Pocock forcing questions, picks the profile, forks into POWERFUL specialists (api-design-reviewer, database-designer, slo-architect). Invokes the cs-fullstack-engineer agent with context fork.
Stats
Stars23,056
Forks3,139
LanguagePython
LicenseMIT
Ships with claude-skills
Command definition
cs-fullstack-review.md
--- description: Fullstack engineering review — walks the 7 Matt Pocock forcing questions, picks the profile, forks into POWERFUL specialists (api-design-reviewer, database-designer, slo-architect). Invokes the cs-fullstack-engineer agent with context fork. argument-hint: "<problem or codebase to review>" --- # /cs:fullstack-review — Fullstack engineering review Use the `cs-fullstack-engineer` agent (which uses `context: fork` to keep the parent thread clean) to handle this inquiry: **$ARGUMENTS** ## Forcing-question library Canonical source: `engineering-team/skills/senior-fullstack/references/forcing_questions.md` (7 questions, one-per-turn, recommendation + canon citation per question). 1. Team size now + 12-month headcount 2. Deployment cadence (per-PR / daily / weekly / quarterly) 3. Customer-facing / internal tool / marketing site 4. One-year p50 + p99 traffic forecast 5. Hiring-against vs training-into the stack 6. Year-one monthly cloud + SaaS budget ceiling 7. Three verifiable success criteria with numeric targets ## Routing protocol 1. **Walk the 7 forcing questions** in `engineering-team/skills/senior-fullstack/references/forcing_questions.md`. One per turn. Recommend the answer with cited canon. Track in `/tmp/fullstack-grill-<date>.md`. 2. **Surface kill criteria** — if any question trips one (e.g., "microservices day 1, team size 3"), STOP and resolve before proceeding.
