Slash Commands¶
92 commands for quick access to common operations
-
Scan a frontend project for WCAG 2.2 accessibility issues, show fixes, and optionally check color contrast.
-
Generate Keep a Changelog entries from git history and validate commit message format.
-
Step through the design of a chaos engineering experiment using the chaos-engineering skill. Produces a plan, calcula...
-
Reverse-engineer a frontend codebase into a complete Product Requirements Document.
-
Build competitive matrices with weighted scoring, gap analysis, and market positioning insights.
-
Command: /cs:aeo action args
-
Use the cs-backend-engineer agent (uses context: fork) to handle this inquiry:
-
Walk the user through the Matt Pocock forcing-question discipline before they lock any engineering decision. This is ...
-
Use the cs-frontend-engineer agent (uses context: fork) to handle this inquiry:
-
Use the cs-fullstack-engineer agent (which uses context: fork to keep the parent thread clean) to handle this inquiry:
-
Command: /cs:webinar mode args
-
Analyze financial statements, build valuation models, assess budget variances, and construct forecasts.
-
Run the full feature-flag cleanup workflow:
-
Systematically repair an entire feature or module using the 5-phase protocol. Target: $ARGUMENTS (a feature path or m...
-
Google Workspace CLI administration via the gws CLI. Run setup diagnostics, security audits, browse and execute recip...
-
Review your staged changes (or last commit) against Karpathy's 4 coding principles.
-
Generate cascaded OKR frameworks from company-level strategy down to team-level key results.
-
Run the full audit on a Kubernetes Operator repository:
-
Generate structured user personas with demographics, goals, pain points, and behavioral patterns.
-
Detect project stack and generate CI/CD pipeline configurations for GitHub Actions or GitLab CI.
-
Full audit pipeline for any skill, plugin, agent, or command in this repository. Runs 8 validation phases, auto-fixes...
-
Generate a concise, evidence-gated product requirements document for $ARGUMENTS.
-
Generate portfolio health dashboards and risk matrices for project oversight.
-
Analyze retrospective data for recurring themes, sentiment trends, and action item effectiveness.
-
Prioritize features using RICE scoring (Reach, Impact, Confidence, Effort) with optional capacity constraints.
-
Calculate SaaS financial health metrics from raw business numbers, benchmark against industry standards, and project ...
-
Systematically scan, audit, and optimize documentation files for SEO. Targets README.md files and docs/ pages — fixes...
-
Step through SLO design using the slo-architect skill. Produces an SLO definition, computes error budget + multi-wind...
-
Score sprint health across delivery, quality, and team metrics with velocity trend analysis.
-
Create a sprint plan for $ARGUMENTS with explicit capacity math, a carry-over check, and a definition-of-ready gate. ...
-
Dispatch a TC (Technical Change) command. Arguments: $ARGUMENTS.
-
Drive a test-first workflow for $ARGUMENTS using the TDD Guide skill. The first word of $ARGUMENTS selects the mode (...
-
Scan codebases for technical debt, score severity, and generate prioritized remediation plans.
-
Generate structured user stories with acceptance criteria, story points, and sprint capacity planning.
-
Ingest a new source into the LLM Wiki. This is the most-used command.
-
Bootstrap a new LLM Wiki vault. Creates raw/, wiki/{entities,concepts,sources,comparisons,synthesis}, the index and l...
-
Health-check the wiki. Surfaces orphan pages, broken wikilinks, stale claims, missing frontmatter, contradictions, an...
-
Show recent entries from wiki/log.md. Every LLM operation on the wiki leaves a standardized entry:
-
Ask the wiki a question. The librarian reads index.md first, picks relevant pages across categories, synthesizes an a...
-
Command: /cs:caveman
-
Activates the claude-coach skill. From this point on, the conversation gains:
-
Command: /cs:grill-me
-
Command: /cs:grill-with-docs
-
Command: /cs:handoff
-
Run a gated extraction pipeline for $ARGUMENTS using skills/universal-scraping-architect/SKILL.md.
-
Command: /cs:workflow-build
-
Command: /cs:write-a-skill
-
Command: /cs:andreessen
-
Command: /cs:pmf-check
-
Command: /cs:capture
-
Command: /cs:inbox-setup
-
Command: /cs:inbox-triage
-
Configure the handoff skill. Walks 5 questions (plus 1-2 optional) and writes the config. Re-run any time.
-
Command: /cs:reflect
-
Command: /cs:landing
-
Command: /cs:dossier
-
Command: /cs:grants
-
Command: /cs:litreview
-
Command: /cs:notebooklm
-
Command: /cs:patent
-
Command: /cs:pulse
-
Command: /cs:research
-
Command: /cs:syllabus
-
Use the cs-bizops-orchestrator agent + business-operations-skills orchestrator skill to handle this inquiry:
-
Run the capacity-planner skill on this input:
-
Apply Matt Pocock's grill-with-docs discipline to this BizOps plan / problem:
-
Run the internal-comms skill on this input:
-
Run the knowledge-ops skill on this input:
-
Run the process-mapper skill on this input:
-
Run the procurement-optimizer skill on this input:
-
Run the vendor-management skill on this input:
-
Run the channel-economics skill on this input:
-
Run the commercial-forecaster skill on this input:
-
Run the commercial-policy skill on this input:
-
Use the cs-commercial-orchestrator agent + commercial-skills orchestrator skill to handle this inquiry:
-
Run the deal-desk skill on this input:
-
Apply Matt Pocock's grill-with-docs discipline to this Commercial plan / problem:
-
Run the partnerships-architect skill on this input:
-
Run the pricing-strategist skill on this input:
-
Run the rfp-responder skill on this input:
-
Run the clinical-research skill on this input:
-
Apply Matt Pocock's grill-with-docs discipline to this plan / problem:
-
Run the market-research skill on this input:
-
Run the product-research skill on this input:
-
Run the research-finance skill on this input:
-
Route this inquiry through the research-ops-skills orchestrator:
-
Run the design-system wizard:
-
Walk the user through 5 forcing questions before routing to the converter. One question per turn, with a recommended ...
-
Route this conversion through the markdown-html-orchestrator skill:
-
Convert the markdown at $ARGUMENTS into a single-file interactive HTML document.
-
Convert the review markdown at $ARGUMENTS into a single-file 2-column HTML review.
-
Convert the markdown deck at $ARGUMENTS into a single-file interactive HTML presentation.