Collaborative task design

Convert a PRD into sequenced engineering tasks using real multi-model review, spec driven development, domain driven design, clean architecture, and test driven development.

Shared scaffolding (inputs, routing and configurability, local panel runner and flags, native response helper, panel status taxonomy, completion gate) lives in ../_shared/collaborative-panel-runner.md. Read it before running any panel phase. This file keeps only what is specific to task design.

Roles

Task design uses the role names synthesis_anchor, adversarial_anchor, architecture, testing, interface, backend, and delivery. The mapping to models is editable in assets/routing.toml.

Phases

Run the configured panel phases in order: architecture_mapping, test_strategy, task_slicing, dependency_review, and convergence. Artifacts and prompts live under .codex_workflow/task_design.

Workflow

Use this skill to convert specification into executable engineering work. The output is not a PRD and not a patch. It is the bridge between product intent and implementation. Every task must trace back to a spec item and must define tests before code.

Read references/engineering_rules.md before running architecture_mapping and task_slicing; it holds the spec driven development, domain driven design, clean architecture, and test driven development rules this skill applies.