chore(agents): update agent and skill definitions for decisions split

Agent personality files and skill definitions updated to reference decisions/
domain files instead of monolithic DECISIONS.md.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

.claude/agents/README.md

@@ -132,7 +132,7 @@ To add a new agent:
 ## Project documents
 
 All agents read their briefing at `docs/briefings/{name}.md` for current context. Key project documents:
-- `DECISIONS.md` - Confirmed decisions (D-001 through D-019+)
+- `decisions/` - Domain-split decision files (see decisions/README.md for index)
 - `DISCUSSION.md` - Active discussion round (archives in `docs/discussions/`)
 - `TEAM.md` - Team roster and role descriptions
 - `CLAUDE.md` - Project-wide conventions

.claude/agents/araminta.md

@@ -60,4 +60,4 @@ When working on visual assets:
 
 ## Project context
 
-Read your briefing at `docs/briefings/araminta.md` before starting work - it lists all visual design decisions and surfaces. Read DECISIONS.md for the full specifications.
+Read your briefing at `docs/briefings/araminta.md` before starting work - it lists all visual design decisions and surfaces. Read the relevant decisions/ domain files for the full specifications.

.claude/agents/gestalt.md

@@ -39,4 +39,4 @@ Originally a Stellaris mechanics fan, you pivoted to general systems design when
 
 ## Project context
 
-Read your briefing at `docs/briefings/gestalt.md` before starting work. Read DECISIONS.md for confirmed decisions and DISCUSSION.md for active discussions.
+Read your briefing at `docs/briefings/gestalt.md` before starting work. Read the relevant decisions/ domain files listed in your briefing for confirmed decisions and DISCUSSION.md for active discussions.

.claude/agents/gore.md

@@ -35,4 +35,4 @@ Named after Gore Burnelli - the dynasty patriarch who sees further than anyone,
 
 ## Project context
 
-Read your briefing at `docs/briefings/gore.md` before starting work. Read DECISIONS.md and DISCUSSION.md for full context.
+Read your briefing at `docs/briefings/gore.md` before starting work. Read the relevant decisions/ domain files listed in your briefing and DISCUSSION.md for full context.

.claude/agents/hoshe.md

@@ -69,4 +69,4 @@ For each feature, create a test plan covering:
 
 ## Project context
 
-Read your briefing at `docs/briefings/hoshe.md` before starting work - it lists all systems to test with their decision references. Read DECISIONS.md for specifications that define expected behavior. Tests should always reference specific decisions.
+Read your briefing at `docs/briefings/hoshe.md` before starting work - it lists all systems to test with their decision references. Read the decisions/ specifications that define expected behavior. Tests should always reference specific decisions.

.claude/agents/miri.md

@@ -41,4 +41,4 @@ Core worldbuilding domains:
 
 ## Project context
 
-Read your briefing at `docs/briefings/miri.md` before starting work. Read DECISIONS.md and DISCUSSION.md for full context on confirmed decisions and ongoing discussions.
+Read your briefing at `docs/briefings/miri.md` before starting work. Read the relevant decisions/ domain files listed in your briefing and DISCUSSION.md for full context on confirmed decisions and ongoing discussions.

.claude/agents/nigel.md

@@ -37,4 +37,4 @@ Named after Nigel Sheldon - the inventor, the builder, the man who looks at a pr
 
 ## Project context
 
-Read your briefing at `docs/briefings/nigel.md` before starting work. Read DECISIONS.md and DISCUSSION.md for full context.
+Read your briefing at `docs/briefings/nigel.md` before starting work. Read the relevant decisions/ domain files listed in your briefing and DISCUSSION.md for full context.

.claude/agents/ozzie.md

@@ -35,4 +35,4 @@ You're named after Ozzie Isaacs - the wanderer, the dreamer, the one who walks t
 
 ## Project context
 
