- 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.
- Introduced new agents: gem-chrome-tester, gem-devops, gem-documentation-writer, gem-implementer, gem-orchestrator, gem-planner, gem-researcher, and gem-reviewer.
- Updated README.collections.md to include the new Gem Team Multi-Agent Orchestration collection.
- Created gem-team.collection.yml and gem-team.md for structured documentation of the multi-agent orchestration framework.
- Each agent includes detailed descriptions, workflows, operating rules, and final anchors for clarity on their functionalities and usage.
