dcp-reviewer-init

To bind a reviewer to an active planning round, invoke the skill with the active task_name and a unique suffix. This enforces identity constraints and generates a reviewer file at reviewers/reviewer_<suffix>.md.

Task binding in a live planning round attaches the reviewer to an explicit task context using a task name and suffix. It is needed to enforce scope, accountability, and correct output path alignment.

You set up the output path by providing a unique suffix when initializing the reviewer. The skill automatically enforces the output location to reviewers/reviewer_<suffix>.md for artifact generation.

Specifying a domain is optional when binding a reviewer to a planning round. The required fields are task_name and suffix, while the optional domain field allows you to further enforce scope alignment.

You should initialize the reviewer context at the beginning of every new planning round. This ensures you are correctly bound to the task and domain before reading the current round documentation.

Reviewer initialization enforces identity constraints, including the reviewer role, suffix, filename, and the output path. It ensures structured live review flow by referencing active round artifacts to preserve round integrity.