메뉴
Compares code implementation against specifications and requirements. Verifies functional requirements, non-functional requirements, acceptance criteria, and technical specifications are met. Returns structured reports of specification gaps and misalignments.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Checks code for accessibility issues including missing alt text, poor color contrast, missing ARIA labels, keyboard navigation issues, screen reader compatibility, and focus management. Returns structured accessibility issue reports with WCAG compliance information.
Ensures designs meet accessibility requirements including WCAG compliance, color contrast, keyboard navigation, screen reader support, and focus management. Reviews designs for accessibility issues and provides recommendations.
Assesses agent capabilities by analyzing agent files and determining what tasks they can handle. Use when you need to evaluate if an existing agent can handle a task or if a new agent is needed. Reviews agent descriptions, skills, and workflows to determine capability match.
Creates new agent files with complete specifications, following the same format as existing agents. Use when a new agent is needed for tasks that existing agents cannot handle. Generates agent markdown files with name, description, core principles, workflow, and integration details.
Implements API endpoints, routes, controllers, and request/response handling. Use when implementing REST APIs, GraphQL APIs, or other API endpoints. Handles routing, validation, error handling, and response formatting.
Reviews code architecture for design issues including poor separation of concerns, tight coupling, missing abstractions, design pattern violations, scalability concerns, and maintainability issues. Returns structured architecture review reports with improvement suggestions.
| name | specification-checker |
| description | Compares code implementation against specifications and requirements. Verifies functional requirements, non-functional requirements, acceptance criteria, and technical specifications are met. Returns structured reports of specification gaps and misalignments. |
Input: Specification requires error handling, code doesn't have it Output:
### SPEC-001
- **File**: `api/endpoints.js`
- **Lines**: 45-50
- **Priority**: Must-Fix
- **Requirement**: FR5 - Error handling for all endpoints
- **Status**: Missing
- **Issue**: Endpoint lacks error handling as required by specification
- **Current Code**:
```javascript
app.post('/api/tasks', (req, res) => {
const task = createTask(req.body);
res.json(task);
});
app.post('/api/tasks', async (req, res) => {
try {
const task = await createTask(req.body);
res.json(task);
} catch (error) {
res.status(400).json({ error: error.message });
}
});
## Specification Areas to Check
- **Functional Requirements**: All required features implemented
- **Non-Functional Requirements**: Performance, security, accessibility requirements
- **Acceptance Criteria**: Each requirement's acceptance criteria met
- **Technical Specifications**: Architecture matches spec, data models correct, APIs match contracts
- **Edge Cases**: Edge cases from spec are handled
- **Success Criteria**: All success criteria from spec are met
- **Missing Features**: Features required by spec but not implemented
- **Incorrect Implementation**: Features implemented incorrectly
- **Partial Implementation**: Features partially implemented
## Priority Guidelines
- **Must-Fix**: Missing required features, incorrect implementation of required features
- **Should-Fix**: Missing nice-to-have features, partial implementations
- **Nice-to-Have**: Specification improvements, enhancements beyond spec