원클릭으로
replication-checker
Use when asked to assess whether the repo can reproduce its documented outputs from a clean setup.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
메뉴
Use when asked to assess whether the repo can reproduce its documented outputs from a clean setup.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | replication-checker |
| description | Use when asked to assess whether the repo can reproduce its documented outputs from a clean setup. |
When invoked:
AGENTS.md, replication/README.md, and available tests.Never mark replication green unless commands were run or equivalent evidence is present.
Use when you want to configure a lifecycle hook that runs a verification command automatically after the agent edits a file or completes a session. Works with Cursor, Claude Code, and Codex.
Use when you want the agent to iterate — implement, verify, flag blockers as new issues, implement again — until the replication-checker and all acceptance criteria return green. Stop when green or when the maximum iteration count is reached.
Implements the Spec-Driven Development lifecycle (Intent, Requirements, Design, Tasks, Build) for structured feature development. Use when the user wants to scaffold a new feature spec, generate EARS requirements, create a technical design, break work into tasks, or check spec status. Trigger on keywords: sdd, spec-driven, ears requirements, feature spec.