菜单
Guide for writing evidence packages for the consensus-loop watch file. Use when preparing code review submissions, structuring feedback evidence, or addressing audit rejections.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | consensus-loop:guide |
| description | Guide for writing evidence packages for the consensus-loop watch file. Use when preparing code review submissions, structuring feedback evidence, or addressing audit rejections. |
| version | 1.0.0 |
When submitting code changes for consensus review, write a properly structured evidence package in the watch file.
Read ${CLAUDE_PLUGIN_ROOT}/config.json first:
consensus.watch_file → submission pathconsensus.trigger_tag / agree_tag / pending_tag → actual tag valuesplugin.respond_file → auditor verdict fileplugin.locale → localeFollow the format defined in ${CLAUDE_PLUGIN_ROOT}/templates/references/${locale}/evidence-format.md.
Required sections: Claim, Changed Files, Test Command, Test Result, Residual Risk.
Key rules:
[trigger_tag] → auditor reviews → [agree_tag] or [pending_tag]
↓
Fix issues, re-submit with [trigger_tag]
When auditor returns [pending_tag]:
test-gap, claim-drift, scope-mismatch)[trigger_tag] to trigger a new audit cycleFull rejection code reference: ${CLAUDE_PLUGIN_ROOT}/templates/references/${locale}/rejection-codes.md
Design tasks into tracks with work breakdowns and execution order. Also writes and maintains PRDs (Product Requirements Documents) — when a user requests a feature, analyzes it, adds it to the PRD, then decomposes into work breakdowns. Use for new feature planning, PRD writing, architecture changes, multi-track decomposition, requirements analysis, or adjusting existing execution plans. Trigger when user says things like 'add feature X', 'I need Y', 'plan Z', or describes any product requirement.
Run all done-criteria checks (CQ/T/CC/CL/S/I/FV/CV) and produce a pass/fail verification report. Use after implementing code, before submitting evidence to the quorum audit.
Run a consensus-loop audit manually — Codex reviews pending trigger_tag items in the watch file. Use when you want to trigger an audit without editing the watch file, re-run a failed audit, or test the audit prompt.
Squash-merge a worktree branch into the target branch with a structured commit message. Use after audit consensus and retrospective completion.
Session orchestrator for the consensus-loop — reads handoff, picks unblocked tasks, distributes to parallel workers, tracks agent assignments, manages correction cycles via SendMessage. Use when starting a work session with pending tasks, distributing implementation work, or reviewing completed worker output.
Extract learnings from audit history and conversation, manage memories, clean up stale entries. Use after completing a track, during retrospective (③ memory step), at end of session, or anytime the user wants memory maintenance. Triggers on 'what did we learn', 'memory cleanup', 'review learnings', 'retrospective', 'update memories', '회고', '메모리 정리'.