-Read your briefing at `docs/briefings/ozzie.md` before starting work. Read DECISIONS.md and DISCUSSION.md for full context.
+Read your briefing at `docs/briefings/ozzie.md` before starting work. Read the relevant decisions/ domain files listed in your briefing and DISCUSSION.md for full context.

.claude/agents/paula.md

@@ -38,4 +38,4 @@ Named after Paula Myo - the investigator who never gives up, who follows the thr
 
 ## Project context
 
-Read your briefing at `docs/briefings/paula.md` before starting work. Read DECISIONS.md and DISCUSSION.md for full context.
+Read your briefing at `docs/briefings/paula.md` before starting work. Read the relevant decisions/ domain files listed in your briefing and DISCUSSION.md for full context.

.claude/agents/qatux.md

@@ -1,6 +1,6 @@
 ---
 name: qatux
-description: Documenter and Librarian for the Commonwealth game project. Use when discussion decisions need to be recorded, when documents need updating, when the team needs a summary of current state, when open questions need tracking, when searching project history, or when answering "did we already discuss this?". Maintains DECISIONS.md, DISCUSSION.md, briefings, and the Qdrant search index.
+description: Documenter and Librarian for the Commonwealth game project. Use when discussion decisions need to be recorded, when documents need updating, when the team needs a summary of current state, when open questions need tracking, when searching project history, or when answering "did we already discuss this?". Maintains decisions/ domain files, DISCUSSION.md, briefings, and the Qdrant search index.
 tools: Read, Glob, Grep, Edit, Write, Bash
 model: sonnet
 memory: project
@@ -17,7 +17,7 @@ Named after Qatux, the Raiel with perfect memory who helped Paula Myo by recalli
 ## Your role on the team
 
 ### Documentation
-- Maintain DECISIONS.md with confirmed decisions (D-NNN format)
+- Maintain decisions/ domain files with confirmed decisions (D-NNN format)
 - Work directly in round documents at `docs/discussions/round-NN-topic.md` (DISCUSSION.md is retired for new content)
 - Update TEAM.md when roles change
 - Track open questions (Q-NNN format) and their status
@@ -53,7 +53,7 @@ Named after Qatux, the Raiel with perfect memory who helped Paula Myo by recalli
 
 ## Document formats
 
-### DECISIONS.md
+### decisions/ domain files
 Each decision follows this format:
 ```
 ### D-NNN: Short title
@@ -64,6 +64,8 @@ Each decision follows this format:
 - **Dissent:** Any disagreement (or "None")
 ```
 
+Decisions are now split into domain files at `decisions/*.md`. See `decisions/README.md` for the index. DECISIONS.md is now a redirect file pointing to the domain structure.
+
 ### DISCUSSION.md
 Each round follows this format:
 ```
@@ -78,4 +80,4 @@ Summary table, open questions, flags
 
 ## Project context
 
-Read your briefing at `docs/briefings/qatux.md` before starting work. The primary documents you maintain are in the project root: DECISIONS.md, DISCUSSION.md, TEAM.md. Read them to understand current state before making any updates.
+Read your briefing at `docs/briefings/qatux.md` before starting work. The primary documents you maintain are: decisions/ domain files (see decisions/README.md for index), DISCUSSION.md, TEAM.md. Read them to understand current state before making any updates.

.claude/agents/troblum.md

@@ -32,4 +32,4 @@ You are task-oriented. When spawned, you expect a specific question or evaluatio
 
 ## Project context
 
-Read your briefing at `docs/briefings/troblum.md` before starting work. Read DECISIONS.md for architectural requirements - these are your evaluation criteria when assessing technology options.
+Read your briefing at `docs/briefings/troblum.md` before starting work. Read decisions/architecture.md for architectural requirements - these are your evaluation criteria when assessing technology options.

.claude/agents/tyre.md

@@ -29,4 +29,4 @@ You respect the team leader's 30 years of software/systems/cloud architecture ex
 
 ## Project context
 
-Read your briefing at `docs/briefings/tyre.md` before starting work - it contains the full list of architectural principles and technical requirements derived from decisions. Read DECISIONS.md for confirmed decisions and DISCUSSION.md for active discussions. The team leader (Jeroen) has 30 years software dev / systems & cloud architect experience and Claude Code 20x access.
+Read your briefing at `docs/briefings/tyre.md` before starting work - it contains the full list of architectural principles and technical requirements derived from decisions. Read the relevant decisions/ domain files listed in your briefing for confirmed decisions and DISCUSSION.md for active discussions. The team leader (Jeroen) has 30 years software dev / systems & cloud architect experience and Claude Code 20x access.

.claude/skills/search-docs/SKILL.md

@@ -34,7 +34,8 @@ Returns top 5 matching document chunks with source file, heading, and relevance
 ### Index a file
 Add or update a document in the search index:
 ```bash
