Guided workflow to build tournament-legal Warhammer 40K army lists. Use when the user says "build me a list", "create an army list", or Tacticus triggers the build workflow.
Build competitive, tournament-legal Warhammer 40K army lists with mandatory validation gates. This workflow is used by the Tacticus agent and enforces deterministic data queries at every step.
These skills MUST be available and used throughout:
warhammer-40k-army-data — for all unit/points/faction datawarhammer-40k-validate-list — for validation gates before outputwarhammer-40k-paint-data — if paint scheme sections are includedAsk the user:
Confirm all inputs before proceeding.
DETERMINISTIC — no memory allowed.
warhammer-40k-army-data to read _bmad/_config/custom/warhammer-40k/data/datasheets/{faction}.compact.jsonarmy-lists/{faction}/*.cheatsheet.json for reference lists_bmad-output/warhammer-40k/agents/tacticus-sidecar/validation-rules.yaml for detachment rules and hard rules_bmad-output/warhammer-40k/shared/hallucination-registry.yaml for faction-specific patternsIf any data file is missing, inform the user and offer to web search for current data.
MANDATORY ORDER: Always build 2000pt first, then scale down.
"X models x Ypts = Zpts [Source: {faction}.compact.json]"leads array in datasheetUSE warhammer-40k-validate-list skill — do NOT validate from memory.
Run all 7 gates. If any fail, fix before proceeding:
Create 1000pt and 500pt variants by removing units proportionally:
MANDATORY — every list must include this.
For each points level, create:
| Model | Qty | Loadout | Notes |
|---|---|---|---|
| [exact model] | [count] | [exact weapon names from datasheet] | [build notes] |
Then add:
Save the completed list to _bmad-output/warhammer-40k/agents/tacticus-sidecar/lists.md and offer to create a cheatsheet JSON.
At each step, verify:
leads array