메뉴
Use only after the main path exists to choose and implement 1-3 critical-path tests that prove the MVP closes the loop. Not for broad coverage goals, full E2E suites, or testing every edge case.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use only at the end of an exam task to write a short submission-oriented README that tells graders what was built, how to run it, how it was verified, what was intentionally omitted, and what would come next. Not for marketing, changelogs, or long architecture essays.
Use only when the user explicitly asks to write, improve, adapt, or decompose a prompt for another AI tool or IDE. This is an optional sidecar skill for prompt-authoring tasks, not part of the default exam coding path.
Use only after prompt intake to classify the task as gateway/proxy/aggregator/BFF, tool-using assistant, retrieval assistant, or workflow agent, then choose the smallest suitable implementation path. Not for framework comparison or coding.
Use only before implementation to define the minimum contract for an agent project: endpoint or interface, tool contract, input and output shapes, state flow, error handling, and assumptions. Not for abstract architecture design.
Use only when the exam project fails to start, fails a key test, or returns the wrong contract. Prioritize the fastest evidence path to restore the main loop. Not for large refactors or speculative cleanup.
Use only at the start of a timed agent-project exam to shrink the prompt into a 2-hour MVP with explicit scope, non-goals, happy path, file tree, and time budget. Not for implementation details.
| name | minimal-test-gate |
| description | Use only after the main path exists to choose and implement 1-3 critical-path tests that prove the MVP closes the loop. Not for broad coverage goals, full E2E suites, or testing every edge case. |
| origin | ECC-derived |
Primary inherited sources:
legacy/ecc-source/agents/tdd-guide.mdlegacy/ecc-source/skills/tdd-workflow/SKILL.mdlegacy/ecc-source/skills/verification-loop/SKILL.mdlegacy/ecc-source/skills/ai-regression-testing/SKILL.mdlegacy/ecc-source/skills/eval-harness/SKILL.mdlegacy/ecc-source/agents/code-reviewer.mdlegacy/ecc-source/commands/tdd.mdInherited methods:
Use this after the core path is implemented and before final handoff. If you are still before implementation, use it briefly to define the minimum proof target first, then come back after the main path exists.
Pick only the highest-signal cases:
Examples:
Before writing code, define one of these:
If you cannot automate first, still write down the exact proof you will use. Do not start implementation with no test target at all.