[gem-team] v1.138.0 Enhance Workflow for Cached Token re-usages

[mubaidr]

Pull Request Checklist

• I have read and followed the CONTRIBUTING.md guidelines.
• I have read and followed the Guidance for submissions involving paid services.
• My contribution adds a new instruction, prompt, agent, skill, workflow, or canvas extension 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, workflow, or canvas extension with GitHub Copilot.
• I have run npm start and verified that README.md is up to date.
• I am targeting the main branch for this pull request.

---

Description

• Add plan cache context to avoid re-explroation
• Structured execution to improve token cache usage
• Improve tool call paralleize
• Improve rule for simple communication
• don't ignore bugs during run, either fix if trivial or log it for future work
• enforce evidence to be optional

---

Type of Contribution

• New instruction file.
• New prompt file.
• New agent file.
• New plugin.
• New skill file.
• New agentic workflow.
• New canvas extension.
• Update to existing instruction, prompt, agent, plugin, skill, workflow, or canvas extension.
• 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.

[github-actions]

🔒 PR Risk Scan Results

Scanned 15 changed file(s).

Severity	Count
🔴 High	1
🟠 Medium	0
ℹ️ Info	0

Severity	Rule	File	Line	Match
🔴	remote-shell-execution	plugins/gem-team/README.md	69	curl -sSL https://aka.ms/apm-unix | sh

This is an automated soft-gate report. Findings indicate review targets and do not block merge by themselves.

[github-actions]

🔍 Vally Lint Results

⚠️ Warnings or advisories found

Scope	Checked
Skills	0
Agents	12
Total	12

Severity	Count
❌ Errors	0
⚠️ Warnings	0
ℹ️ Advisories	1

Summary

Level	Finding
ℹ️	Vally currently lints SKILL.md content. Agent files were detected but skipped:

Full linter output

### Agent files detected (not linted by vally)
ℹ️ Vally currently lints SKILL.md content. Agent files were detected but skipped:
agents/gem-browser-tester.agent.md
agents/gem-code-simplifier.agent.md
agents/gem-debugger.agent.md
agents/gem-devops.agent.md
agents/gem-documentation-writer.agent.md
agents/gem-implementer.agent.md
agents/gem-mobile-tester.agent.md
agents/gem-orchestrator.agent.md
agents/gem-planner.agent.md
agents/gem-researcher.agent.md
agents/gem-reviewer.agent.md
agents/gem-skill-creator.agent.md

[github-actions]

🚦 Submission status: 👀 Ready for review

Risk tier: merge-risk:medium — New or substantially changed resource without privileged execution
Required to merge: passing submission-gate checks plus 1 approval from reviewers with write access.

Why this tier

• Changes 195 lines (low-risk limit is 40)

Automated checks

Check	Status	Details
Line endings	✅ Passed	Passed · logs
Spelling	✅ Passed	Passed · logs
Generated README consistency	✅ Passed	Passed · logs
Plugin and extension validation	✅ Passed	Passed · logs
Plugin structure	✅ Passed	Passed · logs
Skill lint (vally)	✅ Passed	Passed · logs
Risk scan	✅ Passed	Passed · logs
Contributor reputation	✅ Passed	Passed · logs
Duplicate resource scan	✅ Passed	Passed · logs
PR quality signal	⏭️ Skipped	Skipped by its workflow · logs
Canvas/plugin smoke test	✅ Passed	Passed · logs

Review

• Approvals: 0/1
• Assigned reviewer: aaronpowell
• Review target date: not set
• Still needed: 1 more approval(s)
• No staffed reviewer pool owns these files yet; any reviewer with write access counts as the domain reviewer.

Commands

Command	Who	What it does
/rerun-checks	PR author, maintainers	Re-runs failed or incomplete checks and re-evaluates this gate
/request-review	PR author, maintainers	Asks the review rotation to assign a reviewer (adds needs-reviewer)

_{Updated for 9ed0a92 · gate run · This comment is maintained automatically — see submission gate docs.}

[aaronpowell]

Looks like a merge conflict, my guess is line endings. Need to rerun the script to build the readme.

[aaronpowell]

Thanks for sorting out the conflict. All automated checks pass now; the submission gate is just waiting on a review approval. The typed handoff objects and cache-ordered payloads look consistent across orchestrator, planner and the consumers. One thing to confirm: gem-planner changes from user-invocable: true to false, which stops users invoking the planner directly. Is that intentional? If so, a line in the plugin README/changelog would help. Otherwise LGTM.

[mubaidr]

This is intentional. Good suggestion, I will update readme.