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.
Creates mechanical contracts with postconditions, invariants, error cases, and consumer maps. Every postcondition is traceable to a test and a code line. Contracts must exist before any source code edits. Use after enterprise-plan.
Creates mechanical contracts with postconditions, invariants, error cases, and consumer maps. Every postcondition is traceable to a test and a code line. Contracts must exist before any source code edits. Use after enterprise-plan.
Use when an enterprise implementation plan exists and work needs a locked contract with postconditions, invariants, consumer mapping, and traceability before build starts.
Systematic enterprise debugging for bugs, failing tests, and unexpected behavior. Reproduce, trace, scan blast radius, identify root cause, then fix with TDD and prevention records.
Full enterprise workflow for legacy enterprise-dev invocations. Use when starting a feature, significant refactor, enterprise hardening effort, GitHub issue intake/processing, or multi-stage bugfix that needs end-to-end workflow control, portable repo-local artifacts, and explicit proof scope.
Use when starting enterprise work in a new repo, new worktree, unfamiliar package, or new computer, or whenever commands, paths, conventions, portability, or project traps are not yet known.
Use when enterprise work has been built and reviewed and needs a final mechanical ship or release gate before merge, PR readiness, install, deploy, or signoff. Checks proof trace, current diff, architecture, post-merge test kit, rollback, observability, security/privacy, and performance regression readiness.
Use when an approved enterprise design exists and the next step is to turn it into an exact implementation plan with file paths, task boundaries, and verification commands.
End-to-end PR conversation closer and advisory review harvester for enterprise work. Use this whenever the user mentions unresolved PR conversations, Copilot/GitHub review comments, a PR that cannot merge, skipped/non-blocking Copilot feedback, a failed PR review, or asks to address/resolve/learn from PR feedback. It…
End-to-end enterprise workflow for turning multiple refactor opportunities into serial green pull requests. Use when the user asks to identify refactor/domain opportunities, create lane plans, run Helpdesk enterprise gates, use specialist subagents, loop code reviews such as /review, CodeRabbit, Copilot, or GitHub…
Use when enterprise implementation is complete enough for a structured review that separates spec compliance from code quality and classifies drift explicitly.
★not rated 7 2mo agoA26 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: