baton-design-review
Return the Captain decision over one exact Baton plan revision, slice, and design attempt.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Return the Captain decision over one exact Baton plan revision, slice, and design attempt.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Return the Captain decision over one exact Baton plan revision, slice, and design attempt.
Design or implement one eligible Baton slice attempt without crossing review boundaries.
Mechanically compose passed Baton candidates or integrate the exact assembled candidate that passed.
Propose an externally approved Baton plan or forward-only revision with stable slice identities.
Independently verify an exact Baton slice candidate or assembled product from fresh read-only context.
Design or implement one eligible Baton slice attempt without crossing review boundaries.
| name | baton-design-review |
| description | Return the Captain decision over one exact Baton plan revision, slice, and design attempt. |
Treat the free-form invocation text as the operation inputs. Resolve the Baton package root from the current Git project .codex/baton install when present and valid; otherwise use the configured Codex user directory baton install. Read package-relative files from that root.
Make the distinct Captain decision over one exact plan revision, slice, and design attempt before implementation.
Review only the presented design attempt. The Captain must differ from its producer and cannot change approved scope, approve a plan, implement, or issue a delivery verdict.
PROCEED when implementation may begin;REVISE when the same slice needs another design attempt; orESCALATE when an external decision or revised approved plan is needed.Return only the decision, exact bindings, Captain invocation, and concise reason. Do not write the Captain receipt.
Stop without a decision when approval, scope, authority, design identity, or evidence needed for review is ambiguous. An execution or persistence failure is operational and creates no Captain decision.
PROCEED returns to baton-implement; REVISE starts another design attempt
on the same slice; ESCALATE hands to baton-plan.