Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.
Use when approaching context limits (70%+ usage), switching tasks mid-stream, ending a session with incomplete work, or when the user says "write a handover", "save progress", "I need to stop", or "context is getting full". Also use proactively when you detect that context compression has started occurring.
Standards-enforcement gate that runs BEFORE implementation. Takes a plan, TDD, or fix proposal and hard-blocks it if SRP, seam, ownership, blast radius, edge cases, or root-cause reasoning are missing. Emits a hardening-report.md that downstream skills (enterprise-plan, enterprise-contract, patch-or-fix, b-deep-debug)…
Install and configure the claude-harness governance system in the current project. Sets up hooks, skills, settings.json, evidence system, Obsidian vault integration, and runs enterprise-discover to produce a stack profile. After this, /enterprise is ready to go. Use when starting a new project or adding the harness to…
Pull latest skills from claude-harness repo and sync to /.claude/skills/ and /.codex/skills/. Run this in any project to get the latest enterprise skills. Use when the user says 'update skills', 'sync skills', 'pull latest harness', or invokes /harness-update.
Oldest-first Helpdesk dev PR queue closeout orchestrator. Use when Ben asks to drain, close out, babysit, green, reply to review threads, or merge eligible open Helpdesk pull requests targeting dev. Requires live GitHub truth, clean isolated worktrees, full PR blast-radius fan-out, patch-or-fix for bugfix or behavior…
Apply final Claude/Codex consensus quality gates for Helpdesk PRs, goals, skills, and workflows before claiming ready, green, done, merge-ready, or workflow-complete.
Use when reviewing, creating, enabling, disabling, or troubleshooting Codex hooks; when hooks may be adding context noise, hidden state, stale disabled entries, or surprise behavior; or when proposing a guardrail hook. Keeps hooks mechanical, low-noise, PreToolUse-first, deterministic, and separate from skill decision…
Delivers changes incrementally. Use when implementing any feature or change that touches more than one file. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step.
Use when writing or modifying code that interacts with REX (Retail Express), Shopify, or any external integration/sync system. Triggers on work involving SOAP calls, REX API, Shopify API, inventory sync, order sync, product sync, fulfillment sync, or any code in services/retailExpress/, services/shopify, or queue…
Use after GitHub issues are created, discovered, pushed, or handed off and the operator asks "now what", "which issue should an agent do", "make this ready for a build agent", "turn these issues into agent prompts", or "classify the queue". Fetches live issue state, separates intake from proof, routes through…
Standalone single GitHub issue to green PR orchestrator. Use when Codex is asked to target one specific GitHub issue number, owner/repo#number, or issue URL and drive it through a one-subagent-one-job repair workflow into a proved PR. Requires diagnose, blast-radius, patch-or-fix, live GitHub gate discovery…
Automation-safe GitHub issue to green PR orchestrator. Use when Codex is asked to process GitHub issues labeled bug or needs-triage, run a one-agent-one-job repair workflow, create or babysit PRs, get PR checks/review threads green, or run a recurring Codex automation that turns eligible issues into proved pull…
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.
Adversarial code review with mechanical checks, contract probing, and 5 adversarial lenses. Bugs recycle to contract for full TDD treatment. 3-fail circuit breaker prevents infinite loops. Use after enterprise-review.
Start-of-day briefing for ADHD workflow. Shows what happened since last session, surfaces stale/blocked items across ALL life domains (dev, business, personal, learning, creative), recommends focus items, and proactively nudges about forgotten things. Use when the user says "good morning", "what's up", "brief me"…
Control nested single-job subagents without overrunning thread capacity. Use when the user asks for nested agents, subagents, bug-factory style one-agent-one-job delegation, review coordinators, multi-agent build/review/proof loops, or when prior agent loops hit thread limits and need disciplined orchestration.
Fast guilt-free shelving of vault items you're not doing right now. Preserves context and sets an optional reminder date. Works for dev items, business tasks, personal errands, learning goals — anything in the vault. Use when the user says "park this", "not now", "shelve it", "put it aside", "I'll do this later", or…
Evidence-gated post-fix review that classifies whether a bug change removes the root cause or only masks the symptom. Any invocation, including a one-sentence prompt, requires the full canonical workflow and Required Output sections: Evidence Ledger, Assumption Ledger, Boundary Ledger, Specialist Reviews, Causal…
Use when a plan, design, migration, or deployment checklist is drafted and needs review before passing a planning gate or proceeding to implementation. Triggers on phrases like "review this plan", "is this ready", "gate check", "audit the plan", "stakeholder review", or whenever a document in docs/plans/…
Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible. For refactor, debugging, lifecycle/status, or system-design plans, require source…
Create or run a post-merge validation kit for a PR after it lands. Use when the user asks how to test a merged PR, validate a release, smoke-test production, verify deploy behavior, or choose agent-run versus human-run post-merge checks.
Audit GitHub pull requests against the live Helpdesk Postgres schema. Use when asked to check a PR, merged PR, open PR, schema drift, SQL call coverage, database variables, or PR review failures against live database shape; publishes bug-labeled issues for merged or closed failing PRs and PR conversation comments for…
★not rated 7 1mo agoA79 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: