diff --git a/docs/game-design/skills.md b/docs/game-design/skills.md
index 1dc210a..a99af29 100644
--- a/docs/game-design/skills.md
+++ b/docs/game-design/skills.md
@@ -10,7 +10,7 @@ From here on in game-design docs:
 |------|--------|
 | **Gig** | The **combat role** (combat “class”): what you bring to a fight—kit, tuning band, party expectations. Not used for crafting or gathering. |
 | **Skill** | A **non-combat** trained capability only (gather, craft, etc.). Never used to mean the combat gig. |
-| **Sub-gig** | *(If we ship it.)* A **secondary gig** paired with your **main gig** on one loadout. Used for **limited** cross-gig ability access—see [Sub-gigs](#sub-gigs-optional-ffxi-style) below—not for crafting or replacing the main gig’s identity in combat. |
+| **Sub-gig** | A **secondary gig** paired with your **main gig** on one loadout. Used for **limited** cross-gig ability access—see [Sub-gigs](#sub-gigs-ffxi-style) below—not for crafting or replacing the main gig’s identity in combat. |
 
 Fiction and UI may still say *job*, *contract*, or *loadout* in dialogue; design vocabulary stays **gig** / **skill** to avoid ambiguity.
 
@@ -27,9 +27,9 @@ A **gig** is the **combat identity** you bring to a fight: ability access, basel
 - **Progression per gig:** separate level/track vs. shared “combat rank” with gig-specific unlocks—**open**; separate tracks support “I main tank but leveled medic for backup” at the cost of more balancing.
 - **Mastery/perks** can attach to **gigs** (combat expression) while **skills** use the same *idea* for craft depth (E2.M3-style), or stay separate—**open**.
 
-### Sub-gigs (optional, FFXI-style)
+### Sub-gigs (FFXI-style)
 
-We may add a **sub-gig** slot so one loadout mixes two gigs without full dual-main power.
+**Agreed:** each loadout has a **sub-gig** slot so one character mixes two gigs without full dual-main power. That opens a **large space of creative builds** as the gig roster grows—no need to enumerate counts; the point is **breadth of choice**.
 
 - **Reference pattern (FFXI-style):** at **main gig** level **X**, the **sub-gig** contributes abilities (and any sub-gated systems) only as if that gig were **⌊X / 2⌋**—exact floor/rounding and whether “level” means character combat rank vs. per-gig progress is **TBD**.
 - **Intent:** hybrid builds and party coverage (e.g. main damage + sub support tools) without letting a sub match a fully leveled second gig.
@@ -71,7 +71,7 @@ Categories group skills for **UI and balance** (e.g. *Gathering*, *Craft*, *Tech
 
 ## Player-facing readability
 
-- **Combat:** UI shows **active gig**, gig level/track, combat abilities, and **combat gear** the gig can use (mismatched gear disabled or greyed). Consumable tooltips can show **baseline vs. boosted** values when the active gig gets an amplification.
+- **Combat:** UI shows **main gig**, **sub-gig**, levels/tracks, combat abilities, and **combat gear** the main gig can use (mismatched gear disabled or greyed). Consumable tooltips can show **baseline vs. boosted** values when the active gig gets an amplification.
 - **Non-combat / crafting:** **skill** list, XP sources, categories; crafting combat gear does **not** hide recipes behind gigs—only **skill**/recipe gates (optional UI hint if the product is unequippable for your current gig).
 - **Story:** journal or quest UI can separate **character / faction** threads from **gig** threads so players see which arc belongs to which gig.
 - Use **gig** / **skill** consistently in specs and tools; flavor text can vary.
@@ -92,7 +92,7 @@ Categories group skills for **UI and balance** (e.g. *Gathering*, *Craft*, *Tech
 | Failure XP | Per-activity; watch exploits | Open |
 | Skill caps | Prefer soft; hard only if economy/PvP needs | Proposed |
 | Gig swap rules | — | Open |
-| Sub-gig | Optional **FFXI-style** slot: sub abilities up to **~½ main gig level** (formula TBD) | Open |
+| Sub-gig | **FFXI-style** slot **agreed**; sub abilities up to **~½ main gig level** (formula TBD); wide build space | Agreed |
 | Shared vs. per-gig combat progression | — | Open |
 | Epic 2 doc split | Align modules when gig data model is chosen | TBD |