Skip to content

refactor(gem-browser-tester): restructure agent with detailed workflo…#820

Draft
mubaidr wants to merge 1 commit intogithub:stagedfrom
mubaidr:steamline
Draft

refactor(gem-browser-tester): restructure agent with detailed workflo…#820
mubaidr wants to merge 1 commit intogithub:stagedfrom
mubaidr:steamline

Conversation

@mubaidr
Copy link
Contributor

@mubaidr mubaidr commented Feb 25, 2026

Pull Request Checklist

  • I have read and followed the CONTRIBUTING.md guidelines.
  • My contribution adds a new instruction, prompt, agent, skill, or workflow file in the correct directory.
  • The file follows the required naming convention.
  • The content is clearly structured and follows the example format.
  • I have tested my instructions, prompt, agent, skill, or workflow with GitHub Copilot.
  • I have run npm start and verified that README.md is up to date.

Description

Overhauled the browser tester agent specification with a comprehensive, step-by-step workflow and explicit input/output contracts. Key changes:

  • Removed mission statement and refined expertise scope
  • Replaced high-level workflow with detailed procedural steps:
    • Explicit initialization, execution, verification, failure handling, reflection, and cleanup phases
    • Mandated accessibility snapshots over visual screenshots for reliable element identification
    • Defined structured evidence collection in docs/plan/{plan_id}/evidence/{task_id}/
  • Added JSON input format guide defining task_id, plan_id, plan_path, and task_definition
  • Added JSON output format guide with standardized status, summary, and failure details

This refactor makes agent behavior predictable, ensures consistent evidence collection, and enables reliable integration with downstream systems through well-defined I/O schemas.


Type of Contribution

  • New instruction file.
  • New prompt file.
  • New agent file.
  • New plugin.
  • New skill file.
  • New agentic workflow.
  • Update to existing instruction, prompt, agent, plugin, skill, or workflow.
  • Other (please specify):

Additional Notes


By submitting this pull request, I confirm that my contribution abides by the Code of Conduct and will be licensed under the MIT License.

…w and I/O formats

Overhauled the browser tester agent specification with a comprehensive, step-by-step workflow and explicit input/output contracts. Key changes:

- Removed mission statement and refined expertise scope
- Replaced high-level workflow with detailed procedural steps:
  * Explicit initialization, execution, verification, failure handling, reflection, and cleanup phases
  * Mandated accessibility snapshots over visual screenshots for reliable element identification
  * Defined structured evidence collection in docs/plan/{plan_id}/evidence/{task_id}/
- Added JSON input format guide defining task_id, plan_id, plan_path, and task_definition
- Added JSON output format guide with standardized status, summary, and failure details

This refactor makes agent behavior predictable, ensures consistent evidence collection, and enables reliable integration with downstream systems through well-defined I/O schemas.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant