Menu
Give DOTS lords lore-driven skill values and traits via the DOTS SkillSet system. Use when a canonical lord has wrong stats or a culture roster needs a balance pass.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Author a culture's armor items and swap troop equipment rosters via the generator + validation pipeline. Use when adding/revamping armor. Enforces the canonical-folder + cover-attribute rules.
Author or revamp a DOTS culture's armor set, troop tree, and recruitment wiring end-to-end. Use for new cultures or troop-tree revamps. Follows docs/ai-includes/new-culture-authoring.md.
Use when reviewing an external repo or article to adopt practices into DOTS — security-vet first, map novel vs duplicative, port (never install), review, commit your changes.
Structured 4-phase self-debug for failing agent runs (looping, drifting, burning tokens). Capture, diagnose, contained recovery, report. Complements /investigate (which is for code bugs); this skill is for harness/agent failures.
Incrementally fix dotnet build errors with minimal diffs, one error at a time
Dispatch an independent Codex verification job directly via `codex exec` Bash call, then retrieve and present results
| name | lord-skills |
| description | Give DOTS lords lore-driven skill values and traits via the DOTS SkillSet system. Use when a canonical lord has wrong stats or a culture roster needs a balance pass. |
| argument-hint | ["lord-name|culture"] |
Assign lore-driven skill values + personality traits to DOTS lords. Read the authoritative guide: docs/ai-includes/lord-skills-authoring.md (modeled on the 16-culture / ~880-NPC sweep, #228–#245).
GoT re-skin (2026-06-13): lords are now the great houses of Westeros (House = clan, per ADR-011). The LOTR lords below were zeroed at bootstrap; the SkillSet mechanism + archetype approach are reusable for GoT house lords (Eddard, Robert, Tywin, Rhaegar, Barristan…), authored in the conversion's lords phase (Phase D).
Hero stats come from skill_template="SkillSet.dots_...", NOT from the NPCCharacter's <skills> block — explicit <skills> on heroes are IGNORED by the engine (kept as documentation only). To change a hero's skills, edit the SkillSet (or repoint skill_template). See memory feedback_skill_template_overrides_explicit_skills.md — Boromir showed OneHanded=145 instead of 295 because someone hand-edited <skills>.
characters/lords.xml, lords.xslt, heroes.xslt for the name → NPCCharacter id. Classify the layer: lords.xml (DOTS-new, wins at runtime) > lords.xslt (vanilla override, loses to lords.xml on same id) > heroes.xslt (bio text, stat-irrelevant).CULTURES dict in tools/apply_culture_skills_traits.py.python tools/apply_culture_skills_traits.py --all-cultures --apply emits 3 outputs: dots_lord_skill_sets.xml, updated lords.xml + lords.xslt (skill_template swaps + populated blocks)./commit-split (data vs tool separate); one GitHub issue per culture via tools/generate_culture_issue_drafts.py.lords.xml and lords.xslt, the lords.xml version is live; the XSLT one is dead code.Main/_Module/ModuleData/**/*.xml for the OLD name (lore flavor text goes stale silently — memory feedback_rename_grep_all_moduledata.md).