- Make browser tester generic to support for chrome devotols mcp, playwright, agentic browser tools.
- Add Team lead and energetci peronsality to Orchestrator
- Add progress updates between phases/ waves
* feat: Prd/ steer support
- Add supprot for PRD
- Vscode steer/ queue support
- Consistent artifacts
- Improved parallel running; for researchers too
* chore: improve prd update support
* chore: Make reviewer use prd for compaince
* chore: imrpvoe websearch in researcher
* fix(gem-team): revert gem-team plugin version from 1.5.0 to 1.2.0
Updated agent guidelines to specify the use of accessibility_snapshot over visual screenshots for element identification. Accessibility snapshots provide structured DOM/ARIA data, which is more reliable for browser automation than pixel-based visual analysis.
- Refined `gem-browser-tester` workflow to separate initialization from
execution and enforce an Observation-First loop.
- Added retry logic for transient failures (e.g., timeouts, network issues)
in browser automation tasks.
- Standardized artifact generation paths to `docs/plan/{plan_id}/`
across multiple agents.
- Updated failure actions to specify evidence capture locations
(logs, network) for improved debugging and traceability.
Introduce explicit sections for input, output, and verification criteria.
Define structured JSON output including detailed evidence paths and error counts.
Update workflow to reference new guides and move Observation-First loop to operating rules.
Clarify verification steps with specific pass/fail conditions for console, network, and accessibility checks.
- Remove redundant `<mission>` section from gem-browser-tester
- Add "Reflect" step to gem-documentation-writer for self-review on high-priority or failed tasks
- Refactor gem-orchestrator completion phase to generate a walkthrough markdown file instead of a review
- Update orchestrator rules to allow direct execution for creating walkthrough files
Remove "detailed thinking on" directive and consolidate operating_rules sections for consistency. Both gem-browser-tester.agent.md and gem-devops.agent.md now share standardized rules: unified tool activation phrasing ("Always activate tools before use"), merged context-efficient reading instructions, and removed agent-specific variations. This simplifies maintenance and ensures consistent behavior across different agent types while preserving core functionality like evidence storage, error handling, and output constraints.
Rename the Chrome-specific testing agent to a browser-agnostic version
to support multiple automation tools (Playwright, Chrome DevTools, etc.).
Updates all references in orchestrator and planner configurations, and
broadens the description and execution workflow to be tool-flexible.
Evidence storage rule clarified to apply primarily on failures.
