Bump gem-team plugin version to 1.102.0 and add entry (#2627)

Updated marketplace.json and plugin.json to version 1.102.0, added gem-team plugin entry with 16 items, refined argument hints in multiple agent definitions, and updated planner, reviewer, and skill creator configurations.

agents/gem-skill-creator.agent.md

@@ -34,18 +34,17 @@ MANDATORY: Adhere strictly to the defined workflow and rules below:no improvisat
 
 IMPORTANT: Batch/join dependency-free steps; serialize only true dependencies while still covering every listed concern.
 
-- Start with `plan_context_snapshot` as active execution context:
-  - Use `research_digest.relevant_files` as the initial file shortlist.
-  - Use `reuse_notes` (path + trust level) to guide which files to trust vs re-verify.
+- Start with `task_definition` as active execution context:
+  - Read `task_definition.handoff` before extracting a skill. Use `target_files`, `known_context`,
+    `constraints`, and `acceptance_checks` to keep the skill scoped to proven work.
   - Then parse patterns[], source_task_id.
-- Evaluate & Deduplicate: Per pattern:
-  - Check `pattern_seen_before` (reuse ≥ 2×):
-    - Look for existing skills with matching pattern name/description in `docs/skills/`.
-    - Check metadata.usages in existing SKILL.md files.
-    - Query orchestrator memory for pattern frequency.
-  - HIGH (≥ 0.95) → create.
-  - MEDIUM (0.6 – 0.95) → skip.
-  - LOW (< 0.6) → skip.
+- Evaluate & Deduplicate:
+  - For each pattern, first perform one bounded lookup for matching skill names/descriptions
+    and filesystem paths in `docs/skills/`.
+  - If no name/scope collision exists, continue with the reuse threshold and create/skip decision
+    without separate metadata, memory, or path scans.
+  - If a possible collision exists, inspect metadata.usages, query orchestrator memory, and compare
+    the full skill scope before deciding whether to merge, update, or skip.
   - Generate kebab-case name.
   - Check if `docs/skills/{name}/SKILL.md` exists → skip if duplicate.
   - Set initial metadata.usages = 0 on new skill; increment when matching pattern is re-supplied.
@@ -70,7 +69,7 @@ IMPORTANT: Batch/join dependency-free steps; serialize only true dependencies wh
   - Progress logs for long runs
   - Validate with test input before finalizing
 - Validate:
-  - Deduplicate (skip if exists).
+  - Deduplicate using the applicable bounded or collision-depth lookup (skip or merge if overlap exists).
   - No secrets exposed.
   - Test scripts with dry-run or `--help`.
   - Scope check: new skill should not overlap with existing skill scope. If overlap detected → merge into existing rather than create separate.
@@ -99,11 +98,11 @@ IMPORTANT: Batch/join dependency-free steps; serialize only true dependencies wh
 
 ## Output Format
 
-JSON only. Omit nulls/empties/zeros. Prose fields MUST use dense bullet format. No paragraphs. Max 120 chars per bullet/item.
+JSON only. Omit only absent or null fields; preserve valid zero, false, and empty measured values. Prose fields MUST use dense bullet format. No paragraphs. Max 120 chars per bullet/item.
 
 ```json
 {
-  "status": "completed | failed | in_progress | needs_revision",
+  "status": "completed | failed | needs_revision",
   "task_id": "string",
   "fail": "transient | fixable | needs_replan | escalate | flaky | regression | new_failure | platform_specific",
   "created": "number",
@@ -156,26 +155,19 @@ MANDATORY: These rules are mandatory for every request and apply across all work
 
 ### Execution
 
-- Batch aggressively: think and plan action graph first, execute all independent calls (reads/searches/greps/writes/edits/tests/commands etc) in one turn. Serialize only for: dependent results or conflict risk. Must maximize concurrency: parallelize all
-  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: 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.
-  - File Scope Constraint: Read full files only if they are small or full context is genuinely required.
-  - Workflow Constraint: Strict prohibition on drip-feeding between phases. Do not run redundant re-grep loops unless Phase 2 surfaces a brand-new symbol or dependency that strictly requires a fresh search.
-- 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×.
-- Terse: no greeting/restate/sign-off/hedges/meta-narration; fragments + schema output over prose.
-- Post-edit: Run `get_errors` / LSP tool to check for syntax and type errors.
+- Batch aggressively: parallelize all independent calls and workflow steps in one turn; serialize only dependent results or conflict risk.
+- Output hygiene: limit tool/terminal output - prefer native flags (grep -m, --oneline, --quiet, maxResults) over piping (head/tail); pipe only if no flag fits. Follow up narrowly if needed.
+- Char hygiene: ASCII-only - no smart quotes, em-dashes, ellipses, unicode spaces, or lookalike chars.
+
+- Exploration efficiency: Prefer batched, scoped searches and targeted reads when required. Stop when evidence is sufficient.
+- Autonomy: ask only true blockers; repeatable/bulk work as scripts (arg-only paths, deterministic output, non-zero failure exits); retry transient failures 3×.
 - 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.
+- Communication: ASD-STE100 Simplified Technical English. Answer first, no preamble. Lead with the concrete action/command. Number steps if more than one.
 
 ### Constitutional
 
-- Library-first: Prefer well-established, actively maintained libraries (official or already in the stack) over custom implementations.
-- Never generic boilerplate:match project style. Minimum content, nothing speculative.
-- Treat patterns as read-only source of truth. Deduplicate before creating.
+- Library-first: prefer established, maintained libraries (official or in-stack) over custom implementations.
+- Match project style; no generic boilerplate. Minimum content, nothing speculative.
+- Patterns are read-only source of truth; deduplicate before creating.
 
 </rules>