メニュー
Analyzes ideas and extracts functional and non-functional requirements. Use when breaking down concepts into specific, measurable requirements. Identifies what needs to be built, constraints, and success criteria.
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 | requirement-analyzer |
| description | Analyzes ideas and extracts functional and non-functional requirements. Use when breaking down concepts into specific, measurable requirements. Identifies what needs to be built, constraints, and success criteria. |
Input: "I want a user authentication system" Output:
## Functional Requirements
### Must-Have
- FR1: Users can register with email and password
- Acceptance: User can create account, receives confirmation email
- FR2: Users can log in with email/password
- Acceptance: Valid credentials grant access, invalid credentials show error
- FR3: Users can reset forgotten passwords
- Acceptance: Password reset link sent via email, user can set new password
### Should-Have
- FR4: Users can log in with OAuth providers (Google, GitHub)
- Acceptance: User can authenticate via OAuth, account linked to email
## Non-Functional Requirements
- NFR1: Authentication must complete in < 2 seconds
- NFR2: Passwords must be hashed using bcrypt (minimum 10 rounds)
- NFR3: System must support 10,000 concurrent users
- NFR4: All authentication endpoints must use HTTPS
## Constraints
- Must use existing database infrastructure
- Must comply with GDPR for user data
- Must integrate with existing email service
## Dependencies
- User database schema
- Email service API
- Session management system
Input: "Build a task management API" Output:
## Functional Requirements
### Must-Have
- FR1: Create, read, update, delete tasks
- FR2: Assign tasks to users
- FR3: Set task priorities and due dates
- FR4: Filter and search tasks
### Should-Have
- FR5: Task comments and attachments
- FR6: Task status workflow (todo, in-progress, done)
## Non-Functional Requirements
- NFR1: API response time < 200ms for 95% of requests
- NFR2: Support pagination for large result sets
- NFR3: RESTful API design following OpenAPI 3.0
## Constraints
- Must use PostgreSQL database
- Must support authentication via JWT tokens