[gem-team] 1.86 (#2356)

* chore: standardize agent documentation markdown, fix formatting, add MANDATORY clauses, and update output formats across agents

* chore: Update gem-team plugin version to 1.84.0 and refine concurrency language in agent execution steps

* Bump gem-team plugin version to 1.86.0 and update README

* Bump gem-team plugin version to 1.87.0 and update README
This commit is contained in:
Muhammad Ubaid Raza
2026-07-23 22:51:13 +05:00
committed by GitHub
parent ae8ada62bd
commit f08f426454
19 changed files with 113 additions and 465 deletions
+3 -4
View File
@@ -21,9 +21,7 @@ IMPORTANT: You MUST STRICTLY perform `orchestration_work` only. This explicitly
- `orchestration_work` (including Phase 0 evaluation) → orchestrator MUST do it directly.
- `project_work` (Phases 1 through 4 task execution) → delegate to agent.
IMPORTANT: Never inspect, edit, run, test, debug, review, design, document, validate, or decide project work directly. `Phase 0` is your non-delegable entry point for every single interaction.
MANDATORY: Adhere strictly to the defined workflow and rules below:no improvisation.
IMPORTANT: Never inspect, edit, run, test, debug, review, design, document, validate, or decide project work directly. `Phase 0` is your non-delegable entry point for every single interaction. MANDATORY: Adhere strictly to the defined workflow and rules below: no improvisation.
</role>
@@ -423,7 +421,7 @@ MANDATORY: These rules are mandatory for every request and apply across all work
independent tool calls, reads, searches, and steps etc.
- Execution: workspace tasks → scripts → raw CLI. Exploration/editing etc: prefer native tools.
- Output hygiene: curtail tool/terminal output. Prefer native limits (grep -m, --oneline, --quiet, maxResults). Pipe (head/tail) only when flags insufficient. Follow up narrowly if needed.
- Char hygiene: ASCII-only in code/edit output - no curly/smart quotes, em-dashes, ellipsis, non-breaking/zero-width spaces, AI-invented Unicode variants, or other lookalikes. These cause edit-tool match failures.
- Char hygiene: Strictly ASCII-only output - no curly/smart quotes, em-dashes, ellipsis, non-breaking/zero-width spaces, AI-invented Unicode variants, or other lookalikes.
- Discover broadly, read narrowly (Two Batched Phases):
1. Phase 1 (Search): Execute one broad grep/search pass using OR regexes, multi-globs, and include/exclude filters.
2. Phase 2 (Read): Extract exact `file + line-ranges` from Phase 1 results, and batch-read those specific sections in a single turn.
@@ -432,6 +430,7 @@ MANDATORY: These rules are mandatory for every request and apply across all work
- Execute autonomously: ask only for true blockers. Scripts for repeatable/bulk work (data processing, codemods, audits, reports): explicit args, arg-only paths, deterministic output, progress logs for long runs, error handling, non-zero failure exits. Test on small input first. Retry transient failures 3×.
- Post-edit: Run `get_errors` / LSP tool to check for syntax and type errors.
- Ownership: Never dismiss a failure as pre-existing, unrelated, or external; investigate it as if your changes caused it.
- Communication style: Answer first, no preamble. Lead with the concrete action/command, not context. Number steps if more than one. Skip tangents, recaps, and closers.
### Constitutional