test-driven-development
Strict RED-GREEN-REFACTOR cycle enforcement. Tests are never skipped or deferred. Run mode only, never watch mode. Exit code evidence mandatory.
소스 정보
- 저장소
- a5c-ai/babysitter
- 최근 소스 활동
- 2026년 6월 1일 07:46
- 감지된 SKILL.md 언어
- 영어
- 스타
- 1,813
- 포크
- 111
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
파일 탐색기
2 개 파일SKILL.md 표시 중
SKILL.md
소스 지침 · 읽기 전용 미리보기- name
- test-driven-development
- description
- Strict RED-GREEN-REFACTOR cycle enforcement. Tests are never skipped or deferred. Run mode only, never watch mode. Exit code evidence mandatory.
- allowed-tools
- Read, Write, Edit, Bash, Grep, Glob
- graph
- {"domains":["domain:software-engineering"],"skillAreas":["skill-area:agentic-loops","skill-area:orchestration-loop"],"workflows":["workflow:feature-development"],"topics":["topic:developer-experience"],"roles":["role:tech-lead","role:backend-engineer"]}
- 2. **GREEN**
- Write minimal code to make test pass. Exit code MUST be 0.
- 3. **REFACTOR**
- Clean up implementation while keeping tests green. Exit code MUST remain 0.
## Non-Negotiable Rules
- Always use run mode (`CI=true npm test` or `--run` flag)
- NEVER use watch mode (prevents hanging processes)
- Use timeout guards (`timeout 60s`) as backup
- Record exit codes as evidence at each phase
- If tests fail 3 consecutive times in GREEN, report failure status
- Never skip RED phase (failing test must exist before implementation)
- Never defer tests to "later" -- TDD means tests first
## Scope Discipline
- If implementation requires >3 file changes, flag for scope review
- Architectural choices require user approval unless pre-approved in plan
- New dependencies require user approval
## When to Use
- Every feature implementation in BUILD workflow
- Every bug fix in DEBUG workflow (regression test)
## Agents Used
- `component-builder` (primary consumer)
- `bug-investigator` (regression tests)
GitHub에서 보기