playwright-test-agent 0.2.4 → 0.2.5

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "playwright-test-agent",
-  "version": "0.2.4",
+  "version": "0.2.5",
   "description": "Initialize Playwright Test agents with a Playwright CLI-first browser workflow.",
   "type": "module",
   "bin": {

package/playwright-test-agent/SKILL.md

@@ -5,7 +5,7 @@ description: Use first when a user asks to investigate or test a website, browse
 
 # Playwright Test Agent
 
-Use Planner -> Generator -> execute -> Healer (only on failure) for durable tests. Follow the platform routing defined by the project's `AGENTS.md` or `CLAUDE.md`. Each role owns its assigned browser interaction and artifacts; the orchestrating agent performs the documented handoffs and required test-suite execution.
+Use Planner -> Generator -> execute -> Healer (only on failure) for durable tests. Follow the platform routing defined by the project's `AGENTS.md` or `CLAUDE.md`. Planner, Generator, and Healer must run as their configured role agents; the orchestrating agent performs only the documented preparation, handoffs, user confirmation, and required test-suite execution.
 
 ## Required phase handoff
 
@@ -61,4 +61,4 @@ Run from the target project:
 npx playwright-test-agent init
 ```
 
-The command globally installs `@playwright/cli`, installs the Playwright CLI skills and browser, initializes Playwright Test agents, and reinjects CLI-first instructions into all generated role definitions. Run it again after Playwright updates regenerate those definitions. Restart the host agent after initialization so global skills and changed definitions are reloaded.
+The command globally installs `@playwright/cli`, installs the Playwright CLI skills and browser, initializes Playwright Test agents, configures Codex and Claude Code to dispatch the three generated role agents, and reinjects CLI-first instructions into all generated role definitions. Run it again after Playwright updates regenerate those definitions. Restart the host agent after initialization so global skills and changed definitions are reloaded.

package/playwright-test-agent/scripts/init-playwright.mjs

@@ -26,14 +26,14 @@ const CODEX_INSTRUCTIONS = `${BLOCK_START}
 Codex routing is mandatory for website, browser workflow, HTTP API, or application-feature testing:
 
 1. Load \`.agents/skills/playwright-test-agent/SKILL.md\`.
-2. Before Planner, the main agent may read relevant local project information and ask for information that materially affects the test, such as the deployed URL, account or role, expected behavior, environment, and authorization boundary. Do not perform a seed/config/generated-file audit or open the website during preparation.
-3. Use the Codex routing configured for this project. Do not create nested or same-role Playwright agents. If the configured Codex route assigns phases to the main session, that is a Codex-specific compatibility route; explicitly mark each phase and follow its role definition.
-4. Planner's first live browser action is \`playwright-cli open <url>\`. Prefer CLI while preserving the generated Playwright Test MCP configuration and tools. Do not call Chrome DevTools or an unrelated browser integration.
-5. Planner must convert its investigation into a complete Markdown test plan under \`specs/\`. Show that saved plan to the user and wait for explicit confirmation; investigation alone is not completion.
-6. After confirmation, the configured Generator role must generate executable Playwright test code for the confirmed plan. When generation finishes, execute the generated tests with \`npx playwright test\`; generating files alone is not completion.
-7. If every generated test passes, report the result. If any generated test fails, invoke the configured Healer role with the failed test names and output; diagnose, patch, and rerun until the tests pass or a genuine application/environment/product blocker is identified. Never skip execution and never report generated-but-unexecuted tests as passing.
+2. Before starting Planner, the main agent may read relevant local project information and ask for information that materially affects the test, such as the deployed URL, account or role, expected behavior, environment, and authorization boundary. Do not perform a seed/config/generated-file audit or open the website during preparation.
+3. Once the required context is available, directly start a subagent with \`agent_type: "playwright_test_planner"\`, passing the objective, deployed URL, supplied access information, relevant project context, and constraints. The main agent must not perform Planner work, open or inspect the website, or call \`playwright-cli\`, browser MCP tools, Chrome DevTools, or another browser integration.
+4. Planner opens and investigates the website with \`playwright-cli\`, converts its findings into a complete Markdown test plan under \`specs/\`, and returns the saved plan path. After Planner returns, show that plan to the user and wait for explicit confirmation; investigation alone is not completion.
+5. Only after confirmation, directly start a subagent with \`agent_type: "playwright_test_generator"\`, passing the confirmed plan. Generator validates the confirmed scenarios with \`playwright-cli\`, writes executable Playwright test files, and returns their paths.
+6. After Generator returns, the main agent must execute the generated tests with \`npx playwright test\`. Generating test files alone never completes the workflow.
+7. If every generated test passes, report the result. If any generated test fails, directly start a subagent with \`agent_type: "playwright_test_healer"\`, passing the failed test names, failure output, confirmed plan, and generated file paths. Healer diagnoses and patches justified test defects and reruns the affected tests until they pass or it identifies a genuine application/environment/product blocker. Never report generated-but-unexecuted tests as passing.
 
-Ask only for information that is necessary or could materially change scope, assertions, access, or safety. Do not guess or create nested agents.
+Start each role as its configured subagent and never make the main agent perform that role. Do not create a nested or same-role intermediary. Do not locate a seed file or make setup-file discovery a prerequisite to Planner. If exploration finds missing, incorrect, or contradictory required information, let Planner pause and return the precise question; after the user answers, resume the same Planner subagent when possible, or restart it with that answer and the blocking observation. Ask only for information that is necessary or could materially change scope, assertions, access, or safety. Do not guess.
 
 ${BLOCK_END}`;