levnikolaevich

Use when an evaluation coordinator needs normalized findings from target artifacts and research evidence.

Use when auditing the test surface through the evaluation platform with mandatory research, coordinated test audit workers, and structured summaries.

Coordinates project documentation creation with single context gathering and project type detection. Use when generating project docs subset.

Sets up Docker, CI/CD, and environment configuration with auto-detection. Use when adding DevOps infrastructure to a project.

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.

Builds and queries code knowledge graph for dependency analysis, references, implementations, and architecture overview. Use when starting work on unfamiliar codebase or before refactoring.

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.

Builds all detected projects and verifies successful compilation. Use when checking that a bootstrapped project compiles.

Use when removing Claude-side hex-line integration surfaces such as MCP registration, permissions, hooks, and output style.

Creates test documentation (testing-strategy.md, tests/README.md) with Risk-Based Testing philosophy. Use when setting up test strategy for a project.

Configures Husky, lint-staged, commitlint, and Python pre-commit hooks. Use when adding Git hook automation to a project.