build-synergy-scenarios

The synergy tracker state machine uses three states: not_started, needs_rewrite, and needs_review. The Skill selects the next non-complete entry and transitions it through deep rewrites, validation, and review stages.

Yes, you can batch up to five synergy scenarios per invocation. Each batch researches target card oracle text, validates mechanics, writes results to scenario files, and updates the tracker and action coverage summaries.

Synergy scenario testing validates card interactions using accurate oracle text. A tracker state machine is needed when orchestrating batch rewrites and reviews across multiple scenario files to maintain coherence and prevent incomplete entries.

Yes, scenario testing applies linting and validation steps alongside self-review to catch math and rule errors. It verifies oracle text accuracy and performs checks to ensure scenario mechanics reflect correct rules.

Batch processing handles up to five scenarios per invocation and processes one file at a time. It requires the tracker state machine to be coherent and cannot exceed the batch limit without multiple sequential runs.