domain-review-to-task

Domain review automation works by orchestrating parallel reviews across backend modules to produce an executable task queue. It filters issues by phase, checks them against OpenSpec specifications, and generates task files with per-issue metadata like severity and file references.

To generate a READY_FOR_IMPLEMENTATION task queue, provide the backend modules for review. The workflow applies phase-based filtering, performs OpenSpec spec checks, and incorporates user decisions to produce the final executable task list.

Yes, domain review automation integrates OpenSpec spec checks to validate issues before task generation. The workflow enforces these checks during the review process to ensure generated tasks align with project specifications.

The best way to handle parallel code reviews across multiple modules is using an automated workflow that enforces structured feedback. It speeds up the feedback cycle and generates per-module issue logs with statuses, severities, and file references.

A generated task file from a code review includes per-issue metadata such as statuses, severities, and file references. This structured data ensures each item in the READY_FOR_IMPLEMENTATION queue is executable and traceable.