jovd83 Analyze Requirements
1. Find Sources
- Search the repo for stories, epics, acceptance criteria, ADRs, specs, and tickets.
- Read the user-provided requirement source completely.
- Extract only behavior that affects API requests, responses, authorization, validation, workflow state, integrations, or observability.
2. Normalize The Requirements
- Convert prose into testable behaviors.
- Separate happy path, validation, authorization, negative, and workflow behaviors.
- Mark missing details explicitly instead of inventing them.
3. Validate With The User
- Present the summarized behaviors.
- Ask the user to confirm that the requirement summary is complete.
- Stop before coverage generation when the summary is not approved.
4. Output Shape
- Group the output by feature or endpoint area.
- Include the source identifier for each behavior when available.
- Highlight gaps that must be resolved by contract analysis or user clarification.
5. Examples
- 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
- Problem: The requirements mention UI behavior only. Fix: Extract only the backend behavior that the API must enforce or expose.
- 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.