DEPRECATED — Use /enterprise instead. This skill has been superseded by the modular enterprise pipeline (/enterprise orchestrator + /enterprise-discover, /enterprise-brainstorm, /enterprise-plan, /enterprise-contract, /enterprise-build, /enterprise-review, /enterprise-forge, /enterprise-verify, /enterprise-compound).…
Deep root-cause analysis for API endpoint crashes and frontend display bugs in the Cortex stack — Express route handlers, service layer queries, React component rendering, and data formatting. Use this skill when the user reports 500 errors, null reference crashes, "Cannot read properties of null/undefined", data that…
Deep root-cause analysis for concurrency, race condition, and duplicate processing bugs in the Cortex stack — Shopify webhook double-firing, queue worker race conditions, idempotency failures, and any bug where the same operation appears to execute twice or where timing affects correctness. Use this skill when the…
Deep root-cause analysis for data sync bugs in the Cortex stack — REX SOAP sync, Shopify product/inventory sync, and any pipeline where data flows between external systems and the local PostgreSQL database. Use this skill when the user reports wrong data after a sync ("wrong supplier", "missing products", "inventory…
Deep root-cause analysis using the 5 Whys method for the Cortex stack (Express + JS + PostgreSQL + React/Vite). Use this skill when diagnosing bugs, unexpected behavior, test failures, or system issues. This skill NEVER changes code — it only reads, traces, and analyzes. Trigger whenever the user says "debug", "why is…
Project-grounded blast-radius tracing for code changes, PRs, diffs, files, symbols, or bugfixes, especially in Helpdesk-style repos. Use before editing, committing, merging, or reviewing when downstream callers, tests, routes, SQL, configs, schema, auth/tenant boundaries, external integrations, sibling bugs, or…
Ultra-frictionless stream-of-consciousness capture for ADHD minds. Accepts raw unstructured text and parses it into discrete vault items — bugs, tasks, features, ideas, business thoughts, personal errands, learning goals, creative sparks. Works across ALL life domains, not just code. Use when the user says "brain…
Standard rigorous multi-agent pipeline for bugs and build tasks that "must be workflowed". Engage when the user says "workflow this", "must be workflowed", "run the bug factory", "process the open bugs", "sweep and fix the bugs", or flags a build/bug task for the full pipeline. Sweeps open issues tagged bug (closes…
Relentless curiosity-driven questioning skill that drills down to root causes and concrete facts. Use this skill when you need to deeply understand something before acting — debugging, planning, requirements gathering, architecture decisions, investigating unknowns, or any situation where surface-level understanding…
Audit pull requests, branches, diffs, or local source files for semantically suspicious variable, identifier, member-access, and payload-field usage. Use when checking wrong-object bugs such as product.id versus rexProduct.id, source-system identity confusion, alias erasure, mismatched payload keys, or cross-system…
Resume a conductor dispatch — loads fleet state and handovers from Obsidian, presents what completed/failed, and offers verify/redispatch/merge options. Use when: starting a new session after a conductor dispatch, checking on worker results, picking up where a fleet left off. Triggers on: 'resume dispatch', 'what…
Review plans, fixes, and designs before implementation so code can be built mechanically. Use before coding, contract review, spec audit, readiness checks, or post-implementation contract verification. Fails vague contracts and missing Mechanical Build Packet fields.
Index or reindex the current project with cortex-engine. Use when the user says "index this repo", "reindex", "cortex index", or invokes /cortex-index. Also use when cortex queries return empty or stale results.
Use when choosing daily Helpdesk service-to-domain migration candidates, table ownership moves, write seam consolidation, domain README gaps, or A-plus architecture burn-down work before implementation.
Use when inspecting Helpdesk domains for SRP, README, write-boundary, table ownership, or service-migration opportunities and when running one selected domain refactor lane through enterprise gates, PR audits, review loops, and explicit dev merge authorization.
Mandatory read-only pre-action and plan-review protocol for substantive coding, debugging, design, review, refactor, system-analysis, workflow, and business-context work. Use this skill to prevent first-match excitement by forcing source-grounded reading, explicit zoom-out system mapping, operator/business framing…
Use when preparing to deploy code to production, merging to main, running migrations on production databases, or setting environment variables on Render. Use when the user mentions "deploy", "push to production", "merge to main", "run migrations", or asks about pending deploy items. Also use when reviewing what needs…
Bounded consensus workflow for diagnostic skills, root-cause handoffs, fix evals, and pasteable /goal prompts. Use when Ben asks for a cohort, committee, looping agreement, multi-agent diagnostic review, but-why style assumption challenge, or when diagnose, patch-or-fix, blast-radius, or another diagnostic gate needs…
Turn a vague or product-shaped enterprise request into a Technical Design Document. Extract intent, read source, design the product/workflow, then write a source-grounded TDD for plan/contract.
Use when a locked enterprise contract and mechanical build packet exist and implementation must proceed through strict TDD, contract traceability, receipt-only progress, and staged review handoffs. Always use this for enterprise build-stage work; stop if the complete build body is unavailable.
Use when verified enterprise work or a resolved debugging session should be captured as searchable institutional knowledge with prevention guidance.
★not rated 7 1mo agoA24 tokens
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: