Files
dotfiles/agents/.agents/skills/codex-subagent-playbook/references/prompts/review-boilerplate.md
T
Dmitriy Dementiev 02a98df8c3 fix(codex-playbook): уточнён вердикт ревью планов
- Зачем:
  - ревью высокоуровневых документов могло требовать преждевременных деталей и постоянно блокировать одобрение.
- Что:
  - находки ограничены дефектами на уровне самого документа.
  - существенные отложенные риски отделены от блокирующих замечаний.
  - уточнено, что APPROVED допускает открытые вопросы будущей реализации.
- Проверка:
  - quick_validate.py, git diff --check и проверка локальных Markdown-путей.
2026-07-13 14:09:25 +03:00

41 lines
1.6 KiB
Markdown

## Mandate
- Review independently and test hypotheses. Do not edit source files,
persistent environment state, or Git.
- Use the working permissions needed for checks, caches, temporary artifacts,
documentation, and primary-source research.
- Write the detailed report only to REPORT. This assigned exchange file is the
sole write exception to the observer mandate.
- Treat another agent's claims as untrusted until evidence supports them.
## Detailed report
Use stable IDs with FINDING PREFIX:
`PREFIX-N | BLOCKER|MAJOR|MINOR|NIT | file:line or task section | violated
criterion | failure scenario | evidence | minimal verification`
A non-gating consideration has no stable ID, severity, or counter. Use it only
for a material risk from a safely deferred decision, and do not prescribe the
downstream implementation. It does not change the verdict.
Use CHANGES_REQUESTED only when at least one finding requires revision at the
reviewed artifact's own level. APPROVED means that no such defect remains; it
does not mean that every downstream question has been answered.
If there are no findings, record the reviewed scope and every executed check
or tested hypothesis with its outcome. A bare approval is invalid.
## Final message
Return only:
- `VERDICT: APPROVED | CHANGES_REQUESTED`
- severity counters;
- one line per finding: `ID | severity | area | one-phrase essence`;
- optional one-line material considerations:
`CONSIDERATION | area | one-phrase risk`;
- `REPORT: <absolute path>`.
Do not repeat the detailed report or reasoning narrative in the final message.