메뉴
Use when Codex needs to extract testable API behavior from epics, user stories, acceptance criteria, tickets, markdown docs, or other prose requirements before generating Rest Assured scenarios.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Use when Codex needs to design, implement, run, document, or report Rest Assured API tests for REST services, contract-driven service tests, JUnit 5 automation, CI pipelines, or test-management integrations.
Use when Codex needs to derive Rest Assured test scenarios from OpenAPI or Swagger contracts, including endpoints, methods, schemas, auth rules, status codes, and error conditions.
Use when Codex needs to derive service-test scenarios from WSDL or SOAP contracts and translate them into HTTP and XML checks that can still be implemented with Rest Assured where appropriate.
Use when Codex needs to scaffold, retrofit, or normalize a Java Rest Assured test module with JUnit 5, Maven or Gradle, shared specifications, and an initial runnable smoke test.
Use when Codex needs to configure or troubleshoot Rest Assured API tests in CI pipelines, including JUnit 5 execution, tags, Docker, containers, artifacts, quality gates, and provider-specific pipeline examples.
Use when Codex needs to implement, refactor, debug, or extend Rest Assured API tests with JUnit 5, reusable request and response specifications, authentication helpers, DTOs, contract checks, and service-test best practices.
| name | restassured-analysis-requirements |
| description | Use when Codex needs to extract testable API behavior from epics, user stories, acceptance criteria, tickets, markdown docs, or other prose requirements before generating Rest Assured scenarios. |
| metadata | {"author":"jovd83","version":"1.0","dispatcher-category":"testing","dispatcher-capabilities":"requirements-analysis, api-requirements-analysis, restassured-requirements-analysis","dispatcher-accepted-intents":"analyze_api_requirements, derive_api_testable_behaviors","dispatcher-input-artifacts":"requirements, user_story, acceptance_criteria, ticket, markdown_docs, repo_context","dispatcher-output-artifacts":"analysis_baseline, requirement_summary, open_questions, routing_request","dispatcher-stack-tags":"restassured, analysis, api-testing","dispatcher-risk":"low","dispatcher-writes-files":false} |
Derive tests from these checkout user stories.
Output: A grouped list of API behaviors, validations, permissions, and edge cases tied back to story IDs.Use dispatcher intent plan_api_test_coverage when the next step is scenario planning.
If dispatcher routing is unavailable, hand off to ../coverage_plan/generation/SKILL.md.