Quality Gate for Task Master FAQs

Question 1

Does it support monorepos or custom build tools?

Accepted Answer

Yes, it features auto-detection for popular package managers and tools like Turbo, Vitest, Jest, and ESLint, while also supporting custom commands via a configuration file.

Question 2

What is the primary purpose of the Quality Gate skill?

Accepted Answer

It serves as an enforcement engine that prevents tasks from being marked as 'completed' until they pass all required quality checks including linting, type-checking, and unit tests.

Question 3

What happens after all quality checks pass?

Accepted Answer

The skill updates the task status to 'completed', updates the project's state.json, unblocks any dependent tasks, and regenerates your TODOs.md progress report.

Question 4

Can I bypass the requirement for new tests?

Accepted Answer

The test existence check is mandatory for core implementation phases, but it is automatically skipped for documentation and cleanup tasks where new tests may not be applicable.

Question 5

Why does the skill fail if my task complexity is too high?

Accepted Answer

To ensure stability and accuracy, Quality Gate enforces a maximum complexity score of 4, requiring you to decompose large tasks into smaller, atomic units.

Quality Gate for Task Master

Key Features

Use Cases

Quality Gate for Task Master

Key Features

Use Cases