
Checks inline code documentation quality: WHY-not-WHAT, density, forbidden content, docstrings quality, actuality, legacy cleanup. Use when auditing comments and docstrings.
Checks runtime lifecycle and config validation: bootstrap, shutdown, probes, cleanup, env sync, and fail-fast startup. Use for runtime readiness.
Checks local maintainability hotspots: complexity, long methods, god modules, signatures, algorithms, and constants. Also flags identifier drift across API/DTO/DB layers. Use when auditing code hotspots.
Performs manual testing of Story AC via executable bash scripts in tests/manual/. Use when Story implementation needs hands-on AC verification.
Checks evidence-backed duplication, over-abstraction, and unused extensibility. Use when auditing DRY/KISS/YAGNI risk.
Checks races, deadlocks, async hazards, TOCTOU, blocking I/O, and shared resource contention. Use when auditing concurrency correctness.
Finds code that can be safely deleted: unreachable, unused, obsolete compatibility, and commented-out code. Use when pruning dead code.
Verifies claims in .md files (paths, versions, counts, configs, endpoints) against codebase, cross-checks contradictions. Use when auditing docs accuracy.
Checks diagnosability through structured logs, metrics, traces, correlation IDs, and useful log levels. Use when auditing incident visibility.
Checks application security boundaries: secrets, injection, XSS, input validation, and sensitive env defaults. Use when auditing exploitable code paths.
Use when auditing project documentation through the evaluation platform with mandatory research, coordinated audit workers, and structured summaries.
Checks document semantic content against SCOPE and project goals, coverage gaps, off-topic content, SSOT. Use when auditing documentation relevance.
Checks build, lint, type, test, and CI delivery gate failures. Use when auditing whether the project can reliably ship.
Checks dependency health and generic custom utility/integration replacement opportunities. Use when auditing dependency and reuse risk.
Plans automated tests (E2E/Integration/Unit) using Risk-Based Testing after manual testing. Use when Story needs a test task with prioritized scenarios.
Use when auditing the test surface through the evaluation platform with mandatory research, coordinated test audit workers, and structured summaries.
Use when auditing the codebase through the evaluation platform with mandatory research, coordinated domain audit workers, and structured summaries.
Checks hierarchy, links, SSOT, compression, requirements compliance, freshness, legacy cleanup. Use when auditing documentation structure.
Checks DRY/KISS/YAGNI/architecture compliance with quantitative Code Quality Score. Use when implementation tasks are Done and need quality scoring.
Analyzes application logs: classifies errors, checks log quality, maps stack traces to source. Use when logs need review after test runs or during development.
Auto-fixes low-risk tech debt (unused imports, dead code, commented-out code) with >=90% confidence. Use when audit findings need safe automated cleanup.
Orchestrates test planning pipeline: research, manual testing, automated test planning. Use when Story needs comprehensive test coverage planning.
Runs existing test suite to catch regressions after implementation changes. Use when Story needs regression verification. No status changes.
Researches real-world problems, competitor solutions, and customer complaints for a feature domain. Use before test planning to ground tests in actual user pain points.
Use when coordinating story quality evaluation with mandatory research, worker summaries, agent review, regression evidence, and bounded refinement.
Story-level quality gate with 4-level verdict (PASS/CONCERNS/FAIL/WAIVED) and Quality Score. Use when Story is ready for quality assessment.
Reviews task implementation for quality, code standards, and test coverage. Use when task is in To Review. Sets task Done or To Rework.
Fixes tasks in To Rework by applying reviewer feedback, then returns to To Review. Use when task was rejected during review.
Executes test tasks (label 'tests') through Todo to To Review with risk-based limits. Use for test task execution. Not for implementation tasks.
Executes implementation tasks through Todo, In Progress, To Review. Use when task needs coding with KISS/YAGNI. Not for test tasks.
Use when an evaluation run must merge research, findings, documentation, and repair outputs into one verified result.
Executes Story tasks in priority order (To Review, To Rework, Todo). Use when Story has planned tasks ready for implementation.
Use when validating Stories, plans, or tasks through the evaluation platform with mandatory research, parallel evidence lanes, sequential merge, and bounded refinement. Modes: story | plan_review.
Analyzes Story and builds optimal task plan (1-8 tasks), then routes to create or replan. Use when Story needs task breakdown or replanning.
Use when accepted findings require bounded repair changes and a structured repair summary.
Use when an evaluation run requires bounded iterative refinement with trace and cleanup evidence.
Replans Stories by comparing IDEAL vs existing (KEEP/UPDATE/OBSOLETE/CREATE). Use when Epic requirements changed and Stories need realignment.
Creates or replans 3-7 Epics from scope using Decompose-First pattern. Use when initiative needs Epic-level breakdown or Epic scope changed.
Creates Story documents with 9-section structure and INVEST validation via the configured tracker provider. Use when Epic has an IDEAL plan ready for Story generation.
Use when an evaluation run needs mandatory official-doc, MCP Ref, Context7, and current best-practice research with a structured research summary.
Decomposes scope into Epics, Stories, and RICE priorities. Use when user has project scope and wants full Agile breakdown.
Discovers growth opportunities using Traffic-First KILL funnel. Use when searching for next product direction with validated demand.
Creates, replans, or appends 5-10 Stories per Epic with standards research and multi-epic routing. Use when Epic needs Story decomposition.
RICE-scores Stories with market research and generates prioritization table. Use when Stories need business priority ranking for sprint planning.
Compares ideal plan vs existing tasks and applies KEEP/UPDATE/OBSOLETE/CREATE changes. Use when Story tasks need re-sync with updated requirements.
Creates implementation, refactoring, and test tasks from templates. Use when an approved task plan needs tasks created via the configured tracker provider and reflected in kanban.
Use when an evaluation run needs review-driven documentation updates and a structured documentation summary.
Use when an evaluation coordinator needs normalized findings from target artifacts and research evidence.
Drives a Story through full pipeline (tasks, validation, execution, quality). Use when executing a Story end-to-end from kanban board.
Use when deploying, redeploying, verifying, migrating, or syncing users for the hex-relay Telegram/API control plane on a VPS.
Use when installing, verifying, or updating the shared VPS host runtime for Claude Code, Codex, MCP, and marketplace plugins.
Use when inspecting health, drift, logs, auth, ports, systemd, tmux, or safe repair needs for one VPS project environment.
Use when creating or verifying one project runtime on a prepared VPS, including god-session, provider credentials, and local dispatcher setup.
Use when bootstrapping or managing VPS agent environments: fresh install, add project, hex-relay redeploy, diagnostics, or fleet plan/apply.
Use when an evaluation run needs review-driven documentation updates and a structured documentation summary.
Use when validating Stories, plans, or tasks through the evaluation platform with mandatory research, parallel evidence lanes, sequential merge, and bounded refinement. Modes: story | plan_review.
Use when accepted findings require bounded repair changes and a structured repair summary.
Reviews skills (D1-D11 + M1-M6 criteria) or .claude/commands for quality. Use when validating skill correctness before release.
Use when validating optimization plans through the evaluation platform with mandatory research, parallel agent evidence, sequential merge, and bounded refinement.
Use when an evaluation coordinator needs normalized findings from target artifacts and research evidence.
Use when coordinating story quality evaluation with mandatory research, worker summaries, agent review, regression evidence, and bounded refinement.
Drives a Story through full pipeline (tasks, validation, execution, quality). Use when executing a Story end-to-end from kanban board.
Story-level quality gate with 4-level verdict (PASS/CONCERNS/FAIL/WAIVED) and Quality Score. Use when Story is ready for quality assessment.
Creates slash commands from procedural doc sections. Use when transforming documentation prose into executable commands.
Executes Story tasks in priority order (To Review, To Rework, Todo). Use when Story has planned tasks ready for implementation.
Multi-cycle performance optimization with profiling and bottleneck analysis. Use when optimizing application performance.
Researches competitive benchmarks and generates optimization hypotheses for identified bottlenecks. Use after profiling.
Executes optimization hypotheses with keep/discard testing loop. Use when applying validated performance improvements.
Upgrades dependencies across all detected package managers. Use when updating npm, NuGet, or pip packages project-wide.
Modernizes codebase via OSS replacement and bundle optimization. Use when acting on audit findings to reduce custom code.
Replaces custom modules with OSS packages using atomic keep/discard testing. Use when migrating custom code to established libraries.
Reduces JS/TS bundle size via tree-shaking, code splitting, and unused dependency removal. Use when optimizing frontend bundle size.
Produces prioritized triage report from open GitHub issues, PRs, and discussions. Use when reviewing community backlog.
Composes and publishes announcements to GitHub Discussions. Use when sharing releases, updates, or news with the community.
Launches RFC and debate discussions on GitHub. Use when proposing changes that need community input or voting.
Responds to unanswered GitHub discussions and issues with codebase-informed replies. Use when clearing community question backlog.
Reviews task implementation for quality, code standards, and test coverage. Use when task is in To Review. Sets task Done or To Rework.
Sets up test infrastructure with Vitest, xUnit, and pytest. Use when adding testing frameworks and sample tests to a project.
Bootstraps projects to production-ready structure. Use when creating new or transforming existing projects.
Use when benchmarking hex-line MCP against Claude built-in tools with scenario manifests, activation checks, and diff-based correctness.
Analyzes current or recent session for errors, inefficiencies, and improvement opportunities across skills, tools, hooks, and communication. Use after completing a task or periodically.
Installs agents, configures MCP servers, aligns marketplace plugins, creates and audits instructions. Use after setup or when agents/MCP/plugins need alignment.
Installs agents, configures MCP servers, aligns marketplace plugins, creates and audits instructions. Use after setup or when agents/MCP/plugins need alignment.
Installs or updates Codex CLI and Claude Code. Use when CLI agents need installation or update.
Installs or updates Codex CLI and Claude Code. Use when CLI agents need installation or update.
Use when installing MCP packages and configuring Claude-side MCP registration, hooks, permissions, IDE extension mode, and migrations.
Use when installing MCP packages and configuring Claude-side MCP registration, hooks, permissions, IDE extension mode, and migrations.
Use when installing or verifying this marketplace in Claude and Codex, aligning selected plugins, MCP settings, and Codex execution defaults.
Creates AGENTS.md canonical and CLAUDE.md @AGENTS.md stub; audits token budget, cache safety, import-pattern compliance. Use when instruction files need alignment.
Creates AGENTS.md canonical and CLAUDE.md @AGENTS.md stub; audits token budget, cache safety, import-pattern compliance. Use when instruction files need alignment.
Use when removing Claude-side hex-line integration surfaces such as MCP registration, permissions, hooks, and output style.
Builds and queries code knowledge graph for dependency analysis, references, implementations, and architecture overview. Use when starting work on unfamiliar codebase or before refactoring.
Creates complete project documentation system (project docs, reference, tasks, tests). Use when bootstrapping docs from scratch or regenerating all.
Creates complete project documentation system (project docs, reference, tasks, tests). Use when bootstrapping docs from scratch or regenerating all.
Creates root documentation files (AGENTS.md, CLAUDE.md, docs/README.md, standards, principles). Use for initial project doc setup.
Creates core project docs (requirements, architecture, tech stack, patterns catalog). Use for any project regardless of type.
Creates design_guidelines.md with WCAG 2.1 compliance and design system docs. Use when project has a frontend.
Creates task management docs (kanban board, workflow rules) with Linear integration. Use when setting up task tracking for a project.
Creates test documentation (testing-strategy.md, tests/README.md) with Risk-Based Testing philosophy. Use when setting up test strategy for a project.
Extracts procedural content from project docs into slash commands. Use when docs contain deploy, test, or troubleshoot procedures.
Creates slash commands from procedural doc sections. Use when transforming documentation prose into executable commands.
Reviews skills (D1-D11 + M1-M6 criteria) or .claude/commands for quality. Use when validating skill correctness before release.
RICE-scores Stories with market research and generates prioritization table. Use when Stories need business priority ranking for sprint planning.
Analyzes Story and builds optimal task plan (1-8 tasks), then routes to create or replan. Use when Story needs task breakdown or replanning.
Checks DRY/KISS/YAGNI/architecture compliance with quantitative Code Quality Score. Use when implementation tasks are Done and need quality scoring.
Use when an evaluation run requires bounded iterative refinement with trace and cleanup evidence.
Checks redundant fetches, N+1 loops, over-fetching, missing bulk operations, wrong caching scope. Use when auditing query efficiency.
Analyzes application logs: classifies errors, checks log quality, maps stack traces to source. Use when logs need review after test runs or during development.
Plans automated tests (E2E/Integration/Unit) using Risk-Based Testing after manual testing. Use when Story needs a test task with prioritized scenarios.
Checks hierarchy, links, SSOT, compression, requirements compliance, freshness, legacy cleanup. Use when auditing documentation structure.
Checks document semantic content against SCOPE and project goals, coverage gaps, off-topic content, SSOT. Use when auditing documentation relevance.
Checks inline code documentation quality: WHY-not-WHAT, density, forbidden content, docstrings quality, actuality, legacy cleanup. Use when auditing comments and docstrings.
Checks cyclomatic complexity, nesting, long methods, god classes, O(n2), N+1 queries, constants management. Use when auditing code quality.
Checks DRY, KISS/YAGNI, error handling, DI patterns. Use when auditing code principles compliance.
Checks outdated packages, unused deps, reinvented wheels, CVE/CVSS vulnerability scan. Use when auditing dependencies.
Checks unreachable code, unused imports/variables/functions, commented-out code, unsupported patterns. Use when auditing dead code.
Checks structured logging, health checks, metrics collection, request tracing, log levels. Use when auditing observability.
Checks bootstrap initialization, graceful shutdown, resource cleanup, signal handling, liveness/readiness probes. Use when auditing app lifecycle.
Validates E2E coverage for critical paths (money, security, data integrity). Risk-based prioritization. Use when auditing E2E test coverage.
Checks test isolation (API/DB/FS/Time/Network), determinism, flaky tests, order-dependency, anti-patterns. Use when auditing test isolation.
Checks manual test scripts for harness adoption, golden files, fail-fast, config sourcing, idempotency. Use when auditing manual test quality.
Checks test file organization, directory layout, test-to-source mapping, domain grouping, co-location. Use when auditing test structure.
Analyzes single pattern implementation, calculates compliance/completeness/quality scores, identifies gaps. Use when auditing a specific pattern.
Discovers custom modules replaceable by OSS, evaluates alternatives (stars, license, CVE), generates migration plan. Use when reducing custom code.
Checks file hygiene, ignore files, framework conventions, domain/layer organization, naming. Use when auditing project structure.
Checks env var config sync, missing defaults, naming conventions, startup validation. Use when auditing environment configuration.
Checks blocking IO in async, unnecessary allocations, sync sleep, string concat in loops, redundant copies. Use when auditing runtime performance.
Checks session scope mismatch, missing cleanup, pool config, error path leaks, resource holding. Use when auditing resource lifecycle.
Bootstraps projects to production-ready structure. Use when creating new or transforming existing projects.
Scaffolds new React projects or restructures monoliths to component-based architecture. Use when setting up frontend structure.
Generates .NET Clean Architecture backend structure from entity definitions. Use when bootstrapping .NET backend projects.
Removes platform-specific artifacts from Replit, StackBlitz, CodeSandbox, Glitch. Use when preparing exported projects for production.
Sets up Docker, CI/CD, and environment configuration with auto-detection. Use when adding DevOps infrastructure to a project.
Generates Dockerfile and docker-compose configuration for multi-container development. Use when containerizing a project.
Generates GitHub Actions CI workflow configuration. Use when adding continuous integration to a project.
Configures ESLint, Prettier, Ruff, mypy, and .NET analyzers. Use when setting up linting and formatting for a project.
Configures ESLint, Prettier, Ruff, mypy, and .NET analyzers. Use when setting up linting and formatting for a project.
Sets up security scanning for secrets and dependency vulnerabilities. Use when adding security infrastructure to a project.
Configures structured JSON logging with Serilog (.NET) or structlog (Python). Use when adding logging to backend projects.
Verifies bootstrapped projects via build, test, and container health checks. Use when validating project setup completeness.
Builds and launches Docker containers with health verification. Use when validating that containerized services start correctly.
Upgrades npm/yarn/pnpm dependencies with breaking change handling. Use when updating JavaScript/TypeScript dependencies.
Upgrades Python pip/poetry/pipenv dependencies with breaking change handling. Use when updating Python dependencies.
Generates seed data from ORM schemas or entity definitions to any target format. Use when populating databases for development.
Configures CORS policy for development and production environments. Use when setting up cross-origin access for APIs.
Configures health check endpoints for Kubernetes readiness/liveness/startup probes. Use when deploying to Kubernetes.
Commits and pushes all changes (staged, unstaged, untracked) to remote. Use when you need a quick push of everything at once.
Coordinates project documentation creation with single context gathering and project type detection. Use when generating project docs subset.
Analyzes current or recent session for errors, inefficiencies, and improvement opportunities across skills, tools, hooks, and communication. Use after completing a task or periodically.
Configures environment variables and secrets protection. Use when setting up .env files and gitignore rules for a project.
Verifies claims in .md files (paths, versions, counts, configs, endpoints) against codebase, cross-checks contradictions. Use when auditing docs accuracy.
Creates root documentation files (AGENTS.md, CLAUDE.md, docs/README.md, standards, principles). Use for initial project doc setup.
Checks unreachable code, unused imports/variables/functions, commented-out code, unsupported patterns. Use when auditing dead code.
Upgrades dependencies across all detected package managers. Use when updating npm, NuGet, or pip packages project-wide.
Executes all test suites and reports results with coverage. Use when verifying that test infrastructure works after bootstrap.
Builds all detected projects and verifies successful compilation. Use when checking that a bootstrapped project compiles.
Sets up logging, error handling, CORS, health checks, and API docs. Use when adding cross-cutting concerns to backend projects.
Configures Swagger/OpenAPI documentation for backend APIs. Use when adding interactive API docs to a project.
Configures global exception handling middleware. Use when adding centralized error handling to .NET or Python backends.
Checks transaction scope, missing rollback handling, long-held transactions, trigger/notify interaction. Use when auditing transaction correctness.
Use when auditing persistence and runtime performance through the evaluation platform with mandatory research, coordinated data-layer workers, and structured summaries.
Checks layer leakage in method signatures, missing DTOs, entity leakage to API, inconsistent error contracts. Use when auditing API contracts.
Checks layer boundary violations, transaction boundaries, session ownership, cross-layer consistency. Use when auditing architecture layers.
Checks async races, thread safety, TOCTOU, deadlocks, blocking I/O, resource contention. Use when auditing concurrency safety.
Checks compiler/linter errors, deprecation warnings, type errors, failed tests, build config issues. Use when auditing build health.
Checks hardcoded secrets, SQL injection, XSS, insecure deps, input validation. Use when auditing security.
Auto-fixes low-risk tech debt (unused imports, dead code, commented-out code) with >=90% confidence. Use when audit findings need safe automated cleanup.
Sets up linters, pre-commit hooks, and test infrastructure. Use when adding code quality tooling to a project.
Coordinates project documentation creation with single context gathering and project type detection. Use when generating project docs subset.
Creates reference docs (ADRs, guides, manuals) for nontrivial tech stack choices. Use when project needs justified architecture decision records.
Use when validating optimization plans through the evaluation platform with mandatory research, parallel agent evidence, sequential merge, and bounded refinement.
Configures Husky, lint-staged, commitlint, and Python pre-commit hooks. Use when adding Git hook automation to a project.
Detects tests validating framework/library behavior instead of project code. Use when auditing test business logic focus.
Creates backend docs (api_spec.md, database_schema.md). Use when project has backend API or database.
Scans codebase for hardcoded secrets with severity classification and remediation guidance. Use when auditing a project for leaked credentials.
Checks compiler/linter errors, deprecation warnings, type errors, failed tests, build config issues. Use when auditing build health.
Creates backend docs (api_spec.md, database_schema.md). Use when project has backend API or database.
Upgrades .NET NuGet packages with breaking change handling. Use when updating .NET dependencies.
Scaffolds new or restructures existing projects to Clean Architecture. Use when setting up project structure.
Scores each test by Impact x Probability, returns KEEP/REVIEW/REMOVE decisions. Use when auditing test value and pruning low-value tests.
Use when auditing architectural patterns through the evaluation platform with mandatory best-practice research, coordinated pattern workers, and structured summaries.
Use when installing or verifying this marketplace in Claude and Codex, aligning selected plugins, MCP settings, and Codex execution defaults.
Sets up test infrastructure with Vitest, xUnit, and pytest. Use when adding testing frameworks and sample tests to a project.
Profiles runtime performance with CPU, memory, and I/O metrics. Use when measuring bottlenecks before optimization.
Builds dependency graph, detects cycles, validates boundary rules, calculates coupling metrics (Ca/Ce/I). Use when auditing dependency structure.
Identifies missing tests for critical paths (money, security, data integrity, core flows). Use when auditing test coverage gaps.
Analyzes community health and delegates engagement tasks. Use when managing GitHub issues, discussions, and announcements.
Creates infrastructure.md and runbook.md (Docker-conditional). Use for DevOps documentation in any project.
Discovers growth opportunities using Traffic-First KILL funnel. Use when searching for next product direction with validated demand.
Checks layer boundary violations, transaction boundaries, session ownership, cross-layer consistency. Use when auditing architecture layers.
Checks test isolation (API/DB/FS/Time/Network), determinism, flaky tests, order-dependency, anti-patterns. Use when auditing test isolation.
Checks bootstrap initialization, graceful shutdown, resource cleanup, signal handling, liveness/readiness probes. Use when auditing app lifecycle.
Use when auditing project documentation through the evaluation platform with mandatory research, coordinated audit workers, and structured summaries.
Scores each test by Impact x Probability, returns KEEP/REVIEW/REMOVE decisions. Use when auditing test value and pruning low-value tests.
Analyzes single pattern implementation, calculates compliance/completeness/quality scores, identifies gaps. Use when auditing a specific pattern.
Checks file hygiene, ignore files, framework conventions, domain/layer organization, naming. Use when auditing project structure.
Checks env var config sync, missing defaults, naming conventions, startup validation. Use when auditing environment configuration.
Checks redundant fetches, N+1 loops, over-fetching, missing bulk operations, wrong caching scope. Use when auditing query efficiency.
Checks transaction scope, missing rollback handling, long-held transactions, trigger/notify interaction. Use when auditing transaction correctness.
Builds all detected projects and verifies successful compilation. Use when checking that a bootstrapped project compiles.
Profiles runtime performance with CPU, memory, and I/O metrics. Use when measuring bottlenecks before optimization.
Modernizes codebase via OSS replacement and bundle optimization. Use when acting on audit findings to reduce custom code.
Creates, replans, or appends 5-10 Stories per Epic with standards research and multi-epic routing. Use when Epic needs Story decomposition.
Checks async races, thread safety, TOCTOU, deadlocks, blocking I/O, resource contention. Use when auditing concurrency safety.
Checks hardcoded secrets, SQL injection, XSS, insecure deps, input validation. Use when auditing security.
Detects tests validating framework/library behavior instead of project code. Use when auditing test business logic focus.
Executes test tasks (label 'tests') through Todo to To Review with risk-based limits. Use for test task execution. Not for implementation tasks.
Decomposes scope into Epics, Stories, and RICE priorities. Use when user has project scope and wants full Agile breakdown.
Creates reference docs (ADRs, guides, manuals) for nontrivial tech stack choices. Use when project needs justified architecture decision records.
Extracts procedural content from project docs into slash commands. Use when docs contain deploy, test, or troubleshoot procedures.
Use when benchmarking hex-line MCP against Claude built-in tools with scenario manifests, activation checks, and diff-based correctness.
Replaces custom modules with OSS packages using atomic keep/discard testing. Use when migrating custom code to established libraries.
Upgrades Python pip/poetry/pipenv dependencies with breaking change handling. Use when updating Python dependencies.
Upgrades npm/yarn/pnpm dependencies with breaking change handling. Use when updating JavaScript/TypeScript dependencies.
Researches competitive benchmarks and generates optimization hypotheses for identified bottlenecks. Use after profiling.
Multi-cycle performance optimization with profiling and bottleneck analysis. Use when optimizing application performance.
Builds and launches Docker containers with health verification. Use when validating that containerized services start correctly.
Configures Husky, lint-staged, commitlint, and Python pre-commit hooks. Use when adding Git hook automation to a project.
Checks session scope mismatch, missing cleanup, pool config, error path leaks, resource holding. Use when auditing resource lifecycle.
Checks blocking IO in async, unnecessary allocations, sync sleep, string concat in loops, redundant copies. Use when auditing runtime performance.
Checks layer leakage in method signatures, missing DTOs, entity leakage to API, inconsistent error contracts. Use when auditing API contracts.
Checks manual test scripts for harness adoption, golden files, fail-fast, config sourcing, idempotency. Use when auditing manual test quality.
Reduces JS/TS bundle size via tree-shaking, code splitting, and unused dependency removal. Use when optimizing frontend bundle size.
Builds dependency graph, detects cycles, validates boundary rules, calculates coupling metrics (Ca/Ce/I). Use when auditing dependency structure.
Validates E2E coverage for critical paths (money, security, data integrity). Risk-based prioritization. Use when auditing E2E test coverage.
Researches real-world problems, competitor solutions, and customer complaints for a feature domain. Use before test planning to ground tests in actual user pain points.
Checks structured logging, health checks, metrics collection, request tracing, log levels. Use when auditing observability.
Use when auditing persistence and runtime performance through the evaluation platform with mandatory research, coordinated data-layer workers, and structured summaries.
Checks DRY, KISS/YAGNI, error handling, DI patterns. Use when auditing code principles compliance.
Performs manual testing of Story AC via executable bash scripts in tests/manual/. Use when Story implementation needs hands-on AC verification.
Runs existing test suite to catch regressions after implementation changes. Use when Story needs regression verification. No status changes.
Fixes tasks in To Rework by applying reviewer feedback, then returns to To Review. Use when task was rejected during review.
Executes all test suites and reports results with coverage. Use when verifying that test infrastructure works after bootstrap.
Use when an evaluation run must merge research, findings, documentation, and repair outputs into one verified result.
Compares ideal plan vs existing tasks and applies KEEP/UPDATE/OBSOLETE/CREATE changes. Use when Story tasks need re-sync with updated requirements.
Creates implementation, refactoring, and test tasks from templates. Use when an approved task plan needs tasks created in Linear and kanban.
Replans Stories by comparing IDEAL vs existing (KEEP/UPDATE/OBSOLETE/CREATE). Use when Epic requirements changed and Stories need realignment.
Creates Story documents with 9-section structure and INVEST validation in Linear. Use when Epic has an IDEAL plan ready for Story generation.
Use when an evaluation run needs mandatory official-doc, MCP Ref, Context7, and current best-practice research with a structured research summary.
Creates core project docs (requirements, architecture, tech stack, patterns catalog). Use for any project regardless of type.
Builds and queries code knowledge graph for dependency analysis, references, implementations, and architecture overview. Use when starting work on unfamiliar codebase or before refactoring.
Use when removing Claude-side hex-line integration surfaces such as MCP registration, permissions, hooks, and output style.
Upgrades .NET NuGet packages with breaking change handling. Use when updating .NET dependencies.
Executes optimization hypotheses with keep/discard testing loop. Use when applying validated performance improvements.
Discovers custom modules replaceable by OSS, evaluates alternatives (stars, license, CVE), generates migration plan. Use when reducing custom code.
Use when auditing the test surface through the evaluation platform with mandatory research, coordinated test audit workers, and structured summaries.
Creates or replans 3-7 Epics from scope using Decompose-First pattern. Use when initiative needs Epic-level breakdown or Epic scope changed.
Executes implementation tasks through Todo, In Progress, To Review. Use when task needs coding with KISS/YAGNI. Not for test tasks.
Orchestrates test planning pipeline: research, manual testing, automated test planning. Use when Story needs comprehensive test coverage planning.
Use when auditing the codebase through the evaluation platform with mandatory research, coordinated domain audit workers, and structured summaries.
Identifies missing tests for critical paths (money, security, data integrity, core flows). Use when auditing test coverage gaps.
Checks cyclomatic complexity, nesting, long methods, god classes, O(n2), N+1 queries, constants management. Use when auditing code quality.
Checks outdated packages, unused deps, reinvented wheels, CVE/CVSS vulnerability scan. Use when auditing dependencies.
Use when auditing architectural patterns through the evaluation platform with mandatory best-practice research, coordinated pattern workers, and structured summaries.
Checks test file organization, directory layout, test-to-source mapping, domain grouping, co-location. Use when auditing test structure.
Commits and pushes all changes (staged, unstaged, untracked) to remote. Use when you need a quick push of everything at once.
Generates .NET Clean Architecture backend structure from entity definitions. Use when bootstrapping .NET backend projects.
Sets up Docker, CI/CD, and environment configuration with auto-detection. Use when adding DevOps infrastructure to a project.
Creates task management docs (kanban board, workflow rules) with Linear integration. Use when setting up task tracking for a project.
Launches RFC and debate discussions on GitHub. Use when proposing changes that need community input or voting.
Creates design_guidelines.md with WCAG 2.1 compliance and design system docs. Use when project has a frontend.
Scaffolds new or restructures existing projects to Clean Architecture. Use when setting up project structure.
Scans codebase for hardcoded secrets with severity classification and remediation guidance. Use when auditing a project for leaked credentials.
Sets up logging, error handling, CORS, health checks, and API docs. Use when adding cross-cutting concerns to backend projects.
Configures environment variables and secrets protection. Use when setting up .env files and gitignore rules for a project.
Configures health check endpoints for Kubernetes readiness/liveness/startup probes. Use when deploying to Kubernetes.
Configures global exception handling middleware. Use when adding centralized error handling to .NET or Python backends.
Configures structured JSON logging with Serilog (.NET) or structlog (Python). Use when adding logging to backend projects.
Creates infrastructure.md and runbook.md (Docker-conditional). Use for DevOps documentation in any project.
Sets up linters, pre-commit hooks, and test infrastructure. Use when adding code quality tooling to a project.
Generates GitHub Actions CI workflow configuration. Use when adding continuous integration to a project.
Generates Dockerfile and docker-compose configuration for multi-container development. Use when containerizing a project.
Removes platform-specific artifacts from Replit, StackBlitz, CodeSandbox, Glitch. Use when preparing exported projects for production.
Scaffolds new React projects or restructures monoliths to component-based architecture. Use when setting up frontend structure.
Creates test documentation (testing-strategy.md, tests/README.md) with Risk-Based Testing philosophy. Use when setting up test strategy for a project.
Composes and publishes announcements to GitHub Discussions. Use when sharing releases, updates, or news with the community.
Responds to unanswered GitHub discussions and issues with codebase-informed replies. Use when clearing community question backlog.
Produces prioritized triage report from open GitHub issues, PRs, and discussions. Use when reviewing community backlog.
Analyzes community health and delegates engagement tasks. Use when managing GitHub issues, discussions, and announcements.
Verifies bootstrapped projects via build, test, and container health checks. Use when validating project setup completeness.
Configures Swagger/OpenAPI documentation for backend APIs. Use when adding interactive API docs to a project.
Configures CORS policy for development and production environments. Use when setting up cross-origin access for APIs.
Generates seed data from ORM schemas or entity definitions to any target format. Use when populating databases for development.
Sets up security scanning for secrets and dependency vulnerabilities. Use when adding security infrastructure to a project.