Collaborative Delivery

Use this only after an approved task plan exists and a panel audit trail is required. It is intentionally more expensive than the normal implementation path. The panel is mandatory once this skill is chosen.

Read shared/collaborative-panel-runner.md before starting. It defines the panel runner, real-participation rule, status taxonomy, and completion check. assets/routing.toml proposes roles and model defaults. Before any role starts, use the approved routing plan described in shared/references/task-shaped-model-routing.md. Show its exact model, runner, effort, and verification policy to the user. A configured model label is not a serving-model receipt.

Outcome

Deliver one task with a recorded red, green, refactor, review, verification, and handoff trail. A phase is complete only when its required roles have real recorded responses. A generated prompt is not participation.

Workflow

1. Select one task and restate its acceptance contract, expected files, and narrowest verification command.
2. Run the phases in order: task_intake, red, green, refactor, review, verification, and handoff.
3. Every phase includes the synthesis and adversarial anchors. The configured specialist roles add their independent response. Add backend or interface as a phase role only when the current slice touches that surface.
4. In red, add or update the failing test and record the expected failure. In green, make the smallest change that passes it. In refactor, simplify only while tests stay green.
5. In review, inspect correctness, data and security risk, maintainability, and fit with the task. In verification, record commands, results, skipped checks, and reasons.
6. In handoff, record changed files, behavior, evidence, decisions, limitations, and the next task.