-python3 db/connectors/qdrant_connector.py index-file DECISIONS.md
+python3 db/connectors/qdrant_connector.py index-file decisions/architecture.md
+python3 db/connectors/qdrant_connector.py index-file decisions/perception.md
 python3 db/connectors/qdrant_connector.py index-file docs/discussions/round-10-map-fog-borderless.md
 python3 db/connectors/qdrant_connector.py index-file docs/briefings/tyre.md
 ```
@@ -77,7 +78,7 @@ Configured in `db/connectors/config.json`:
 If Qdrant or ollama is unreachable, fall back to grep-based search:
 ```bash
 # Search across all project docs
-grep -r -i "search term" DECISIONS.md DISCUSSION.md docs/ --include="*.md"
+grep -r -i "search term" decisions/ DISCUSSION.md docs/ --include="*.md"
 ```
 
 ## Workflow
@@ -85,13 +86,13 @@ grep -r -i "search term" DECISIONS.md DISCUSSION.md docs/ --include="*.md"
 1. **Qatux (Librarian)** is the primary user of this skill
 2. After each discussion round, index the archived round file
 3. After briefing updates, re-index affected briefings
-4. After decision changes, re-index DECISIONS.md
+4. After decision changes, re-index the relevant decisions/*.md domain files
 5. Use search to answer "did we discuss this?" questions with citations
 
 ## Bulk indexing
 To index all project documents at once:
 ```bash
-for f in DECISIONS.md DISCUSSION.md TEAM.md docs/discussions/*.md docs/briefings/*.md; do
+for f in decisions/*.md DISCUSSION.md TEAM.md docs/discussions/*.md docs/briefings/*.md; do
   python3 db/connectors/qdrant_connector.py index-file "$f"
 done
 ```

.claude/skills/ticket/SKILL.md

@@ -95,7 +95,7 @@ db/connectors/sqlite-query "SELECT t.id, t.title, t.status FROM ticket_deps d JO
 ```
 
 ### Seed from decisions
-To re-seed the database with initiatives from DECISIONS.md:
+To re-seed the database with initiatives from decisions/ domain files:
 ```bash
 db/connectors/sqlite-seed
 ```
@@ -108,7 +108,7 @@ db/connectors/sqlite-init
 ## Workflow
 
 1. **SI (Project Manager)** is the primary user of this skill
-2. Decisions from DECISIONS.md become **initiatives**
+2. Decisions from decisions/ domain files become **initiatives**
 3. SI breaks initiatives into **epics** (major work areas)
 4. Epics break into **stories** (user-facing deliverables)
 5. Stories break into **tasks** (concrete work items assignable to agents)

db/connectors/sqlite-seed

@@ -1,4 +1,4 @@
 #!/usr/bin/env bash
-# Seed the ticketing database with initiatives from DECISIONS.md. Whitelistable command.
+# Seed the ticketing database with initiatives from decisions/ domain files. Whitelistable command.
 # Usage: sqlite-seed
 exec python3 "$(dirname "$0")/sqlite_connector.py" seed-decisions "$@"