CI/CD
Spec-Verify: Spec-Driven Development & Multi-Layer Verification
Spec-driven development and multi-layer verification pipeline that replaces manual code review. Before writing any code, this skill defines specs with acceptance criteria (AC), then verifies implementation through 4 automated layers: guardrails, BDD tests, scope checking, and independent test generation. Use this skill whenever the user asks to implement a feature, fix a bug, add functionality, refactor code, or make any code change — even if they don't mention specs or verification. Also trigger on: "코드 리뷰", "검증", "스펙", "AC", "수용 기준", "BDD", "가드레일", "merge 전에", "PR 체크", "테스트 먼저", "spec-driven", "리뷰 없이", "자동 검증", "verify", "acceptance criteria", "spec verify", "코드 검증", "구현해줘", "기능 추가", "버그 수정", "리팩토링". This skill should be the default workflow for any implementation task because it ensures code quality through specification, not just code review.