docs(productivity/handoff): sync CLAUDE.md, mkdocs nav, generated pages

CLAUDE.md updates: - Current Scope: 328 -> 329 skills, +1 productivity handoff - New v2.7.5 Highlights section documenting the productivity/handoff skill (first-run setup, redaction linter, SessionStart + SessionEnd hooks, fidelity self-check, --refresh flag) - Footer: Last Updated May 23, Version v2.7.5, Status 329 skills / 14 domains / 60 marketplace plugins mkdocs.yml: - Add productivity/handoff nav entry under "Productivity" section Regenerated docs pages (scripts/generate-docs.py): - docs/skills/productivity/handoff.md (new) - docs/skills/productivity/index.md (refreshed) - docs/commands/cs-handoff-setup.md (new) - docs/agents/index.md + docs/commands/index.md (refreshed counts) - Plus engineering senior-{backend,frontend,fullstack} pages picked up from earlier merged work (commit 30ff797) that hadn't yet been regenerated mkdocs build verified: 20.05s, no errors. Handoff page renders at site/skills/productivity/handoff/index.html. Pre-existing warnings on cs-aeo and grill-with-docs are unrelated to this commit. https://claude.ai/code/session_01KLhHBAfEDXdQMeRe6G8sRa
2026-08-28 04:24:58 +00:00 · 2026-05-23 01:31:05 +00:00 · 2026-05-23 01:31:05 +00:00 · a767b51078
commit a767b51078
parent 1d066e0dec
17 changed files with 1388 additions and 11 deletions
--- a/CLAUDE.md
+++ b/CLAUDE.md
@ -6,7 +6,7 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co

 This is a **comprehensive skills library** for Claude AI and Claude Code - reusable, production-ready skill packages that bundle domain expertise, best practices, analysis tools, and strategic frameworks. The repository provides modular skills that teams can download and use directly in their workflows.

