메뉴
Use this skill to verify work matches requirements. Activates when checking against specifications, validating acceptance criteria, or ensuring implementation matches design.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
WHEN to auto-invoke: Creating API routes, building endpoints, adding route.ts files, implementing REST/GraphQL APIs, adding authentication to APIs, rate limiting, API validation with Zod, handling HTTP methods (GET/POST/PUT/DELETE). WHEN NOT to invoke: Pure frontend work, styling, React components without API calls, documentation-only tasks, database migrations without API changes.
WHEN to auto-invoke: Code review requests, refactoring code, cleaning up code, performance optimization, security audits, linting issues, reducing technical debt. WHEN NOT to invoke: Building new features (use domain-specific skills), initial implementation, documentation-only work.
WHEN to auto-invoke: End of productive sessions, after solving difficult problems, after user corrections, after discovering effective workarounds, after establishing project conventions. WHEN NOT to invoke: Trivial sessions, sessions with only exploration, when explicitly told not to learn.
WHEN to auto-invoke: Database schema design, creating migrations, writing SQL queries, query optimization, Supabase operations, Prisma/Drizzle schema changes, PostgreSQL tasks, RLS policies, indexes. WHEN NOT to invoke: Pure frontend work, API logic without database, styling, React components, deployment tasks.
WHEN to auto-invoke: Creating CI/CD pipelines, GitHub Actions workflows, Docker/containerization, Vercel/Netlify deployment, infrastructure as code, environment variables, deployment configurations. WHEN NOT to invoke: Application code changes, UI development, database schema design, testing application logic.
WHEN to auto-invoke: Measuring code quality, testing AI outputs, establishing success criteria, defining acceptance tests, checking implementation correctness. WHEN NOT to invoke: Simple implementations, prototyping, exploration phases, when speed matters more than measurement.
| name | spec-compliance |
| description | Use this skill to verify work matches requirements. Activates when checking against specifications, validating acceptance criteria, or ensuring implementation matches design. |
Verify that implementation matches specifications and requirements.
Build what was asked, not what you think should be built.
The spec is the contract. Deviation without approval is a bug, not a feature.
## Original Specification
Source: [PRD / Issue / Design Doc / User Story]
### Requirements
1. [Requirement 1]
2. [Requirement 2]
3. [Requirement 3]
### Acceptance Criteria
- [ ] Criterion 1
- [ ] Criterion 2
- [ ] Criterion 3
### Out of Scope
- Item 1
- Item 2
## Implementation Mapping
| Requirement | Implementation | Status |
|-------------|----------------|--------|
| Req 1 | `src/feature.ts:23` | ✅ Met |
| Req 2 | `src/feature.ts:45` | ✅ Met |
| Req 3 | Not implemented | ❌ Gap |
## Acceptance Criteria Verification
### Criterion 1: "User can log in with email"
- **Verification method**: Manual test
- **Steps taken**:
1. Navigated to /login
2. Entered email and password
3. Clicked submit
- **Result**: ✅ Successfully logged in
- **Evidence**: [screenshot/log]
### Criterion 2: "Error shown for invalid credentials"
- **Verification method**: Manual test
- **Steps taken**:
1. Entered wrong password
2. Clicked submit
- **Result**: ✅ Error message displayed
- **Evidence**: Shows "Invalid credentials"
## Compliance Report
**Overall Status**: ✅ Compliant / ⚠️ Partial / ❌ Non-compliant
### Summary
- Requirements met: 8/10
- Acceptance criteria passed: 5/5
- Gaps identified: 2
### Gaps
1. **Requirement 9**: Password reset flow
- Status: Not implemented
- Reason: Deferred to phase 2
- Tracking: ISSUE-456
2. **Requirement 10**: Remember me checkbox
- Status: Partial
- Gap: Cookie not persisting
- Action needed: Fix cookie setting
### Additions (not in spec)
1. Added loading spinner
- Rationale: UX improvement
- Risk: None, additive only
As a [user type]
I want to [action]
So that [benefit]
Acceptance Criteria:
- Given [context]
- When [action]
- Then [result]
## Feature: [Name]
### Overview
### Requirements
### Success Metrics
### Out of Scope
## Design: [Component]
### API Contract
### Data Model
### Behavior Specification
## Issue #123
### Description
### Acceptance Criteria
### Technical Notes
## Deviation Record
**Requirement**: [Original requirement]
**Deviation**: [What was done differently]
**Rationale**: [Why the change]
**Approval**: [Who approved, when]
**Impact**: [Effect on other requirements]
## Gap Identified
**Requirement**: [Missed requirement]
**Discovery**: [How/when found]
**Severity**: Critical / High / Medium / Low
**Action**:
- [ ] Implement now
- [x] Defer to next phase
- [ ] Descope (with approval)
**Tracking**: [Issue number]
## Pre-Completion Compliance Check
### Requirements
- [ ] All requirements traced to implementation
- [ ] Each requirement verified working
- [ ] Gaps documented and tracked
### Acceptance Criteria
- [ ] All criteria testable
- [ ] All criteria tested
- [ ] All criteria passing
### Scope
- [ ] No unplanned additions (or documented)
- [ ] Nothing removed without approval
- [ ] Deferred items tracked
### Documentation
- [ ] Spec updated if changes approved
- [ ] Deviations documented
- [ ] Compliance report generated
Works with:
/riper - Research phase loads spec, Review phase checks compliance/execute-plan - Each task maps to spec requirement/review - Final compliance verificationverification-first skill - Verify against spec, not assumptions