baton-implement
Design or implement one eligible Baton slice attempt without crossing review boundaries.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Design or implement one eligible Baton slice attempt without crossing review boundaries.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Return the Captain decision over one exact Baton plan revision, slice, and design attempt.
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.
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.
| name | baton-implement |
| description | Design or implement one eligible Baton slice attempt without crossing review boundaries. |
Treat the free-form invocation text as the operation inputs. Resolve the Baton package root from the current Git project .claude/baton install when present and valid; otherwise use the configured Claude user directory baton install. Read package-relative files from that root.
Design or implement one eligible slice without crossing the Captain or Verifier boundary.
Work only inside the approved slice and current attempt. Implementation
requires an applicable PROCEED bound to this plan revision, slice, and design
attempt. A REVISE adds a design attempt; a FAIL adds an implementation
attempt. Neither replaces the slice.
PROCEED, build only the approved product scope.For design, return the plan revision, slice, design attempt, TL;DR, exact
binding, and Captain handoff. For implementation, return the implementation
attempt, candidate and product identities, check results, evidence references,
deviations, and Verifier handoff. Do not write protocol receipts or claim
PASS.
Stop on missing approval, ambiguous eligibility, unmet dependencies, changed
consumed inputs, missing PROCEED, scope escape, failed required checks, or an
ambiguous candidate. Report operational failure without inventing a Baton
outcome.
Send a design to baton-design-review; send an implemented candidate and
evidence to a fresh baton-verify.