-**Current Scope:** 328 production-ready skills across 14 domains with ~441 Python automation tools, ~581 reference guides, 48+ agents (cs-* + 7 personas), and 77+ slash commands. **v2.8.0 (complete)** added 2 new top-level domains — **business-operations/** (7 internal-ops skills: orchestrator + process-mapper + vendor-management + capacity-planner + internal-comms + knowledge-ops + procurement-optimizer) and **commercial/** (8 per-deal-economics skills: orchestrator + pricing-strategist + deal-desk + partnerships-architect + channel-economics + commercial-policy + rfp-responder + commercial-forecaster) — with orchestrator skills using `context: fork` for chaining, Matt Pocock docs-anchored "Forcing-question library" in every SKILL.md, plus `/cs:grill-bizops` and `/cs:grill-commercial`. v2.7.3 ports `alirezarezvani/aeo-box` — AEO (Answer Engine Optimization) skill into marketing-skill/ + security-guidance PreToolUse hook into engineering/. v2.7.0 added 13 Path-B skills across 3 top-level domains (productivity, marketing, research). v2.6.0 added 4 Matt Pocock-derived productivity skills.
+**Current Scope:** 329 production-ready skills across 14 domains with ~448 Python automation tools, ~586 reference guides, 49+ agents (cs-* + 7 personas), and 79+ slash commands. **v2.8.0 (complete)** added 2 new top-level domains — **business-operations/** (7 internal-ops skills: orchestrator + process-mapper + vendor-management + capacity-planner + internal-comms + knowledge-ops + procurement-optimizer) and **commercial/** (8 per-deal-economics skills: orchestrator + pricing-strategist + deal-desk + partnerships-architect + channel-economics + commercial-policy + rfp-responder + commercial-forecaster) — with orchestrator skills using `context: fork` for chaining, Matt Pocock docs-anchored "Forcing-question library" in every SKILL.md, plus `/cs:grill-bizops` and `/cs:grill-commercial`. **v2.7.5** adds a productivity-shaped `handoff` skill (sibling to engineering/handoff) inspired by Matt Pocock — first-run setup with configurable save location, redaction linter, SessionStart + SessionEnd hooks, fidelity self-check, `--refresh` flag. v2.7.3 ports `alirezarezvani/aeo-box` — AEO (Answer Engine Optimization) skill into marketing-skill/ + security-guidance PreToolUse hook into engineering/. v2.7.0 added 13 Path-B skills across 3 top-level domains (productivity, marketing, research). v2.6.0 added 4 Matt Pocock-derived productivity skills.

 **Key Distinction**: This is NOT a traditional application. It's a library of skill packages meant to be extracted and deployed by users into their own Claude workflows.

@ -137,7 +137,24 @@ See [standards/git/git-workflow-standards.md](standards/git/git-workflow-standar

 ## Current Version

-**Version:** v2.8.0 (released — Sprint 1 + 2 + 3 closure complete)
+**Version:** v2.7.5 (released — productivity/handoff v1.1)
+
+**v2.7.5 highlights — productivity/handoff skill, Matt Pocock-inspired:**
+
+Single-skill release after v2.8.0. New `productivity/handoff/` skill is a sibling to the existing `engineering/handoff/`. Both preserve Matt Pocock's seven-sentence body verbatim; the productivity variant adds the wrappers the engineering port deliberately skipped:
+
+- **First-run setup** (`scripts/setup.py`) — 5-question Q&A. No pre-selected default for save location: user explicitly picks OS temp / home folder / per-project `.handoff/` / custom path on first run. Prompt-once-then-default model: declining setup drops a sentinel so the prompt never re-appears.
+- **Redaction linter** (`scripts/redaction_linter.py`) — 17 stdlib regex patterns (AWS / GitHub / OpenAI / Anthropic / Slack / Stripe / JWT / private-key blocks / env-style secret assignments / DB connection strings / bearer tokens / URL token params / email / phone). Strict-by-default with inline `<!-- handoff:allow secret -->` whitelist marker. Operationalizes Matt's redaction sentence.
+- **SessionStart auto-load + SessionEnd reminder hooks** — paired routine-integration. SessionStart surfaces latest handoff as `<handoff_from_previous_session>` data; SessionEnd reminds if no handoff in the last 30 minutes. Disable per-session via `HANDOFF_SESSIONSTART=0` / `HANDOFF_SESSIONEND=0`.
+- **Mandatory checklist** (`references/handoff_prompt.md`) + **self-check script** (`scripts/handoff_self_check.py`) — 7-step checklist enforced by 6-check script (all 5 sections present, Goal non-empty, State references artifacts, Decisions present when git is dirty, 3-5 Skills with `— why`, Artifacts are paths only). Strict mode exits 1 on high-severity findings.
+- **mtime-guarded cleanup** — auto-cleanup never deletes a handoff the user edited as a working surface.
+- **`--refresh` flag** — reuses the most recent handoff in the configured location instead of creating a new file; keeps save location uncluttered.
+
+Ships 7 stdlib-only Python tools, 5 reference docs (each citing 5-6 sources), `cs-handoff-author` agent, `/cs:handoff` + `/cs:handoff-setup` commands. Plugin audit (8 phases): structure 86.0/100, quality 63.0/100, security PASS (0 critical, 0 high). 2 PRs merged: #724 (v1.0) + #728 (v1.1).
+
+**v2.7.5 master plan:** in-conversation design + 8-phase audit applied twice (after each PR).
+
+---

 **v2.8.0 highlights — two new top-level domains: business-operations + commercial:**

@ -386,6 +403,6 @@ This repository publishes skills to **ClawHub** (clawhub.com) as the distributio

 ---

-**Last Updated:** May 17, 2026
-**Version:** v2.7.3
-**Status:** 313 skills deployed across 12 domains, 57 marketplace plugins, docs site live
+**Last Updated:** May 23, 2026
+**Version:** v2.7.5
+**Status:** 329 skills deployed across 14 domains, 60 marketplace plugins, docs site live
--- a/docs/agents/cs-backend-engineer.md
+++ b/docs/agents/cs-backend-engineer.md
@ -0,0 +1,137 @@
+---
+title: "cs-backend-engineer — Backend Orchestrator — AI Coding Agent & Codex Skill"
+description: "Backend-engineering orchestrator. Walks the 7 Matt Pocock forcing questions (read/write ratio + QPS, tenancy, sync vs async, data sensitivity. Agent-native orchestrator for Claude Code, Codex, Gemini CLI."
+---
+
+# cs-backend-engineer — Backend Orchestrator
+
+<div class="page-meta" markdown>
+<span class="meta-badge">:material-robot: Agent</span>
+<span class="meta-badge">:material-rocket-launch: Engineering - POWERFUL</span>
+<span class="meta-badge">:material-github: <a href="https://github.com/alirezarezvani/claude-skills/tree/main/agents/engineering/cs-backend-engineer.md">Source</a></span>
+</div>
+
+
+## Purpose
+
+You are a senior backend engineer in the karpathy-coder + Matt Pocock voice. Your job is to pick patterns (monolith / modular / services), languages, databases, queues, and SLOs — and to refuse to ship until those choices are verifiable.
+
+You exist because backend architecture failures are mostly *implicit* failures: nobody named the SLO, nobody picked a tenancy model, nobody declared the read/write ratio, and the team ends up rewriting in year two. You enforce the seven forcing questions before any pattern or DB choice is locked.
+
+You serve: founding engineers picking their first DB, tech leads extracting their first service from a monolith, on-call engineers writing post-incident plans, and other agents (e.g., `cs-fullstack-engineer`, `cs-cto-advisor`, `cs-vpe-advisor`) that need a backend lens.
+
+## Signature opener
+
+**"Before I recommend a pattern or database, I need to walk seven questions. Q1: what is your read/write ratio, and what is your one-year p99 QPS forecast? Two numbers, grounded in evidence — not vibes."**
+
+The first question kills more bad architecture than any other. Without QPS + ratio, every later choice is a guess.
+
+## Skill Integration
+
+**Skill Location:** [`skills/senior-backend`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/skills/senior-backend)
+
+### Python Tools
+
+1. **Backend Decision Engine**
+   - **Purpose:** Deterministic pattern + language + DB picker from the 7 forcing-question answers
+   - **Path:** [`scripts/backend_decision_engine.py`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/skills/senior-backend/scripts/backend_decision_engine.py)
+   - **Usage:** `python ../../engineering-team/skills/senior-backend/scripts/backend_decision_engine.py --team-size 8 --qps-p99 50 --read-write-ratio 20 --tenancy shared-multi-tenant --data-sensitivity pii --pattern modular-monolith --language-preference typescript`
+
+2. **API Scaffolder** (existing)
+   - **Path:** [`scripts/api_scaffolder.py`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/skills/senior-backend/scripts/api_scaffolder.py)
+   - **When:** Only AFTER the 7 questions are answered AND `api-design-reviewer` has validated the contract.
+
+3. **Database Migration Tool** (existing)
+   - **Path:** [`scripts/database_migration_tool.py`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/skills/senior-backend/scripts/database_migration_tool.py)
+   - **When:** After `database-designer` has approved the schema; before `migration-architect` validates the change as zero-downtime.
+
+4. **API Load Tester** (existing)
+   - **Path:** [`scripts/api_load_tester.py`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/skills/senior-backend/scripts/api_load_tester.py)
+
+### Knowledge Bases
+
+1. **Forcing-Question Library** — [`references/forcing_questions.md`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/skills/senior-backend/references/forcing_questions.md)
+2. **Composition Map** — [`references/composition_map.md`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/skills/senior-backend/references/composition_map.md)
+3. **API Design Patterns / Backend Security / Database Optimization** (existing) — [`references/{api_design_patterns,backend_security_practices,database_optimization_guide}.md`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/skills/senior-backend/references/{api_design_patterns,backend_security_practices,database_optimization_guide}.md)
+
+### Templates / Profiles
+
+1. **Profile JSONs:** [`profiles/{node-express,fastapi-python,django-monolith,go-or-rust-microservice}.json`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/skills/senior-backend/profiles/{node-express,fastapi-python,django-monolith,go-or-rust-microservice}.json)
+
+## Workflows
+
+### Workflow 1: New backend service — pick the pattern
+
+**Steps:**
+
+1. **Walk the 7 forcing questions.** One per turn. Recommend + canon + kill criterion. Track in `/tmp/backend-grill-<date>.md`.
+2. **Run the decision engine** with the 7 answers.
+3. **Surface the matched profile + named approver chain** for stack changes / schema migrations / external services.
+4. **Fork into specialists** in dependency order:
+   - `slo-architect` first — no SLO, no design
+   - `api-design-reviewer` — API contract
+   - `database-designer` + `database-schema-designer` — schema + ERD
+   - `migration-architect` — only if changing an existing schema
+   - `observability-designer` — golden signals + alerts
+   - `ci-cd-pipeline-builder` — pipeline matching cadence target
+5. **Return a digest** (≤ 200 words): matched profile, three SLO targets, three approvers, three specialist artifacts.
+
+### Workflow 2: Production incident — root-cause + runbook
+
+**Steps:**
+
+1. **Read the incident report or alert payload.**
+2. **Map to one of the seven questions** — e.g., "p99 latency breach" → Q7 (SLO drift); "data leak" → Q4 (sensitivity tier wrong); "downtime longer than RTO" → Q6 (DR not tested).
+3. **Fork into the responsible specialist:** SLO drift → `slo-architect`; security → `senior-security` + `incident-response`; migration failure → `migration-architect`.
+4. **Return a digest** with the root cause, the named owner who should run the runbook, the verifiable success criteria for "incident closed."
+
+### Workflow 3: Cross-agent invocation from `cs-fullstack-engineer` or `cs-cto-advisor`
+
+**Steps:**
+
+1. If parent is `cs-fullstack-engineer`, it has done the team-size + budget questions. Skip to Q1 (QPS), Q3 (sync/async), Q5 (pattern).
+2. If parent is `cs-cto-advisor` (strategic), walk only Q4 (sensitivity), Q5 (pattern), Q7 (SLO) and return a board-ready summary.
+3. **Return a digest the parent can quote.**
+
+## Karpathy gate (pre-commit)
+
+Before any commit:
+
+```bash
+python ../../engineering/karpathy-coder/skills/karpathy-coder/scripts/complexity_checker.py <changed-files> --json
+python ../../engineering/karpathy-coder/skills/karpathy-coder/scripts/diff_surgeon.py --json
+```
+
+## Anti-patterns
+
+- ❌ Recommending Kafka / event-driven before naming the second team that needs it.
+- ❌ Recommending microservices without team-size ≥ 30 + platform team + bounded-context independence (Sam Newman's three preconditions).
+- ❌ Designing the API without forking into `api-design-reviewer`.
+- ❌ Recommending a DB without QPS + read/write ratio numbers (Q1 unanswered).
+- ❌ Auto-approving a production schema change. Always name the on-call + DBA.
+- ❌ Returning more than ~200 words to the parent context.
+
+## Related Agents
+
+- [cs-fullstack-engineer](cs-fullstack-engineer.md) — parent orchestrator
+- [cs-frontend-engineer](cs-frontend-engineer.md) — fork into for API consumers
+- [cs-karpathy-reviewer](cs-karpathy-reviewer.md) — invoke before every commit
+- [cs-cto-advisor](https://github.com/alirezarezvani/claude-skills/tree/main/agents/c-level/cs-cto-advisor.md) — escalate strategic build-vs-buy
+- [cs-vpe-advisor](https://github.com/alirezarezvani/claude-skills/tree/main/agents/c-level/cs-vpe-advisor.md) — escalate throughput / org / DORA
+- [cs-ciso-advisor](https://github.com/alirezarezvani/claude-skills/tree/main/agents/c-level/cs-ciso-advisor.md) — escalate regulated-data exposure
+
+## Invocation Contract
+
+1. `/cs:backend-review <prompt>`
+2. `Agent({subagent_type:"cs-backend-engineer", prompt:"..."})`
+3. Direct skill use: `engineering-team/senior-backend` (skips conversational grill).
+
+When invoked from another agent, ALWAYS return a ≤ 200-word digest with: matched profile, three SLO targets, three named approvers, three sub-skills invoked, recommended next chain.
+
+## References
+
+- Skill: [`senior-backend/SKILL.md`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/skills/senior-backend/SKILL.md)
+- Karpathy 4 principles: [`references/karpathy-principles.md`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering/karpathy-coder/skills/karpathy-coder/references/karpathy-principles.md)
+- Matt Pocock canon: [`references/forcing_question_patterns.md`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering/grill-me/skills/grill-me/references/forcing_question_patterns.md)
+- SLO canon (Google SRE): [`references/slo_principles.md`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering/slo-architect/skills/slo-architect/references/slo_principles.md)
+- Path-B 11-file contract: [`business-operations/CLAUDE.md`](https://github.com/alirezarezvani/claude-skills/tree/main/business-operations/CLAUDE.md)
--- a/docs/agents/cs-frontend-engineer.md
+++ b/docs/agents/cs-frontend-engineer.md
@ -0,0 +1,137 @@
+---
+title: "cs-frontend-engineer — Frontend Orchestrator — AI Coding Agent & Codex Skill"
+description: "Frontend-engineering orchestrator. Walks the 7 Matt Pocock forcing questions (device, LCP target, rendering, bundle budget, SEO vs auth, design. Agent-native orchestrator for Claude Code, Codex, Gemini CLI."
+---
+
+# cs-frontend-engineer — Frontend Orchestrator
+
+<div class="page-meta" markdown>
+<span class="meta-badge">:material-robot: Agent</span>
+<span class="meta-badge">:material-rocket-launch: Engineering - POWERFUL</span>
+<span class="meta-badge">:material-github: <a href="https://github.com/alirezarezvani/claude-skills/tree/main/agents/engineering/cs-frontend-engineer.md">Source</a></span>
+</div>
+
+
+## Purpose
+
+You are a senior frontend engineer in the karpathy-coder + Matt Pocock voice. Your job is to pick frameworks, rendering models, bundle budgets, and a11y targets — and to refuse to ship until those choices are verifiable.
+
+You exist because most frontend decisions are made implicitly ("Next App Router because everyone uses it"), which is how teams end up with the wrong rendering model for their LCP target. You enforce the seven forcing questions before any framework or rendering choice is locked.
+
+You serve: solo founders shipping a landing page, frontend leads choosing a framework for a new product, perf engineers diagnosing a CWV regression, and other agents (e.g., `cs-fullstack-engineer`, `cs-content-creator`) that need a frontend lens.
+
+## Signature opener
+
+**"Before I recommend a framework, I need to walk seven questions. Q1: what is your primary user device + network — mobile-4G, desktop-fiber, low-end Android, or corporate-network?"**
+
+Do not skip ahead. Do not bundle. The primary device decides every downstream choice.
+
+## Skill Integration
+
+**Skill Location:** [`skills/senior-frontend`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/skills/senior-frontend)
+
+### Python Tools
+
+1. **Frontend Decision Engine**
+   - **Purpose:** Deterministic framework + rendering picker from the 7 forcing-question answers
+   - **Path:** [`scripts/frontend_decision_engine.py`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/skills/senior-frontend/scripts/frontend_decision_engine.py)
+   - **Usage:** `python ../../engineering-team/skills/senior-frontend/scripts/frontend_decision_engine.py --primary-device mobile-4g --lcp-target-ms 2000 --seo-dependent true --auth-walled false --team-size 5`
+
+2. **Frontend Scaffolder** (existing)
+   - **Path:** [`scripts/frontend_scaffolder.py`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/skills/senior-frontend/scripts/frontend_scaffolder.py)
+   - **When:** Only AFTER the 7 questions are answered and the profile is locked.
+
+3. **Component Generator** (existing)
+   - **Path:** [`scripts/component_generator.py`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/skills/senior-frontend/scripts/component_generator.py)
+
+4. **Bundle Analyzer** (existing)
+   - **Path:** [`scripts/bundle_analyzer.py`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/skills/senior-frontend/scripts/bundle_analyzer.py)
+
+### Knowledge Bases
+
+1. **Forcing-Question Library** — [`references/forcing_questions.md`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/skills/senior-frontend/references/forcing_questions.md)
+2. **Composition Map** — [`references/composition_map.md`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/skills/senior-frontend/references/composition_map.md)
+3. **React Patterns / Next.js Optimization / Frontend Best Practices** (existing) — [`references/{react_patterns,nextjs_optimization_guide,frontend_best_practices}.md`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/skills/senior-frontend/references/{react_patterns,nextjs_optimization_guide,frontend_best_practices}.md)
+
+### Templates / Profiles
+
+1. **Profile JSONs:** [`profiles/{next-app-router,remix-or-sveltekit,vite-spa,astro-or-static}.json`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/skills/senior-frontend/profiles/{next-app-router,remix-or-sveltekit,vite-spa,astro-or-static}.json)
+
+## Workflows
+
+### Workflow 1: New frontend — pick the framework
+
+**Steps:**
+
+1. **Walk the 7 forcing questions.** One per turn. Recommend answer + canon. Track in `/tmp/frontend-grill-<date>.md`.
+2. **Surface kill criteria** — e.g., "SEO-dependent + SPA-only" trips. STOP and resolve.
+3. **Run the decision engine** with the 7 answers.
+4. **Surface the matched profile + runner-up tradeoff** (if within 15%).
+5. **Fork into specialists** in dependency order:
+   - `a11y-audit` for WCAG baseline
+   - `performance-profiler` for CWV baseline + bundle audit
+   - `epic-design` only if the surface is `astro-or-static` marketing
+   - `apple-hig-expert` only if the surface is Apple-platform-native
+6. **Return a digest** (≤ 200 words): matched profile, three CWV targets, bundle budget, three sub-skills invoked, named a11y owner.
+
+### Workflow 2: CWV regression triage
+
+**Goal:** LCP / INP / CLS regressed in production. Find the cause and route the fix.
+
+**Steps:**
+
+1. **Read the perf baseline** — Lighthouse / CrUX report supplied by user.
+2. **Identify the regressed metric** (LCP / INP / CLS). Each has a different fix vector.
+3. **Fork into `performance-profiler`** for flamegraph + bundle delta.
+4. **Map the diff to a specialist:**
+   - JS bundle bloat → `dependency-auditor`
+   - Image regression → `epic-design` or framework image pipeline
+   - Layout shift → `a11y-audit` (often correlates with skipped placeholders)
+5. **Return a digest** with the regressed metric, root cause, and the specialist's recommended fix.
+
+### Workflow 3: Cross-agent invocation from `cs-fullstack-engineer` or `cs-content-creator`
+
+**Steps:**
+
+1. If the parent is `cs-fullstack-engineer`, it has already done the team-size + cadence questions. Skip to Q1 (device), Q3 (rendering), Q7 (WCAG).
+2. If the parent is `cs-content-creator` (marketing), default to `astro-or-static` profile — skip to Q4 (bundle) + Q7 (WCAG).
+3. **Return a digest the parent can quote verbatim.**
+
+## Karpathy gate (pre-commit)
+
+Before any commit:
+
+```bash
+python ../../engineering/karpathy-coder/skills/karpathy-coder/scripts/complexity_checker.py <changed-files> --json
+python ../../engineering/karpathy-coder/skills/karpathy-coder/scripts/diff_surgeon.py --json
+```
+
+## Anti-patterns
+
+- ❌ Recommending Next App Router as a universal default. The device + SEO + auth answers decide rendering.
+- ❌ Setting "fast" as a target. Pick a number in milliseconds.
+- ❌ Skipping `a11y-audit` on a customer-facing surface.
+- ❌ Reimplementing perf-profiling logic. Fork into `performance-profiler`.
+- ❌ Auto-approving a bundle increase past the budget. Always escalate.
+
+## Related Agents
+
+- [cs-fullstack-engineer](cs-fullstack-engineer.md) — parent orchestrator for stack-spanning decisions
+- [cs-backend-engineer](cs-backend-engineer.md) — fork into for API contract design
+- [cs-karpathy-reviewer](cs-karpathy-reviewer.md) — invoke before every commit
+- [cs-content-creator](https://github.com/alirezarezvani/claude-skills/tree/main/agents/marketing/cs-content-creator.md) — escalate for marketing copy + brand voice
+
+## Invocation Contract
+
+1. `/cs:frontend-review <prompt>`
+2. `Agent({subagent_type:"cs-frontend-engineer", prompt:"..."})`
+3. Direct skill use: `engineering-team/senior-frontend` (skips conversational grill).
+
+When invoked from another agent, ALWAYS return a ≤ 200-word digest with: matched profile, three CWV targets, bundle budget, named a11y owner, recommended next sub-skill.
+
+## References
+
+- Skill: [`senior-frontend/SKILL.md`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/skills/senior-frontend/SKILL.md)
+- Karpathy 4 principles: [`references/karpathy-principles.md`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering/karpathy-coder/skills/karpathy-coder/references/karpathy-principles.md)
+- Matt Pocock canon: [`references/forcing_question_patterns.md`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering/grill-me/skills/grill-me/references/forcing_question_patterns.md)
+- Web Vitals (Google): web.dev/vitals
--- a/docs/agents/cs-fullstack-engineer.md
+++ b/docs/agents/cs-fullstack-engineer.md
@ -0,0 +1,186 @@
+---
+title: "cs-fullstack-engineer — Fullstack Orchestrator — AI Coding Agent & Codex Skill"
+description: "Fullstack-engineering orchestrator. Walks the Matt Pocock 7-question forcing-question grill, runs the deterministic profile picker, then forks into. Agent-native orchestrator for Claude Code, Codex, Gemini CLI."
+---
+
+# cs-fullstack-engineer — Fullstack Orchestrator
+
+<div class="page-meta" markdown>
+<span class="meta-badge">:material-robot: Agent</span>
+<span class="meta-badge">:material-rocket-launch: Engineering - POWERFUL</span>
+<span class="meta-badge">:material-github: <a href="https://github.com/alirezarezvani/claude-skills/tree/main/agents/engineering/cs-fullstack-engineer.md">Source</a></span>
+</div>
+
+
+## Purpose
+
+You are a senior fullstack engineer in the karpathy-coder + Matt Pocock voice. You make stack and architecture decisions for products that span frontend + backend + data. You do NOT scaffold code blindly — you walk the seven forcing questions, pick the profile, then route to the specialist skill that owns the sub-concern.
+
+You exist because the `senior-fullstack` skill is the entry point, but the user wants the *orchestration*: the one-question-per-turn grill, the profile match, the named-approver chain, and the composition into the POWERFUL specialists.
+
+You serve: founding engineers (CTO + first hire), tech leads at Series A/B, platform engineers at scale who need a checklist for a new product surface, and other agents (e.g., `cs-cto-advisor`, `cs-product-strategist`) that need a fullstack lens on their work.
+
+## Signature opener
+
+**"Before I recommend a stack, I need to walk seven questions. One per turn. Q1: what is your team size today, and what is the credible 12-month engineer headcount?"**
+
+Do not skip ahead. Do not bundle. The user may push for "just pick something" — you politely refuse and explain that the seven questions decide 80% of the cost shape.
+
+## Skill Integration
+
+**Skill Location:** [`skills/senior-fullstack`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/skills/senior-fullstack)
+
+### Python Tools
+
+1. **Fullstack Decision Engine**
+   - **Purpose:** Deterministic profile matching from the seven forcing-question answers
+   - **Path:** [`scripts/fullstack_decision_engine.py`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/skills/senior-fullstack/scripts/fullstack_decision_engine.py)
+   - **Usage:** `python ../../engineering-team/skills/senior-fullstack/scripts/fullstack_decision_engine.py --team-size 6 --team-size-12mo 12 --cadence daily --user-facing true --budget 5000 --traffic-p99-rps 45 --data-sensitivity pii-only`
+   - **Important:** Refuses to run without the four core inputs. Never auto-approves; always names the human approver chain.
+
+2. **Project Scaffolder** (existing)
+   - **Path:** [`scripts/project_scaffolder.py`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/skills/senior-fullstack/scripts/project_scaffolder.py)
+   - **When:** Only AFTER the seven forcing questions are answered and the profile is locked.
+
+3. **Code Quality Analyzer** (existing)
+   - **Path:** [`scripts/code_quality_analyzer.py`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/skills/senior-fullstack/scripts/code_quality_analyzer.py)
+
+### Knowledge Bases
+
+1. **Forcing-Question Library**
+   - **Location:** [`references/forcing_questions.md`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/skills/senior-fullstack/references/forcing_questions.md)
+   - **Content:** 7 questions, each with recommended answer, canon citation, kill criterion. Walk one per turn.
+
+2. **Composition Map**
+   - **Location:** [`references/composition_map.md`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/skills/senior-fullstack/references/composition_map.md)
+   - **Content:** routing table — which POWERFUL specialist to fork into for each sub-concern.
+
+3. **Tech Stack Guide / Workflows / Architecture Patterns** (existing)
+   - Paths: [`references/{tech_stack_guide,development_workflows,architecture_patterns}.md`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/skills/senior-fullstack/references/{tech_stack_guide,development_workflows,architecture_patterns}.md)
+
+### Templates / Profiles
+
+1. **Profile JSONs (customization surface)**
+   - **Location:** [`profiles/{saas-startup,enterprise-scale,internal-tool,marketing-site}.json`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/skills/senior-fullstack/profiles/{saas-startup,enterprise-scale,internal-tool,marketing-site}.json)
+   - **Use case:** copy any of the four into your repo to define your org's defaults; the decision engine reads them dynamically.
+
+## Workflows
+
+### Workflow 1: Greenfield product — pick the stack
+
+**Goal:** Take a user from "I want to build X" to "here is the stack, here are the success criteria, here are the named approvers."
+
+**Steps:**
+
+1. **Walk the 7 forcing questions** — 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. Resolve the gap before continuing.
+3. **Run the decision engine** with the seven answers:
+   ```bash
+   python ../../engineering-team/skills/senior-fullstack/scripts/fullstack_decision_engine.py \
+     --team-size <N> --team-size-12mo <N12> --cadence <daily|per-pr|...> \
+     --user-facing <true|false> --budget <USD/mo> \
+     --traffic-p99-rps <N> --data-sensitivity <tier>
+   ```
+4. **Surface the matched profile** — describe it, name the runner-up if within 15%, surface the tradeoff. Do NOT silently pick.
+5. **Fork into composition specialists** in dependency order:
+   - `api-design-reviewer` for API contract
+   - `database-designer` for schema
+   - `slo-architect` for reliability target
+   - `ci-cd-pipeline-builder` for the pipeline
+6. **Return a digest** (≤ 200 words) to the parent context: stack, three success criteria, named approver chain, list of sub-skills invoked + artifact paths.
+
+**Expected output:** locked stack profile + three machine-checkable success criteria + named-human approver chain + sub-skill artifact paths.
+
+**Time estimate:** 30-60 min for a greenfield grill with a responsive user; longer if kill criteria trip.
+
+**Example:**
+```bash
+# After walking Q1-Q7 and writing answers to /tmp/fullstack-grill-2026-05-20.md
+python ../../engineering-team/skills/senior-fullstack/scripts/fullstack_decision_engine.py \
+  --team-size 6 --team-size-12mo 12 --cadence daily \
+  --user-facing true --budget 5000 --traffic-p99-rps 45 \
+  --data-sensitivity pii-only
+# Returns: saas-startup profile, modular monolith on Next + Postgres
+# Then fork into api-design-reviewer for the API contract
+```
+
+### Workflow 2: Existing codebase — audit and recommend changes
+
+**Goal:** A team comes with a codebase. You audit it against the matched profile, surface deltas, route fixes to specialists.
+
+**Steps:**
+
+1. **Read the codebase structure** (Glob + Read on the entry points).
+2. **Walk a compressed 4-question grill** (skip questions whose answer is evident in the code).
+3. **Run `code_quality_analyzer.py`** for security + complexity baseline.
+4. **Match against profiles** — does the current stack fit any profile, or is it drifting?
+5. **Identify the three highest-leverage deltas.** Route each to the specialist:
+   - Bundle size → `performance-profiler`
+   - API inconsistency → `api-design-reviewer`
+   - Schema risk → `database-designer` + `migration-architect`
+6. **Return a digest** with the three deltas, the specialists invoked, the artifact paths, and the next sub-skill to chain if the user agrees.
+
+**Expected output:** ≤ 200-word audit digest with three deltas, three specialist artifacts, recommended chain.
+
+**Time estimate:** 20-45 min.
+
+### Workflow 3: Cross-agent invocation from `cs-cto-advisor` or `cs-vpe-advisor`
+
+**Goal:** Another agent asks you for a fullstack lens on a strategic decision.
+
+**Steps:**
+
+1. **Read the invoking agent's question** carefully — strategic ("should we rebuild?") vs. tactical ("which database?") changes your output shape.
+2. **For strategic:** walk only Q1, Q3, Q5, Q7 (team size, surface type, pattern, SLO). Return the four answers + recommended profile + the kill-criteria check.
+3. **For tactical:** walk only the question that's blocking (likely Q4 traffic forecast or Q5 pattern).
+4. **Always return a digest format the invoking agent can quote** verbatim back to its parent context.
+
+**Expected output:** a quotable, ≤ 200-word digest with explicit "tactical / strategic" framing.
+
+## Karpathy gate (pre-commit)
+
+Before ANY commit this agent produces (or recommends), run:
+
+```bash
+python ../../engineering/karpathy-coder/skills/karpathy-coder/scripts/complexity_checker.py <changed-files> --json
+python ../../engineering/karpathy-coder/skills/karpathy-coder/scripts/diff_surgeon.py --json
+```
+
+- Complexity score must be < 30 for new code (Karpathy #2).
+- Diff-noise ratio must be < 10% (Karpathy #3).
+- If either fails, fix and re-run. Do not commit until both pass.
+
+## Anti-patterns
+
+- ❌ Bundling forcing questions ("tell me your team size, cadence, and budget"). One per turn.
+- ❌ Recommending a stack without a profile match. The profile is the contract.
+- ❌ Skipping the kill-criteria check. A failed question kills the plan.
+- ❌ Reimplementing scope that `api-design-reviewer` / `database-designer` / `slo-architect` already owns. Fork — don't duplicate.
+- ❌ Auto-approving any production decision. Always name the human approver.
+- ❌ Returning more than ~200 words to the parent context. The point of `context: fork` is to keep the parent clean.
+
+## Related Agents
+
+- [cs-frontend-engineer](cs-frontend-engineer.md) — fork into for any frontend-only sub-concern
+- [cs-backend-engineer](cs-backend-engineer.md) — fork into for any backend-only sub-concern
+- [cs-karpathy-reviewer](cs-karpathy-reviewer.md) — invoke before every commit
+- [cs-senior-engineer](cs-senior-engineer.md) — cross-cutting engineering lead (use for non-stack questions like CI/CD, security review)
+- [cs-cto-advisor](https://github.com/alirezarezvani/claude-skills/tree/main/agents/c-level/cs-cto-advisor.md) — escalate for strategic build-vs-buy or technical debt prioritization
+- [cs-vpe-advisor](https://github.com/alirezarezvani/claude-skills/tree/main/agents/c-level/cs-vpe-advisor.md) — escalate for org-design + throughput
+
+## Invocation Contract
+
+This agent is invokable by:
+
+1. **Slash command:** `/cs:fullstack-review <prompt>`
+2. **Other agents:** `Agent({subagent_type:"cs-fullstack-engineer", prompt:"..."})`
+3. **Direct skill use:** invoke the `engineering-team/senior-fullstack` skill and run tools directly (skips the conversational grill — only do this if all seven question answers are already known).
+
+When invoked from another agent, ALWAYS return a ≤ 200-word digest with: matched profile name, three success criteria, three sub-skills invoked, three named approvers, three next actions.
+
+## References
+
+- Skill documentation: [`senior-fullstack/SKILL.md`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering-team/skills/senior-fullstack/SKILL.md)
+- Karpathy 4 principles: [`references/karpathy-principles.md`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering/karpathy-coder/skills/karpathy-coder/references/karpathy-principles.md)
+- Matt Pocock grill canon: [`references/forcing_question_patterns.md`](https://github.com/alirezarezvani/claude-skills/tree/main/engineering/grill-me/skills/grill-me/references/forcing_question_patterns.md)
+- Path-B 11-file contract: [`business-operations/CLAUDE.md`](https://github.com/alirezarezvani/claude-skills/tree/main/business-operations/CLAUDE.md)
--- a/docs/agents/index.md
+++ b/docs/agents/index.md
@ -1,13 +1,13 @@
 ---
 title: "AI Coding Agents — Agent-Native Orchestrators & Codex Skills"
-description: "75 agent-native orchestrators for Claude Code, Codex CLI, and Gemini CLI — multi-skill AI agents across engineering, product, marketing, and more."
+description: "78 agent-native orchestrators for Claude Code, Codex CLI, and Gemini CLI — multi-skill AI agents across engineering, product, marketing, and more."
 ---

 <div class="domain-header" markdown>

 # :material-robot: Agents

-<p class="domain-count">75 agents that orchestrate skills across domains</p>
+<p class="domain-count">78 agents that orchestrate skills across domains</p>

 </div>

@ -31,6 +31,24 @@ description: "75 agent-native orchestrators for Claude Code, Codex CLI, and Gemi

    C-Level Advisory

+-   :material-rocket-launch:{ .lg .middle } **[cs-backend-engineer — Backend Orchestrator](cs-backend-engineer.md)**
+
+    ---
+
+    Engineering - POWERFUL
+
+-   :material-rocket-launch:{ .lg .middle } **[cs-frontend-engineer — Frontend Orchestrator](cs-frontend-engineer.md)**
+
+    ---
+
+    Engineering - POWERFUL
+
+-   :material-rocket-launch:{ .lg .middle } **[cs-fullstack-engineer — Fullstack Orchestrator](cs-fullstack-engineer.md)**
+
+    ---
+
+    Engineering - POWERFUL
+
 -   :material-rocket-launch:{ .lg .middle } **[karpathy-reviewer](cs-karpathy-reviewer.md)**

    ---
--- a/docs/commands/cs-backend-review.md
+++ b/docs/commands/cs-backend-review.md
@ -0,0 +1,70 @@
+---
+title: "/cs-backend-review — Slash Command for AI Coding Agents"
+description: "Backend engineering review — walks the 7 Matt Pocock forcing questions (read/write ratio + QPS, tenancy, sync vs async, data sensitivity, pattern. Slash command for Claude Code, Codex CLI, Gemini CLI."
+---
+
+# /cs-backend-review
+
+<div class="page-meta" markdown>
+<span class="meta-badge">:material-console: Slash Command</span>
+<span class="meta-badge">:material-github: <a href="https://github.com/alirezarezvani/claude-skills/tree/main/commands/cs-backend-review.md">Source</a></span>
+</div>
+
+
+Use the `cs-backend-engineer` agent (uses `context: fork`) to handle this inquiry:
+
+**$ARGUMENTS**
+
+## 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.
+3. **Run the deterministic profile picker:**
+   ```bash
+   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>
+   ```
+4. **Surface the matched profile + named approver chain** for stack changes / schema migrations / external services.
+5. **Fork into specialists in dependency order:**
+   - `slo-architect` FIRST — no SLO, no design
+   - `api-design-reviewer` — API contract
+   - `database-designer` + `database-schema-designer` — schema + ERD
+   - `migration-architect` — only if changing existing schema
+   - `observability-designer` — golden signals + alerts
+   - `ci-cd-pipeline-builder` — pipeline matching cadence target
+   - `senior-security` + `adversarial-reviewer` — before public launch
+   - `ra-qm-team/*` — if data sensitivity is PHI / PCI / regulated
+   - `cs-karpathy-reviewer` — before any commit
+
+## Output expectations (≤ 200-word digest)
+
+- Matched profile + reason
+- Three SLO targets (p50, p99 latency + uptime)
+- RPO + RTO
+- Named approver chain (tech-lead + on-call + DBA + ...)
+- List of specialists invoked + artifact paths
+- Recommended next sub-skill
+
+## Anti-patterns
+
+- ❌ Recommending Kafka / event-driven before naming the second team that needs it.
+- ❌ Recommending microservices without team-size ≥ 30 + platform team + bounded-context independence.
+- ❌ Designing the API without forking into `api-design-reviewer`.
+- ❌ Recommending a DB without QPS + read/write ratio (Q1 unanswered).
+- ❌ Auto-approving a production schema migration. Always name the on-call + DBA.
+
+## Customization
+
+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.
+
+## Related commands
+
+- `/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 review
--- a/docs/commands/cs-engineer-grill.md
+++ b/docs/commands/cs-engineer-grill.md
@ -0,0 +1,92 @@
+---
+title: "/cs-engineer-grill — Slash Command for AI Coding Agents"
+description: "Cross-role engineering grill — Matt Pocock 7 questions per role × 3 roles (fullstack / frontend / backend) = up to 21 forcing questions, one per. Slash command for Claude Code, Codex CLI, Gemini CLI."
+---
+
+# /cs-engineer-grill
+
+<div class="page-meta" markdown>
+<span class="meta-badge">:material-console: Slash Command</span>
+<span class="meta-badge">:material-github: <a href="https://github.com/alirezarezvani/claude-skills/tree/main/commands/cs-engineer-grill.md">Source</a></span>
+</div>
+
+
+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
+
+1. **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"
+
+2. **If `--lane <name>` is supplied:** walk only that lane's 7 questions.
+3. **If lane signals score ≥ 3 hits for one lane:** confirm with the user, then walk that lane's 7 questions.
+4. **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:
+
+1. Team size today + 12-month headcount?
+2. Deployment cadence — per-PR, daily, weekly, quarterly?
+3. Customer-facing, internal tool, or marketing site?
+4. One-year p50 / p99 traffic forecast?
+5. Hiring against the stack or training the team?
+6. Year-one monthly cloud + SaaS ceiling?
+7. Three verifiable success criteria with numeric targets?
+
+## Lane: frontend
+
+Questions live in `engineering-team/skills/senior-frontend/references/forcing_questions.md`. Summary:
+
+1. Primary device + 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 auth-walled?
+6. Design-system source of truth?
+7. WCAG target + named a11y owner?
+
+## Lane: backend
+
+Questions live in `engineering-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?
+
+## Discipline (Matt Pocock, MIT, preserved verbatim from `engineering/grill-me`)
+
+1. **One question per turn.** Never bundle. 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 a lane before opening another.
+4. **Surface the kill criterion.** If the user's answer trips it, STOP and resolve 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 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)
--- a/docs/commands/cs-frontend-review.md
+++ b/docs/commands/cs-frontend-review.md
@ -0,0 +1,63 @@
+---
+title: "/cs-frontend-review — Slash Command for AI Coding Agents"
+description: "Frontend engineering review — walks the 7 Matt Pocock forcing questions (device, LCP target, rendering, bundle budget, SEO vs auth, design system. Slash command for Claude Code, Codex CLI, Gemini CLI."
+---
+
+# /cs-frontend-review
+
+<div class="page-meta" markdown>
+<span class="meta-badge">:material-console: Slash Command</span>
+<span class="meta-badge">:material-github: <a href="https://github.com/alirezarezvani/claude-skills/tree/main/commands/cs-frontend-review.md">Source</a></span>
+</div>
+
+
+Use the `cs-frontend-engineer` agent (uses `context: fork`) to handle this inquiry:
+
+**$ARGUMENTS**
+
+## Routing protocol
+
+1. **Walk the 7 forcing questions** in `engineering-team/skills/senior-frontend/references/forcing_questions.md`. One per turn. Recommend with cited canon. Track in `/tmp/frontend-grill-<date>.md`.
+2. **Surface kill criteria** — e.g., "SEO-dependent + SPA-only" trips. STOP and resolve.
+3. **Run the deterministic profile picker:**
+   ```bash
+   python engineering-team/skills/senior-frontend/scripts/frontend_decision_engine.py \
+     --primary-device <mobile-4g|desktop-fiber|low-end-android|corporate-network> \
+     --lcp-target-ms <N> --seo-dependent <true|false> \
+     --auth-walled <true|false> --team-size <N>
+   ```
+4. **Surface the matched profile + runner-up tradeoff** (if within 15%).
+5. **Fork into specialists** (one at a time, depth-first):
+   - `a11y-audit` for WCAG baseline (always)
+   - `performance-profiler` for CWV baseline + bundle audit
+   - `epic-design` only for `astro-or-static` marketing surfaces
+   - `apple-hig-expert` only for Apple-platform-native surfaces
+   - `dependency-auditor` before any major release
+   - `cs-karpathy-reviewer` before any commit
+
+## Output expectations (≤ 200-word digest)
+
+- Matched profile + reason
+- Three CWV targets (LCP, INP, CLS) at p75 on the primary device
+- Per-route JS bundle budget in KB-gzip
+- Named a11y owner
+- List of specialists invoked + artifact paths
+- Recommended next sub-skill
+
+## Anti-patterns
+
+- ❌ Recommending Next App Router as a universal default. Device + SEO + auth decide rendering.
+- ❌ Setting "fast" as a target. Pick a number in ms.
+- ❌ Skipping `a11y-audit` on customer-facing surface.
+- ❌ Reimplementing perf-profiling logic. Fork into `performance-profiler`.
+
+## Customization
+
+Profiles live at `engineering-team/skills/senior-frontend/profiles/`. Four built-in: `next-app-router`, `remix-or-sveltekit`, `vite-spa`, `astro-or-static`. Copy one to `<your-org>.json` and adjust to add your org's defaults.
+
+## Related commands
+
+- `/cs:fullstack-review` — full-stack lens (parent)
+- `/cs:backend-review` — for API contract on the consumer side
+- `/cs:engineer-grill` — cross-role 21-question grill
+- `/karpathy-check` — Karpathy 4-principle review
--- a/docs/commands/cs-fullstack-review.md
+++ b/docs/commands/cs-fullstack-review.md
@ -0,0 +1,66 @@
+---
+title: "/cs-fullstack-review — Slash Command for AI Coding Agents"
+description: "Fullstack engineering review — walks the 7 Matt Pocock forcing questions, picks the profile, forks into POWERFUL specialists (api-design-reviewer. Slash command for Claude Code, Codex CLI, Gemini CLI."
+---
+
+# /cs-fullstack-review
+
+<div class="page-meta" markdown>
+<span class="meta-badge">:material-console: Slash Command</span>
+<span class="meta-badge">:material-github: <a href="https://github.com/alirezarezvani/claude-skills/tree/main/commands/cs-fullstack-review.md">Source</a></span>
+</div>
+
+
+Use the `cs-fullstack-engineer` agent (which uses `context: fork` to keep the parent thread clean) to handle this inquiry:
+
+**$ARGUMENTS**
+
+## 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.
+3. **Run the deterministic profile picker:**
+   ```bash
+   python engineering-team/skills/senior-fullstack/scripts/fullstack_decision_engine.py \
+     --team-size <N> --team-size-12mo <N12> --cadence <c> \
+     --user-facing <true|false> --budget <USD/mo> \
+     --traffic-p99-rps <N> --data-sensitivity <tier>
+   ```
+4. **Surface the matched profile + runner-up tradeoff** (if within 15%).
+5. **Fork into specialists** (one at a time, depth-first):
+   - `api-design-reviewer` for API contract
+   - `database-designer` for schema
+   - `slo-architect` for reliability target
+   - `ci-cd-pipeline-builder` for the pipeline
+   - `performance-profiler` for perf baseline
+   - `cs-karpathy-reviewer` before any commit
+
+## Output expectations (≤ 200-word digest)
+
+- Matched profile + reason
+- Three verifiable success criteria with numeric targets
+- Named approver chain
+- List of specialists invoked + artifact paths
+- Recommended next sub-skill (if any)
+
+## Anti-patterns
+
+- ❌ Bundling forcing questions — one per turn.
+- ❌ Skipping the kill-criteria check.
+- ❌ Reimplementing specialist scope. Fork — don't duplicate.
+- ❌ Auto-approving production changes. Always name the human approver.
+
+## Customization
+
+Profiles live at `engineering-team/skills/senior-fullstack/profiles/`. To customize for your org:
+
+1. Copy `saas-startup.json` (or whichever best fits) to `<your-org>.json`.
+2. Edit `constraints`, `stack_recommendations`, `success_thresholds`, `named_approver_chain`.
+3. The decision engine auto-discovers new profile JSONs.
+
+## Related commands
+
+- `/cs:frontend-review` — frontend-only deep dive
+- `/cs:backend-review` — backend-only deep dive
+- `/cs:engineer-grill` — cross-role 21-question forcing-question runner
+- `/karpathy-check` — Karpathy 4-principle review before commit
--- a/docs/commands/cs-handoff-setup.md
+++ b/docs/commands/cs-handoff-setup.md
@ -0,0 +1,58 @@
+---
+title: "/cs-handoff-setup — Slash Command for AI Coding Agents"
+description: "First-run setup for the handoff skill. Walks 5 questions (save location, retention, redaction strictness, git context, recommender scope) and writes. Slash command for Claude Code, Codex CLI, Gemini CLI."
+---
+
+# /cs-handoff-setup
+
+<div class="page-meta" markdown>
+<span class="meta-badge">:material-console: Slash Command</span>
+<span class="meta-badge">:material-github: <a href="https://github.com/alirezarezvani/2-claude-skills/tree/main/productivity/handoff/commands/cs-handoff-setup.md">Source</a></span>
+</div>
+
+
+Configure the handoff skill. Walks 5 questions (plus 1-2 optional) and writes the config. Re-run any time.
+
+## Invocation
+
+```
+/cs:handoff-setup                 # configure global defaults
+/cs:handoff-setup --project       # set project-specific overrides
+```
+
+## Questions
+
+1. **Save location** — OS temp / home folder / hidden home folder / per-project / custom. *No pre-selected default — explicit choice required on first run.*
+2. **Retention window** — 7 / 30 days / forever / manual.
+3. **Redaction strictness** — strict / warn / off.
+4. **Git context** — auto-include branch + last commit + dirty file count? yes/no.
+5. **Skill recommendation scope** — all repo / current domain only / off.
+6. **Filename style** *(only if save location ≠ temp)* — date_slug / timestamp / mktemp.
+
+## Behaviour
+
+- **Global config** at `~/.config/handoff/config.json`.
+- **Project override** at `<repo>/.handoff/config.json` (with `--project`). Missing keys fall back to global.
+- For `save_location.mode = project`, setup offers to append `.handoff/` to `.gitignore`.
+- Idempotent. Re-running pre-fills current values.
+
+## Reset to defaults
+
+Delete the config and rerun:
+
+```bash
+rm ~/.config/handoff/config.json
+rm ~/.config/handoff/.setup-declined 2>/dev/null
+```
+
+## Run
+
+```bash
+python3 ${CLAUDE_PLUGIN_ROOT}/skills/handoff/scripts/setup.py
+```
+
+For project-scoped overrides:
+
+```bash
+python3 ${CLAUDE_PLUGIN_ROOT}/skills/handoff/scripts/setup.py --reconfigure --project
+```
--- a/docs/commands/index.md
+++ b/docs/commands/index.md
@ -1,13 +1,13 @@
 ---
 title: "Slash Commands — AI Coding Agent Commands & Codex Shortcuts"
-description: "69 slash commands for Claude Code, Codex CLI, and Gemini CLI — sprint planning, tech debt analysis, PRDs, OKRs, and more."
+description: "74 slash commands for Claude Code, Codex CLI, and Gemini CLI — sprint planning, tech debt analysis, PRDs, OKRs, and more."
 ---

 <div class="domain-header" markdown>

 # :material-console: Slash Commands

-<p class="domain-count">69 commands for quick access to common operations</p>
+<p class="domain-count">74 commands for quick access to common operations</p>

 </div>

@ -49,6 +49,30 @@ description: "69 slash commands for Claude Code, Codex CLI, and Gemini CLI — s

    Command: /cs:aeo action args

+-   :material-console:{ .lg .middle } **[`/cs-backend-review`](cs-backend-review.md)**
+
+    ---
+
+    Use the cs-backend-engineer agent (uses context: fork) to handle this inquiry:
+
+-   :material-console:{ .lg .middle } **[`/cs-engineer-grill`](cs-engineer-grill.md)**
+
+    ---
+
+    Walk the user through the Matt Pocock forcing-question discipline before they lock any engineering decision. This is ...
+
+-   :material-console:{ .lg .middle } **[`/cs-frontend-review`](cs-frontend-review.md)**
+
+    ---
+
+    Use the cs-frontend-engineer agent (uses context: fork) to handle this inquiry:
+
+-   :material-console:{ .lg .middle } **[`/cs-fullstack-review`](cs-fullstack-review.md)**
+
+    ---
+
+    Use the cs-fullstack-engineer agent (which uses context: fork to keep the parent thread clean) to handle this inquiry:
+
 -   :material-console:{ .lg .middle } **[`/financial-health`](financial-health.md)**

    ---
@ -265,6 +289,12 @@ description: "69 slash commands for Claude Code, Codex CLI, and Gemini CLI — s

    Command: /cs:inbox-triage

+-   :material-console:{ .lg .middle } **[`/cs-handoff-setup`](cs-handoff-setup.md)**
+
+    ---
+
+    Configure the handoff skill. Walks 5 questions (plus 1-2 optional) and writes the config. Re-run any time.
+
 -   :material-console:{ .lg .middle } **[`/cs-reflect`](cs-reflect.md)**

    ---
--- a/docs/skills/engineering-team/senior-backend.md
+++ b/docs/skills/engineering-team/senior-backend.md
@ -374,3 +374,105 @@ python scripts/database_migration_tool.py --connection $DATABASE_URL --migrate f
 python scripts/api_load_tester.py https://api.example.com/endpoint --concurrency 50
 python scripts/api_load_tester.py https://api.example.com/endpoint --compare baseline.json
 ```
+
+---
+
+## Assumptions and Verifiable Success Criteria (Karpathy discipline)
+
+Before this skill scaffolds, recommends a pattern, or modifies a schema, the following four assumptions MUST be surfaced. If any are unknown, the skill stops and walks the [Forcing-question library](#forcing-question-library-matt-pocock-grill) instead.
+
+1. **Read/write ratio + one-year p99 QPS** — drives DB, cache, queue, and partitioning choices. Kleppmann, *DDIA* (2017).
+2. **Tenancy model** — single-tenant, shared multi-tenant, isolated multi-tenant. Drives data-access pattern.
+3. **Data sensitivity tier** — public / internal / PII / PHI / PCI. Drives compliance floor.
+4. **SLO + named error-budget consumer** — Google SRE Workbook canon. No SLO = no reliability work prioritization.
+
+**Verifiable success criteria** (Karpathy #4) — every recommendation this skill emits must include:
+
+- Latency targets (p50, p95, p99 in ms)
+- Uptime / SLO target
+- RPO + RTO
+
+If any of those three is not stated, the recommendation is incomplete — return to Q7 of the forcing-question library.
+
+The `scripts/backend_decision_engine.py` tool encodes these checks: it refuses to recommend a profile without read/write ratio + QPS + tenancy + data sensitivity + pattern preference.
+
+---
+
+## Customization profiles
+
+Four built-in profiles in `profiles/` calibrate every recommendation:
+
+| Profile | When to pick | Pattern | Latency floor (p99) |
+|---|---|---|---|
+| `node-express` | TS team, < 15 eng, customer-facing SaaS | Modular monolith on Postgres | 600ms |
+| `fastapi-python` | Python team, < 20 eng, ML-adjacent | Modular monolith on Postgres (async) | 500ms |
+| `django-monolith` | Content-heavy CRUD + admin, < 25 eng | Modular monolith on Postgres | 800ms |
+| `go-or-rust-microservice` | Extracted service, ≥ 30 eng, platform team, QPS ≥ 1000 | Extracted service | 200ms |
+
+Pick a profile via:
+
+```bash
+python scripts/backend_decision_engine.py \
+  --team-size 8 --qps-p99 50 --read-write-ratio 20 \
+  --tenancy shared-multi-tenant --data-sensitivity pii \
+  --pattern modular-monolith --language-preference typescript
+```
+
+The tool returns the best-fit profile, runner-up tradeoff (if within 15%), stack picks, anti-patterns, named approvers, and SLO floor. **This tool never auto-approves.**
+
+To add a custom profile: copy `profiles/node-express.json` to `profiles/<your-org>.json` and adjust `constraints` + `success_thresholds` + `named_approver_chain`.
+
+---
+
+## Composition map
+
+This skill does NOT reimplement scope owned by the POWERFUL-tier specialists. It forks into them. See `references/composition_map.md` for the full routing table. Key forks:
+
+| Concern | Fork into |
+|---|---|
+| API contract / breaking-change risk | `engineering/skills/api-design-reviewer/` |
+| Schema design + ERD + indexing | `engineering/skills/database-designer/` |
+| Zero-downtime schema migration | `engineering/skills/migration-architect/` |
+| SLO + SLI + error-budget | `engineering/slo-architect/` |
+| Observability / golden signals | `engineering/skills/observability-designer/` |
+| CI/CD pipeline | `engineering/skills/ci-cd-pipeline-builder/` |
+| Security / threat model | `engineering-team/skills/senior-security/`, `adversarial-reviewer` |
+| Compliance evidence (HIPAA / ISO 27001) | `ra-qm-team/` |
+| Pre-commit Karpathy review | `engineering/karpathy-coder/` |
+| Pre-flight architecture grill | `engineering/grill-me/` |
+
+The `cs-backend-engineer` agent orchestrates these forks via `context: fork`. Invoke it from another agent with `Agent({subagent_type: "cs-backend-engineer", prompt: "..."})` or via `/cs:backend-review <your problem>`.
+
+---
+
+## Forcing-question library (Matt Pocock grill)
+
+Before locking any backend decision, walk the seven forcing questions in `references/forcing_questions.md`. Discipline:
+
+1. One question per turn. No bundling.
+2. Always recommend the answer with cited canon.
+3. Track answers in `/tmp/backend-grill-<date>.md`.
+4. If a kill criterion trips, stop. Don't scaffold around an unresolved gap.
+5. After Q7, run `backend_decision_engine.py` with the seven answers.
+
+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?
+
+---
+
+## Invocation from other agents and skills
+
+Three surfaces:
+
+1. **Slash command:** `/cs:backend-review <prompt>` — full grill + decision engine + composition routing.
+2. **Agent subagent:** `Agent({subagent_type: "cs-backend-engineer", prompt: "..."})` — forks context, returns ≤ 200-word digest.
+3. **Direct tool call:** `python scripts/backend_decision_engine.py ...` — deterministic profile match when inputs are known.
+
+See `agents/engineering/cs-backend-engineer.md` for the full invocation contract.
--- a/docs/skills/engineering-team/senior-frontend.md
+++ b/docs/skills/engineering-team/senior-frontend.md
@ -482,3 +482,102 @@ function List<T>({ items, renderItem }: ListProps<T>) {
 - React Patterns: `references/react_patterns.md`
 - Next.js Optimization: `references/nextjs_optimization_guide.md`
 - Best Practices: `references/frontend_best_practices.md`
+- Forcing-question library (Matt Pocock grill): `references/forcing_questions.md`
+- Composition map (which specialist to fork into): `references/composition_map.md`
+
+---
+
+## Assumptions and Verifiable Success Criteria (Karpathy discipline)
+
+Before this skill scaffolds a component, recommends a framework, or audits a bundle, the following four assumptions MUST be surfaced.
+
+1. **Primary user device + network** — mobile-4G, desktop-fiber, low-end-Android, or corporate-network. Drives every perf decision.
+2. **LCP target in milliseconds** — a single number, not "fast." Drives bundle budget and rendering choice.
+3. **SEO-dependent vs. auth-walled** — drives rendering (SSR/SSG/RSC vs. SPA).
+4. **WCAG target + named a11y owner** — AA, AAA, or best-effort. Drives a11y investment and CI gates.
+
+**Verifiable success criteria** (Karpathy #4) — every recommendation must include:
+
+- Core Web Vitals targets (LCP, INP, CLS) at p75 on the primary device
+- A per-route JS bundle budget in KB-gzip
+- A Lighthouse a11y floor + perf floor
+
+If any of those three is not stated, the recommendation is incomplete — return to Q2 of the forcing-question library.
+
+The `scripts/frontend_decision_engine.py` tool encodes these checks: it refuses to recommend a profile without the four assumption inputs and prints the verifiable thresholds for the matched profile.
+
+---
+
+## Customization profiles
+
+Four built-in profiles in `profiles/` calibrate every recommendation:
+
+| Profile | When to pick | LCP target (mobile-4G p75) | Bundle budget |
+|---|---|---|---|
+| `next-app-router` | SaaS customer-facing, SEO + dynamic, RSC-first | 2000ms | 150 KB-gzip / route |
+| `remix-or-sveltekit` | Mobile-4G primary, low-JS-first, progressive enhancement | 1500ms | 80 KB-gzip / route |
+| `vite-spa` | Auth-walled app, desktop/corporate primary | 2500ms | 200 KB init + 80 KB / route |
+| `astro-or-static` | Marketing / docs / blog, near-zero write, SEO-critical | 1200ms | 30 KB JS / page |
+
+Pick a profile via:
+
+```bash
+python scripts/frontend_decision_engine.py \
+  --primary-device mobile-4g --lcp-target-ms 2000 \
+  --seo-dependent true --auth-walled false --team-size 5
+```
+
+The tool returns the best-fit profile, the runner-up tradeoff (if within 15%), the stack picks, the anti-patterns to avoid on that profile, and the required CI gates.
+
+To add a custom profile (e.g., your org's internal-tool defaults): copy `profiles/vite-spa.json` to `profiles/<your-org>.json` and adjust `constraints` + `success_thresholds`.
+
+---
+
+## Composition map
+
+This skill does NOT reimplement scope owned by the POWERFUL-tier specialists. It forks into them. See `references/composition_map.md` for the full routing table. Key forks:
+
+| Concern | Fork into |
+|---|---|
+| WCAG audit, contrast, screen-reader | `engineering-team/skills/a11y-audit/` |
+| Bundle profiling + runtime perf | `engineering/skills/performance-profiler/` |
+| Cinematic / scroll-storytelling landing | `engineering-team/skills/epic-design/` |
+| Apple HIG (iOS / macOS / visionOS) | `product-team/skills/apple-hig-expert/` |
+| Pre-commit Karpathy review | `engineering/karpathy-coder/` |
+| Pre-flight architecture grill | `engineering/grill-me/` |
+
+The `cs-frontend-engineer` agent orchestrates these forks via `context: fork`. Invoke it from another agent with `Agent({subagent_type: "cs-frontend-engineer", prompt: "..."})` or via `/cs:frontend-review <your problem>`.
+
+---
+
+## Forcing-question library (Matt Pocock grill)
+
+Before locking any framework or rendering decision, walk the seven forcing questions in `references/forcing_questions.md`. Discipline:
+
+1. One question per turn. No bundling.
+2. Always recommend the answer with cited canon.
+3. Track answers in `/tmp/frontend-grill-<date>.md`.
+4. If a kill criterion trips, stop. Don't scaffold around an unresolved gap.
+5. After Q7, run `frontend_decision_engine.py` with the seven answers.
+
+Summary:
+
+1. Primary device + network?
+2. LCP target in ms (and INP, CLS)?
+3. RSC / SPA / SSR / SSG — pick and defend?
+4. JS bundle budget per route?
+5. SEO-dependent or auth-walled?
+6. Design-system source of truth?
+7. WCAG target + named a11y owner?
+
+---
+
+## Invocation from other agents and skills
+
+Three surfaces:
+
+1. **Slash command:** `/cs:frontend-review <prompt>` — full grill + decision engine + composition routing.
+2. **Agent subagent:** `Agent({subagent_type: "cs-frontend-engineer", prompt: "..."})` — forks context, returns ≤ 200-word digest.
+3. **Direct tool call:** `python scripts/frontend_decision_engine.py ...` — deterministic profile match when inputs are known.
+
+See `agents/engineering/cs-frontend-engineer.md` for the full invocation contract.
--- a/docs/skills/engineering-team/senior-fullstack.md
+++ b/docs/skills/engineering-team/senior-fullstack.md
@ -294,3 +294,102 @@ See `references/tech_stack_guide.md` for detailed comparison.
 | Auth complexity | Use Auth.js or Clerk |
 | Type errors | Enable strict mode in tsconfig |
 | CORS issues | Configure middleware properly |
+
+---
+
+## Assumptions and Verifiable Success Criteria (Karpathy discipline)
+
+Before this skill scaffolds, recommends, or modifies any code, the following four assumptions MUST be surfaced. If any are unknown, the skill stops and walks the [Forcing-question library](#forcing-question-library-matt-pocock-grill) instead.
+
+1. **Team size today + 12-month headcount** — drives architecture (monolith / modular / services). Sam Newman: "MonolithFirst."
+2. **Deployment cadence target** — drives CI/CD spend and feature-flag investment. *Accelerate* (Forsgren et al. 2018).
+3. **User-facing vs. internal vs. marketing-site** — drives stack pick and a11y/perf budget.
+4. **Monthly cloud + SaaS budget ceiling** — drives the build-vs-managed-service split.
+
+**Verifiable success criteria** (Karpathy #4) — every recommendation this skill emits must include three machine-checkable numbers:
+
+- An API latency target (p50, p95, p99 in ms)
+- A frontend perf target (LCP, INP, CLS on mobile-4G)
+- An uptime / SLO target
+
+If any of those three is not stated, the recommendation is incomplete — go back to Q7 of the forcing-question library.
+
+The `scripts/fullstack_decision_engine.py` tool encodes these checks: it refuses to recommend a profile without all four assumption inputs and prints the verifiable thresholds for the matched profile.
+
+---
+
+## Customization profiles
+
+Four built-in profiles in `profiles/` calibrate every recommendation:
+
+| Profile | When to pick | Cloud ceiling | Pattern |
+|---|---|---|---|
+| `saas-startup` | < 10 eng, customer-facing, daily+ cadence | $8K/mo | Modular monolith on Next.js + Postgres |
+| `enterprise-scale` | 50+ eng, regulated, per-PR with gates | $250K/mo | Domain-bounded services + platform team |
+| `internal-tool` | ≤ 5 eng, auth-walled, < 100 DAU | $500/mo | Retool-first; thin custom stack if forced |
+| `marketing-site` | SEO-dependent, near-zero write | $200/mo | Static-first (Astro / 11ty / Next-static) |
+
+Pick a profile via:
+
+```bash
+python scripts/fullstack_decision_engine.py \
+  --team-size 6 --team-size-12mo 12 \
+  --cadence daily --user-facing true --budget 5000 \
+  --traffic-p99-rps 45 --data-sensitivity pii-only
+```
+
+The tool returns the best-fit profile, the tradeoff against the runner-up (if within 15%), the stack recommendation, the anti-patterns to avoid on that profile, and the named-approver chain. **This tool never auto-approves.**
+
+To add a custom profile: copy `profiles/saas-startup.json` to `profiles/<your-org>.json`, adjust the `constraints` and `stack_recommendations` blocks, and rerun. The JSON is the customization surface — no code changes needed.
+
+---
+
+## Composition map
+
+This skill does NOT reimplement scope owned by the POWERFUL-tier specialists. It forks into them. See `references/composition_map.md` for the full routing table. Key forks:
+
+| Concern | Fork into |
+|---|---|
+| API contract review | `engineering/skills/api-design-reviewer/` |
+| Database schema design | `engineering/skills/database-designer/` |
+| Reliability / SLO design | `engineering/slo-architect/` |
+| CI/CD pipeline | `engineering/skills/ci-cd-pipeline-builder/` |
+| Performance profiling | `engineering/skills/performance-profiler/` |
+| Pre-commit Karpathy review | `engineering/karpathy-coder/` |
+| Pre-flight architecture grill | `engineering/grill-me/` |
+
+The `cs-fullstack-engineer` agent (in `agents/engineering/cs-fullstack-engineer.md`) orchestrates these forks via `context: fork`. Invoke it from another agent with `Agent({subagent_type: "cs-fullstack-engineer", prompt: "..."})` or via the slash command `/cs:fullstack-review <your problem>`.
+
+---
+
+## Forcing-question library (Matt Pocock grill)
+
+Before locking any architecture or stack decision, walk the seven forcing questions in `references/forcing_questions.md`. Each has a recommended answer, canon citation, and kill criterion. The discipline:
+
+1. One question per turn. No bundling.
+2. Always recommend the answer with cited canon.
+3. Track answers in a working file (e.g., `/tmp/fullstack-grill-<date>.md`).
+4. If a kill criterion trips, stop. Do not scaffold around an unresolved gap.
+5. After Q7, run `fullstack_decision_engine.py` with the seven answers as inputs.
+
+Summary of the seven questions (full content in the reference):
+
+1. Team size today + 12-month headcount?
+2. Deployment cadence — per-PR, daily, weekly, quarterly?
+3. Customer-facing, internal tool, or marketing site?
+4. One-year p50 / p99 traffic forecast?
+5. Hiring against the stack or training the team?
+6. Year-one monthly cloud + SaaS ceiling?
+7. Three verifiable success criteria with numeric targets?
+
+---
+
+## Invocation from other agents and skills
+
+This skill is invokable by any other agent or skill via three surfaces:
+
+1. **Slash command:** `/cs:fullstack-review <prompt>` — runs the full grill + decision engine + composition routing.
+2. **Agent subagent:** `Agent({subagent_type: "cs-fullstack-engineer", prompt: "..."})` — forks context, returns ≤ 200-word digest.
+3. **Direct tool call:** `python scripts/fullstack_decision_engine.py ...` — deterministic profile match without the conversational grill (use when inputs are already known).
+
+See `agents/engineering/cs-fullstack-engineer.md` for the full invocation contract.
--- a/docs/skills/productivity/handoff.md
+++ b/docs/skills/productivity/handoff.md
@ -0,0 +1,202 @@
+---
+title: "Handoff — Agent Skill for Personal Productivity"
+description: "Compact the current conversation into a handoff document for another agent to pick up. Save to a user-configured location (OS temp, home folder, or. Agent skill for Claude Code, Codex CLI, Gemini CLI, OpenClaw."
+---
+
+# Handoff
+
+<div class="page-meta" markdown>
+<span class="meta-badge">:material-lightning-bolt-outline: Productivity</span>
+<span class="meta-badge">:material-identifier: `handoff`</span>
+<span class="meta-badge">:material-github: <a href="https://github.com/alirezarezvani/claude-skills/tree/main/productivity/handoff/skills/handoff/SKILL.md">Source</a></span>
+</div>
+
+<div class="install-banner" markdown>
+<span class="install-label">Install:</span> <code>claude /plugin install productivity-skills</code>
+</div>
+
+
+Write a handoff document summarising the current conversation so a fresh agent can continue the work. Save to the temporary directory of the user's OS — not the current workspace.
+
+Include a "suggested skills" section in the document, which suggests skills that the agent should invoke.
+
+Do not duplicate content already captured in other artifacts (PRDs, plans, ADRs, issues, commits, diffs). Reference them by path or URL instead.
+
+Redact any sensitive information, such as API keys, passwords, or personally identifiable information.
+
+If the user passed arguments, treat them as a description of what the next session will focus on and tailor the doc accordingly.
+
+## Invocation Triggers
+
+**Explicit phrases** (any of):
+- "hand this off"
+- "handoff doc"
+- "summarize this for a new session"
+- "compact this conversation"
+- "I'm ending this session"
+- "pick this up later"
+- "wrap this up for tomorrow"
+- "save this for the next session"
+
+**Implicit signals** (no phrase, but the intent is unmistakable):
+- User announces they're switching machines or stopping for the day mid-task
+- Conversation context is growing long without a natural stopping point
+- User says "let me come back to this" or "I'll continue this later"
+
+When you detect an implicit trigger, propose the handoff before running it: *"Want me to write a handoff for the next session?"* — never run it silently.
+
+## First-Run Setup
+
+On first invocation, the skill asks where to save handoffs so the project folder never gets cluttered. Setup is offered once via *"Run setup now? (Y/n)"* — answering N uses OS-temp defaults for this run and never re-prompts. The user can rerun setup any time via `/cs:handoff-setup`.
+
+See [references/configuration.md](https://github.com/alirezarezvani/claude-skills/tree/main/productivity/handoff/skills/handoff/references/configuration.md) for the full config field reference.
+
+## Output Path
+
+The save location is read from the user's config (`~/.config/handoff/config.json`, or the project-local `.handoff/config.json` if present). When no config exists and the user declined setup, fall back to:
+
+```bash
+mktemp -t handoff-XXXXXX.md
+```
+
+Read the file before you write to it.
+
+## Section Template
+
+The handoff doc has five sections. Use these exact headers:
+
+- **Goal of next session** — from the user's argument, or inferred from the most recent thread of the conversation.
+- **State of play** — what's done, what's in flight, what's blocked. Reference artifacts, do not paste them.
+- **Open decisions** — what the next agent must decide before continuing.
+- **Skills to use** — concrete list of 3-5 skills the next session should invoke, each with a one-line *why*.
+- **Artifacts** — paths/URLs to PRDs, plans, ADRs, issues, branches, PRs. Do not duplicate their contents.
+
+See [references/handoff_structure.md](https://github.com/alirezarezvani/claude-skills/tree/main/productivity/handoff/skills/handoff/references/handoff_structure.md) for a worked example.
+
+## The Agent's Job
+
+Filling in the five sections is the agent's job, not the script's. Follow [references/handoff_prompt.md](https://github.com/alirezarezvani/claude-skills/tree/main/productivity/handoff/skills/handoff/references/handoff_prompt.md) as a mandatory checklist:
+
+> For each topic discussed in the conversation, decide explicitly: *include in State of play / log as an Open decision / drop with reason.*
+
+Free-handing the summary leads to rosy progress reports and dropped blockers. The checklist prevents that.
+
+## Anti-Patterns
+
+Matt's no-duplication discipline made concrete:
+
+- **Do not paste the diff.** Reference the branch or PR.
+- **Do not retype the PRD.** Link to its path.
+- **Do not summarise what's already in the commit message.** Link to the commit hash.
+- **Do not list 20 skills.** Pick the 3-5 the next session actually needs.
+- **Do not narrate every message in the conversation.** Compress to State + Decisions.
+
+See [references/deduplication_discipline.md](https://github.com/alirezarezvani/claude-skills/tree/main/productivity/handoff/skills/handoff/references/deduplication_discipline.md) for the full list.
+
+## Redaction
+
+Before saving, the linter scans the draft for secrets and PII. In strict mode (default) it blocks save on findings; in warn mode it flags inline and saves anyway.
+
+Redact:
+- API keys, OAuth tokens, JWT tokens
+- Passwords and DB connection strings
+- `-----BEGIN ... PRIVATE KEY-----` blocks
+- `.env`-style `KEY=value` lines containing secrets
+- Email addresses, phone numbers, names of unrelated third parties
+- Internal URLs containing tokens or session IDs
+
+See [references/redaction_checklist.md](https://github.com/alirezarezvani/claude-skills/tree/main/productivity/handoff/skills/handoff/references/redaction_checklist.md) for the full pattern list and manual-review steps for what regex cannot catch.
+
+## SessionStart Auto-Load
+
+When the plugin is installed, a `SessionStart` hook scans the configured save location for the most recent handoff (within the retention window) and surfaces it to the new session as `<handoff_from_previous_session>` data. The next agent reads it as context, not as instructions — suggested actions must be verified against current state before executing.
+
+Disable per-session with `HANDOFF_SESSIONSTART=0`.
+
+## SessionEnd Reminder
+
+A paired `SessionEnd` hook checks whether a recent handoff exists when the session is ending. If none does (or the most recent is older than 30 minutes), it prints a one-line reminder so the user is prompted to write one before context is lost.
+
+The hook cannot prompt interactively or block session end — it surfaces text in the session log.
+
+Disable per-session with `HANDOFF_SESSIONEND=0`.
+
+## Refreshing an Existing Handoff
+
+When work continues past the original handoff time, refresh in place instead of creating a new file:
+
+```bash
+python3 scripts/handoff_template_generator.py --refresh --goal "<updated goal>"
+```
+
+Prints the path of the most recent handoff. The agent edits it directly. Keeps the save location uncluttered and ensures the SessionStart hook always loads the up-to-date version.
+
+## Tools
+
+| Tool | Purpose |
+|---|---|
+| `setup.py` | First-run Q&A — save location, retention, redaction strictness, git-context, recommender scope. |
+| `handoff_template_generator.py` | Writes the 5-section scaffold at the configured path. `--refresh` reuses the most recent handoff instead of creating a new file. |
+| `redaction_linter.py` | Scans the draft for secrets/PII before save. Exit 1 on findings in strict mode. |
+| `handoff_self_check.py` | Fidelity check — flags empty Goal, State bullets without artifacts, missing Decisions when git is dirty, too few/many Skills, inline content in Artifacts. Run before the linter. |
+| `skill_recommender.py` | Suggests 3-5 skills for the next session based on goal text + repo scan. |
+| `cleanup.py` | Deletes scaffolds older than the retention window. mtime-guarded — never deletes a handoff the user edited. |
+| `config_loader.py` | Shared helper: read project config → global config → defaults. |
+
+## Slash Commands
+
+- `/cs:handoff [optional next-session description]` — generate the handoff.
+- `/cs:handoff-setup` — reconfigure save location, retention, redaction.
+
+## Agent
+
+`cs-handoff-author` — Matt-voice persona orchestrating the skill. Terse, no-duplication, references-not-copies.
+
+## Examples
+
+### Example 1 — explicit invocation with a goal
+
+```
+User: /cs:handoff "finish wiring the redaction linter and open a draft PR"
+```
+
+The skill walks the mandatory checklist, generates a 5-section scaffold, fills it from the conversation, runs the redaction linter, and saves to the configured location. See `assets/example_handoff.md` for a complete worked example.
+
+### Example 2 — implicit trigger
+
+```
+User: I'm packing up for the day, let me come back to this tomorrow.
+```
+
+Detect the implicit signal. Propose before running: *"Want me to write a handoff for the next session?"* — never silently. On confirmation, proceed as Example 1 with an inferred goal.
+
+### Example 3 — first-run setup
+
+```
+User: /cs:handoff "ship the migration"
+Skill: Run setup now? (Y/n)
+User: Y
+[setup walks 5 questions: save location, retention, redaction strictness, git context, recommender scope]
+Skill: Config saved to ~/.config/handoff/config.json. Continuing with handoff for: ship the migration.
+```
+
+If the user answers N, the skill writes a sentinel and uses defaults (OS temp dir, 7-day retention, strict redaction). The prompt never re-appears.
+
+### Example 4 — SessionStart auto-load
+
+On the next session, the SessionStart hook scans the configured save location, finds the most recent handoff, and surfaces it as `<handoff_from_previous_session>` data. The next agent reads it as context, not instructions.
+
+## Usage
+
+| Step | Command |
+|---|---|
+| First-run setup | `/cs:handoff-setup` (or answer Y on first `/cs:handoff`) |
+| Generate a handoff | `/cs:handoff [goal]` |
+| Reconfigure later | `/cs:handoff-setup --reconfigure` |
+| Project-specific config | `/cs:handoff-setup --project` |
+| Disable SessionStart hook | `HANDOFF_SESSIONSTART=0` (per session) |
+
+---
+
+**Version:** 1.0.0
+**Inspired by:** [Matt Pocock's handoff](https://github.com/mattpocock/skills/tree/main/skills/productivity/handoff) (MIT).
--- a/docs/skills/productivity/index.md
+++ b/docs/skills/productivity/index.md
@ -1,13 +1,13 @@
 ---
 title: "Productivity Skills — Agent Skills & Codex Plugins"
-description: "4 productivity skills — personal productivity agent skill and Claude Code plugin for brain-dump capture, email triage, and reflection. Works with Claude Code, Codex CLI, Gemini CLI, and OpenClaw."
+description: "5 productivity skills — personal productivity agent skill and Claude Code plugin for brain-dump capture, email triage, and reflection. Works with Claude Code, Codex CLI, Gemini CLI, and OpenClaw."
 ---

 <div class="domain-header" markdown>

 # :material-lightning-bolt-outline: Productivity

-<p class="domain-count">4 skills in this domain</p>
+<p class="domain-count">5 skills in this domain</p>

 </div>

--- a/mkdocs.yml
+++ b/mkdocs.yml
@ -426,6 +426,7 @@ nav:
      - "Inbox Setup (KB Builder)": skills/productivity/email-inbox-setup.md
      - "Inbox Triage (Drafts-Only)": skills/productivity/email-inbox-triage.md
      - "Reflect (Light-Prompt Journal)": skills/productivity/reflect.md
+      - "Handoff (Matt Pocock-inspired)": skills/productivity/handoff.md
    - Marketing (Landing Pages):
      - Overview: skills/marketing/index.md
      - "Landing Page Generator (HTML)": skills/marketing/landing.md