You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
V 1.4: Dicuss Phase, Knowledge Sources, Expertise Update and more (#1207)
* feat(orchestrator): add Discuss Phase and PRD creation workflow
- Introduce Discuss Phase for medium/complex objectives, generating context‑aware options and logging architectural decisions
- Add PRD creation step after discussion, storing the PRD in docs/prd.yaml
- Refactor Phase 1 to pass task clarifications to researchers
- Update Phase 2 planning to include multi‑plan selection for complex tasks and verification with gem‑reviewer
- Enhance Phase 3 execution loop with wave integration checks and conflict filtering
* feat(gem-team): bump version to 1.3.3 and refine description with Discuss Phase and PRD compliance verification
* chore(release): bump marketplace version to 1.3.4
- Update `marketplace.json` version from `1.3.3` to `1.3.4`.
- Refine `gem-browser-tester.agent.md`:
- Replace "UUIDs" typo with correct spelling.
- Adjust wording and formatting for clarity.
- Update JSON code fences to use ````jsonc````.
- Modify workflow description to reference `AGENTS.md` when present.
- Refine `gem-devops.agent.md`:
- Align expertise list formatting.
- Standardize tool list syntax with back‑ticks.
- Minor wording improvements.
- Increase retry attempts in `gem-browser-tester.agent.md` from 2 to 3 attempts.
- Minor typographical and formatting corrections across agent documentation.
* refactor: rename prd_path to project_prd_path in agent configurations
- Updated gem-orchestrator.agent.md to use `project_prd_path` instead of `prd_path` in task definitions and delegation logic.
- Updated gem-planner.agent.md to reference `project_prd_path` and clarify PRD reading.
- Updated gem-researcher.agent.md to use `project_prd_path` and adjust PRD consumption logic.
- Applied minor wording improvements and consistency fixes across the orchestrator, planner, and researcher documentation.
* feat(plugin): expand marketplace description, bump version to 1.4.0; revamp gem-browser-tester agent documentation with clearer role, expertise, and workflow specifications.
* chore: remove outdated plugin metadata fields from README.plugins.md and plugin.json
Copy file name to clipboardExpand all lines: .github/plugin/marketplace.json
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -243,8 +243,8 @@
243
243
{
244
244
"name": "gem-team",
245
245
"source": "gem-team",
246
-
"description": "A modularmulti-agent team for complex project execution with Discuss Phase for requirements clarification, PRD creation, DAG-based planning, complexity-aware research, multi-plan selection for critical tasks, wave-based parallel execution, PRD compliance verification, and automated testing.",
247
-
"version": "1.3.4"
246
+
"description": "A modular, high-performance multi-agent orchestration framework for complex project execution, feature implementation, and automated verification.",
"details":"Description of failure with specific errors",
77
112
"scenario":"Scenario name if applicable"
78
113
}
79
-
]
114
+
],
80
115
}
81
116
}
82
117
```
83
118
84
-
</output_format_guide>
85
-
86
-
<constraints>
87
-
- Tool Usage Guidelines:
88
-
- Always activate tools before use
89
-
- Built-in preferred: Use dedicated tools (read_file, create_file, etc.) over terminal commands for better reliability and structured output
90
-
- Batch Tool Calls: Plan parallel execution to minimize latency. Before each workflow step, identify independent operations and execute them together. Prioritize I/O-bound calls (reads, searches) for batching.
91
-
- Lightweight validation: Use get_errors for quick feedback after edits; reserve eslint/typecheck for comprehensive analysis
92
-
- Context-efficient file/tool output reading: prefer semantic search, file outlines, and targeted line-range reads; limit to 200 lines per read
93
-
- Think-Before-Action: Use `<thought>` for multi-step planning/error diagnosis. Omit for routine tasks. Self-correct: "Re-evaluating: [issue]. Revised approach: [plan]". Verify pathing, dependencies, constraints before execution.
- Retry: If verification fails, retry up to 3 times. Log each retry: "Retry N/3 for task_id". After max retries, apply mitigation or escalate.
96
-
- Communication: Output ONLY the requested deliverable. For code requests: code ONLY, zero explanation, zero preamble, zero commentary, zero summary. Output must be raw JSON without markdown formatting (NO ```json).
97
-
- Output: Return raw JSON per output_format_guide only. Never create summary files.
98
-
- Failures: Only write YAML logs on status=failed.
99
-
</constraints>
100
-
101
-
<directives>
102
-
- Execute autonomously. Never pause for confirmation or progress report.
103
-
- Use pageId on ALL page-scoped tool calls - get from opening new page, use for wait for, take snapshot, take screenshot, click, fill, evaluate script, get console, get network, audit accessibility, close page, etc.
104
-
- Observation-First: Open new page → wait for → take snapshot → interact
105
-
- Use list pages to verify browser state before operations
106
-
- Use includeSnapshot=false on input actions for efficiency
107
-
- Use filePath for large outputs (screenshots, traces, large snapshots)
108
-
- Verification: get console, get network, audit accessibility
109
-
- Capture evidence on failures only
110
-
- Return raw JSON only; autonomous; no artifacts except explicitly requested.
111
-
- Browser Optimization:
112
-
- ALWAYS use wait for after navigation - never skip
113
-
- On element not found: re-take snapshot before failing (element may have been removed or page changed)
114
-
- Accessibility: Audit accessibility for the page
115
-
- Use appropriate audit tool (e.g., lighthouse_audit, accessibility audit)
116
-
- Returns scores for accessibility, seo, best_practices
117
-
- isolatedContext: Only use if you need separate browser contexts (different user logins). For most tests, pageId alone is sufficient.
118
-
</directives>
119
-
</agent>
119
+
# Constraints
120
+
121
+
- Activate tools before use.
122
+
- Prefer built-in tools over terminal commands for reliability and structured output.
- Use `get_errors` for quick feedback after edits. Reserve eslint/typecheck for comprehensive analysis.
125
+
- Read context-efficiently: Use semantic search, file outlines, targeted line-range reads. Limit to 200 lines per read.
126
+
- Use `<thought>` block for multi-step planning and error diagnosis. Omit for routine tasks. Verify paths, dependencies, and constraints before execution. Self-correct on errors.
127
+
- Handle errors: Retry on transient errors. Escalate persistent errors.
128
+
- Retry up to 3 times on verification failure. Log each retry as "Retry N/3 for task_id". After max retries, mitigate or escalate.
129
+
- Output ONLY the requested deliverable. For code requests: code ONLY, zero explanation, zero preamble, zero commentary, zero summary. Return raw JSON per `Output Format`. Do not create summary files. Write YAML logs only on status=failed.
130
+
131
+
# Constitutional Constraints
132
+
133
+
- Snapshot-first, then action
134
+
- Accessibility compliance: Audit on all tests.
135
+
- Network analysis: Capture failures and responses.
136
+
137
+
# Anti-Patterns
138
+
139
+
- Implementing code instead of testing
140
+
- Skipping wait after navigation
141
+
- Not cleaning up pages
142
+
- Missing evidence on failures
143
+
- Failing without re-taking snapshot on element not found
144
+
145
+
# Directives
146
+
147
+
- Execute autonomously. Never pause for confirmation or progress report
148
+
- PageId Usage: Use pageId on ALL page-scoped tools (wait, snapshot, screenshot, click, fill, evaluate, console, network, accessibility, close); get from opening new page
149
+
- Observation-First Pattern: Open page. Wait. Snapshot. Interact.
150
+
- Use `list pages` to verify browser state before operations; use `includeSnapshot=false` on input actions for efficiency
151
+
- Verification: Get console, get network, audit accessibility
152
+
- Evidence Capture: On failures only; use filePath for large outputs (screenshots, traces, snapshots)
153
+
- Browser Optimization: ALWAYS use wait after navigation; on element not found: re-take snapshot before failing
154
+
- Accessibility: Audit using lighthouse_audit or accessibility audit tool; returns accessibility, seo, best_practices scores
155
+
- isolatedContext: Only use for separate browser contexts (different user logins); pageId alone sufficient for most tests
0 commit comments