levnikolaevich

Checks dependency health and generic custom utility/integration replacement opportunities. Use when auditing dependency and reuse risk.

Checks evidence-backed duplication, over-abstraction, and unused extensibility. Use when auditing DRY/KISS/YAGNI risk.

Creates backend docs (api_spec.md, database_schema.md). Use when project has backend API or database.

Configures CORS policy for development and production environments. Use when setting up cross-origin access for APIs.

Audits whether test results can be trusted: flakiness, isolation, real external dependencies, time/random/order dependency, and shared state. Use when auditing test trustworthiness.

Orchestrates test planning pipeline: research, manual testing, automated test planning. Use when Story needs comprehensive test coverage planning.

Researches competitive benchmarks and generates optimization hypotheses for identified bottlenecks. Use after profiling.

Creates complete project documentation system (project docs, reference, tasks, tests). Use when bootstrapping docs from scratch or regenerating all.

Use when an evaluation run must merge research, findings, documentation, and repair outputs into one verified result.

Indexes and queries project research graphs backed by hex-research MCP. Use for hypotheses, goals, benchmark runs, evidence depth, derived goal metrics, lineage, generated research maps, and graph audits.

Reviews task implementation for quality, code standards, and test coverage. Use when task is in To Review. Sets task Done or To Rework.

Launches RFC and debate discussions on GitHub. Use when proposing changes that need community input or voting.