메뉴
Trigger only when the user explicitly requests test-driven implementation or when an assigned task requires adding behavior by first writing a failing test, then minimal code, then refactoring without behavior change.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
| name | tdd |
| description | Trigger only when the user explicitly requests test-driven implementation or when an assigned task requires adding behavior by first writing a failing test, then minimal code, then refactoring without behavior change. |
| requires | [] |
Use this skill only when the task requires a Test-Driven Development loop:
Do not use this skill for pure verification, code review, debugging without a target behavior, or implementation where tests are intentionally out of scope.
Define:
status: red | green | refactored | blocked
behavior: string
filesModified: string[]
red:
testWritten: boolean
command: string
failedForExpectedReason: boolean
evidence: string
green:
implementationChanged: boolean
command: string
passed: boolean
evidence: string
refactor:
performed: boolean
command: string
passed: boolean
summary: string
blockedReason: string | null
nextAction: none | fix-red | implement-green | refactor | ask-user
Trigger only when an already-approved PLAN.md or equivalent structured plan must be executed through wave-ordered tasks, isolated git worktrees, wave-level verification, final integration, and controlled merge handling; never create the plan or execute unapproved work.
Trigger only to inspect an existing diff, commit, branch, or PR for correctness, regression, security, performance, and maintainability issues; do not use to implement changes or run acceptance verification.
Trigger only when an observed failure, reproducible bug, regression, stack trace, failing test, or merge conflict requires evidence-based root-cause diagnosis before applying or recommending a fix.
Trigger only when a coding task requires a written implementation plan before execution, especially multi-file or multi-step work needing dependency analysis, wave classification, and file-isolation-safe task partitioning; dispatches Planner to write a timestamped plan under ~/.yi-workflow/docs/plans/ and performs no implementation.
Trigger only after an implementation exists and must be validated against an explicit plan, acceptance criteria, or expected behavior by running relevant checks and reporting evidence-backed pass/fail results.