agentsclimarketplace

Requirements

Skill jovd83/restassured-skill/analysis/requirements

Rest Assured skill pack for designing, implementing, documenting, and reporting API tests in Java and CI workflows.

Install
npx -y skills add jovd83/restassured-skill --skill requirements

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

2.5 KB, as published. Nobody here has run it

Analyze Requirements

1. Find Sources

  1. Search the repo for stories, epics, acceptance criteria, ADRs, specs, and tickets.
  2. Read the user-provided requirement source completely.
  3. Extract only behavior that affects API requests, responses, authorization, validation, workflow state, integrations, or observability.

2. Normalize The Requirements

  1. Convert prose into testable behaviors.
  2. Separate happy path, validation, authorization, negative, and workflow behaviors.
  3. Mark missing details explicitly instead of inventing them.

3. Validate With The User

  1. Present the summarized behaviors.
  2. Ask the user to confirm that the requirement summary is complete.
  3. Stop before coverage generation when the summary is not approved.

4. Output Shape

  1. Group the output by feature or endpoint area.
  2. Include the source identifier for each behavior when available.
  3. Highlight gaps that must be resolved by contract analysis or user clarification.

5. Examples

  1. Input: Derive tests from these checkout user stories. Output: A grouped list of API behaviors, validations, permissions, and edge cases tied back to story IDs.

6. Troubleshooting

  1. Problem: The requirements mention UI behavior only. Fix: Extract only the backend behavior that the API must enforce or expose.
  2. Problem: The requirements conflict with the contract. Fix: Surface the mismatch and request clarification before implementation.

7. Handoff

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.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.