Menu
Join Deep Co-Planning as a reviewer for an active planning run.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
| name | dcp-reviewer-init |
| description | Join Deep Co-Planning as a reviewer for an active planning run. |
| invocation-args | {"task_name":"required","suffix":"required","domain":"optional"} |
Do not start this reviewer role implicitly.
Bind the reviewer run to an explicit task_name and suffix at invocation time.
Add domain when the human or lead assigns one.
.agent/playbooks/deep-co-planning/PLAYBOOK.md.agent/playbooks/deep-co-planning/template/round_template/README.mdKeep these hot-loaded for the duration of the playbook:
.agent/playbooks/deep-co-planning/PLAYBOOK.md.agent/playbooks/deep-co-planning/skills/dcp-reviewer-init/SKILL.mdFor every new round, begin by reading the active round README.md.
Then follow 00_round_context.md for the full round contract and read order.
If this is not the first round, also read the prior round outputs referenced in 10_previous_round_feedback.md.
Before writing feedback, know:
Your output file should be:
reviewers/reviewer_<suffix>.mdDo not edit shared synthesis artifacts.
You are responsible for:
The active round packet is the live source of truth.
Do not infer scope, artifacts, or reviewer target paths from chat if the round artifacts already define them.
Do not replace the active round packet with ad hoc reviewer instructions unless the human explicitly changes the plan.
Say so directly.
Common cases:
These are recommendations to the human, not hard stops.
Close a task cleanly at the end of the standard workflow. Use for summary, promotion decisions, project progress updates, session state updates, and session log updates.
Initialize a dotagent working session from within a runtime. Use as the native runtime entrypoint when the project is already initialized and the agent needs to start from the framework correctly.
Join Deep Code Review as a reviewer for an active review run.
Start Deep Co-Planning as the lead for an active planning run.
Start Deep Code Review as the lead for an active review run.
Review code changes with production-grade rigor. Use for mandatory self-review before presenting implementation as complete, or when the user explicitly asks for a review. Focus on findings first: correctness, regressions, scale, architecture, best practices, extendability, and production readiness.