Skip to content

docs(maxsim-batch): add tier selection table and graceful degradation (§7.2)#188

Merged
maystudios merged 1 commit intomainfrom
worktree-agent-a57b9f58
Mar 25, 2026
Merged

docs(maxsim-batch): add tier selection table and graceful degradation (§7.2)#188
maystudios merged 1 commit intomainfrom
worktree-agent-a57b9f58

Conversation

@maystudios
Copy link
Copy Markdown
Owner

Summary

  • Adds the Tier Selection Logic decision table to templates/skills/maxsim-batch/SKILL.md, mapping each workflow type to Tier 1 (Subagents) or Tier 2 (Agent Teams) with a rationale column
  • Adds the Graceful Degradation section with the exact fallback message to display when CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS is unavailable
  • Satisfies the two missing items from PROJECT.md §7.2 lines 293–307, bringing the Parallelism Strategy audit to 100%

Test plan

  • npx vitest run — 548 tests pass (18 suites)
  • npm run build — TypeScript compiles and assets copy cleanly
  • npm run lint — Biome exits 0 (pre-existing warnings only, none in changed file)

🤖 Generated with Claude Code

… to SKILL.md

Adds the §7.2-required Tier Selection Logic decision table showing which
workflows use Tier 1 subagents vs Tier 2 Agent Teams, and a Graceful
Degradation section with the exact fallback message when Agent Teams are
unavailable. Brings the §7.2 Parallelism Strategy audit to 100%.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings March 25, 2026 18:32
@maystudios maystudios merged commit 908447b into main Mar 25, 2026
3 checks passed
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the maxsim-batch skill documentation to fully capture the Tier 1 vs Tier 2 decision guidance and the expected fallback behavior when Agent Teams are unavailable, aligning the skill with the Parallelism Strategy spec in PROJECT.md §7.2.

Changes:

  • Adds a “Tier Selection Logic” decision table mapping workflow types to Tier 1 (Subagents) vs Tier 2 (Agent Teams).
  • Adds a “Graceful Degradation” section describing Tier 1 fallback and the exact user-facing message to display.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +92 to +95
### Tier Selection Logic

MaxsimCLI chooses the tier automatically based on the workflow:

Copy link

Copilot AI Mar 25, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The new Tier Selection Logic section states that “MaxsimCLI chooses the tier automatically based on the workflow”, but this conflicts with the preceding “Current status” note that Tier 2 workflow templates are not yet implemented and all workflows currently run Tier 1. Consider clarifying that this table describes the intended/spec selection logic once Tier 2 templates exist (or otherwise reconcile these statements).

Copilot uses AI. Check for mistakes.
Comment on lines +114 to +117
If Agent Teams are unavailable (env var `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS` not set, unsupported plan, or feature not yet stable), MaxsimCLI falls back to Tier 1 subagents for all workflows. Inform the user with this exact message:

> "Competitive mode: using Tier 1 subagents (Agent Teams not available or not required for this strategy). Each executor works independently; verifier selects the best result."

Copy link

Copilot AI Mar 25, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Graceful Degradation section says Tier 1 fallback applies “for all workflows” and instructs using an “exact message”, but the message itself is specific to “Competitive mode”. If this message is only meant for competitive implementation fallback (as in the execute workflow template), consider scoping this section/message to competitive mode, and/or documenting the user-facing message(s) for other workflow degradations separately to avoid misleading guidance.

Suggested change
If Agent Teams are unavailable (env var `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS` not set, unsupported plan, or feature not yet stable), MaxsimCLI falls back to Tier 1 subagents for all workflows. Inform the user with this exact message:
> "Competitive mode: using Tier 1 subagents (Agent Teams not available or not required for this strategy). Each executor works independently; verifier selects the best result."
If Agent Teams are unavailable (env var `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS` not set, unsupported plan, or feature not yet stable), MaxsimCLI falls back to Tier 1 subagents for all workflows.
For **competitive implementation / competitive mode** workflows, inform the user with this exact message:
> "Competitive mode: using Tier 1 subagents (Agent Teams not available or not required for this strategy). Each executor works independently; verifier selects the best result."
For other workflows, clearly inform the user that Agent Teams are unavailable and that Tier 1 subagents are being used instead, using wording appropriate to that workflow.

Copilot uses AI. Check for mistakes.
@github-actions
Copy link
Copy Markdown
Contributor

🎉 This PR is included in version 5.14.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants