Menu
Improve readiness criterion C5.3 (Integration and E2E Coverage) in the current project by adding integration or E2E test infrastructure. Raises the fulfillment level by one step.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Assess the Agent Readiness level of the current project across all 11 criteria (C1.1–C8.2) and produce a structured report with the achieved level, per-criterion scores, gaps, and recommendations.
Verify readiness criterion C1.1 (Codebase Accessibility) in the current project. Reports fulfillment level 0–2.
Verify readiness criterion C2.1 (Setup Automation) in the current project. Reports fulfillment level 0–3.
Verify readiness criterion C3.1 (Architecture Depth) in the current project. Reports fulfillment level 0–3.
Verify readiness criterion C5.1 (Runnability) in the current project. Reports fulfillment level 0–2.
Verify readiness criterion C5.2 (Unit Test Coverage) in the current project. Reports fulfillment level 0–3.
| name | improve-c5-3 |
| description | Improve readiness criterion C5.3 (Integration and E2E Coverage) in the current project by adding integration or E2E test infrastructure. Raises the fulfillment level by one step. |
| allowed-tools | Bash Read Write Edit |
Examine the project to understand its current state:
Step 1 — Determine current level:
Step 2 — Implement the improvement:
If current level is 0 → raise to 1: Create integration tests covering key service boundaries. Based on the detected project type:
REST API (Express/Fastify/etc.): Create tests/integration/ directory and write integration tests using supertest (Node) or pytest with test client (Python/FastAPI). Test the main endpoints with real HTTP calls. Add supertest to devDependencies if not present.
Example test structure:
tests/integration/
api.test.ts — tests for main API routes
Database-backed service: Write tests that connect to a real (test) database and verify data operations. Use a test database connection string.
Library/module: Write tests that exercise the public API with real dependencies (not mocked) to verify integration points work end-to-end.
Write at minimum 5–10 integration tests covering the most important boundaries.
If current level is 1 → raise to 2: Add E2E test infrastructure. Based on the detected project type:
Web app with UI: Install and configure Playwright (preferred over Cypress for new setups):
@playwright/test to devDependenciesplaywright.config.ts with base URL pointing to localhost and the detected porte2e/ directory with basic tests for the main user flows (login if present, main feature flow, navigation)"test:e2e": "playwright test" to package.json scriptsAPI-only: Extend existing integration tests to cover full request/response cycles including authentication, error handling, and multi-step operations (e.g., create → read → update → delete).
Write at minimum 3–5 E2E scenarios for the most critical user flows.
If current level is 2 → raise to 3: If the project has a UI, add visual regression testing:
@percy/playwright or @storybook/test-runner with Chromatic to devDependencies.env.example)If the project has no UI, report that Level 3 is not applicable (maximum is Level 2 for API-only projects).
If already at level 3 (or at level 2 with no UI): Report the current state and that no improvement is needed.
Step 3 — Report: State what files were created or modified, the before and after level.