enterprise-dev

Mandatory read-only pre-action and plan-review protocol for substantive coding, debugging, design, review, refactor, system-analysis, workflow, and…

Audit pull requests, branches, diffs, or local source files for semantically suspicious variable, identifier, member-access, and payload-field usage.

Use when debugging bugs, failures, regressions, stale proof, recurring whack-a-mole fixes, unclear ownership, poor seams, missing domain boundaries…

Use when inspecting Helpdesk domains for SRP, README, write-boundary, table ownership, or service-migration opportunities and when running one selected domain…

Use when preparing to deploy code to production, merging to main, running migrations on production databases, or setting environment variables on Render.

Review plans, fixes, and designs before implementation so code can be built mechanically.

Use when choosing daily Helpdesk service-to-domain migration candidates, table ownership moves, write seam consolidation, domain README gaps, or A-plus…

Project-grounded blast-radius tracing for code changes, PRs, diffs, files, symbols, or bugfixes, especially in Helpdesk-style repos.

Standard rigorous multi-agent pipeline for bugs and build tasks that "must be workflowed".

Relentless curiosity-driven questioning skill that drills down to root causes and concrete facts.

Ultra-frictionless stream-of-consciousness capture for ADHD minds.

Resume a conductor dispatch — loads fleet state and handovers from Obsidian, presents what completed/failed, and offers verify/redispatch/merge options.