Add accountability chart cross-references to 6 skills

skills/ceos-clarity/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: ceos-clarity
 description: Use when taking a Clarity Break — stepping back from day-to-day work for strategic thinking time
-file-access: [data/clarity/, templates/clarity-break.md, data/vision.md, data/rocks/, data/scorecard/, data/issues/open/]
+file-access: [data/clarity/, templates/clarity-break.md, data/vision.md, data/rocks/, data/scorecard/, data/issues/open/, data/accountability.md]
 tools-used: [Read, Write, Glob]
 ---
 
@@ -39,6 +39,7 @@ If `.ceos` is not found, stop and tell the user: "Not in a CEOS repository. Clon
 | `data/scorecard/weeks/` | Recent scorecard data for trend context |
 | `data/issues/open/` | Open issues for awareness context |
 | `templates/clarity-break.md` | Template for new Clarity Break files |
+| `data/accountability.md` | Accountability Chart (org structure for strategic context) |
 
 ### File Naming
 
@@ -80,6 +81,7 @@ Read current data to provide a strategic snapshot. Keep each section to 2-3 line
 2. **Rock status**: Read `data/rocks/[current-quarter]/`. Count on_track vs off_track. List any off-track Rocks.
 3. **Scorecard trends**: Read the 2-3 most recent files in `data/scorecard/weeks/`. Note any metrics consistently off-track.
 4. **Open issues**: Read `data/issues/open/`. Count total open issues. List the 3-5 highest priority ones.
+5. **Org structure**: Read `data/accountability.md`. Note any unfilled seats or gaps relevant to the reflection topics.
 
 Present the summary:
 
@@ -256,6 +258,11 @@ If yes, read and display the full file content.
 - **Related:** Clarity Break insights are designed to feed into the next L10 meeting. Issues identified during a Clarity Break can be raised during the L10's IDS section.
 - **Suggested flow:** Mention any unresolved Clarity Break issues during the L10. The L10 skill will surface them from `data/issues/open/` if they've been formally created.
 
+### Accountability Chart (ceos-accountability)
+
+- **Read:** `ceos-clarity` reads `data/accountability.md` during Start mode to surface org structure context — unfilled seats, responsibility gaps, or role misalignments that may be worth reflecting on.
+- **Suggested flow:** If the Clarity Break reveals accountability gaps, suggest: "Consider reviewing the Accountability Chart with `ceos-accountability`."
+
 ### Write Principle
 
 Only `ceos-clarity` writes to `data/clarity/`. Other skills do not reference Clarity Break notes directly — they are personal reflections, not operational data.

skills/ceos-l10/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: ceos-l10
 description: Use when running or reviewing a Level 10 weekly leadership meeting
-file-access: [data/meetings/l10/, templates/l10-meeting.md, data/scorecard/weeks/, data/rocks/, data/issues/open/]
+file-access: [data/meetings/l10/, templates/l10-meeting.md, data/scorecard/weeks/, data/rocks/, data/issues/open/, data/accountability.md]
 tools-used: [Read, Write, Glob]
 ---
 
@@ -37,6 +37,7 @@ If `.ceos` is not found, stop and tell the user: "Not in a CEOS repository. Clon
 | `data/issues/open/` | Open issues (surfaced during IDS section) |
 | `data/meetings/l10/` | Previous L10s (for To-Do review) |
 | `templates/l10-meeting.md` | Meeting template |
+| `data/accountability.md` | Accountability Chart (seat owners for To-Do assignment validation) |
 
 ### Meeting Structure (90 minutes)
 
@@ -147,7 +148,7 @@ For each of the top 3 issues, follow the IDS process:
 
 1. **Identify** — What is the real issue? Dig past symptoms. Use the 5 Whys if the root cause isn't obvious.
 2. **Discuss** — Each person shares their perspective. Stay focused — no tangents, no solving yet.
-3. **Solve** — What's the action? Create at least one To-Do with an owner and due date.
+3. **Solve** — What's the action? Create at least one To-Do with an owner and due date. Cross-reference `data/accountability.md` to validate that the To-Do owner matches the seat responsible for that area.
 
 Record the IDS work in the meeting notes. If this creates a new issue file, use `ceos-ids` or write to `data/issues/open/` directly.
 
@@ -222,6 +223,11 @@ During the meeting, display each section header with its time box as you move th
 - **Read:** `ceos-l10` reads open issues from `data/issues/open/` during Section 6 (IDS). The L10 surfaces the prioritized list; `ceos-ids` handles the formal Identify, Discuss, Solve work on individual issues.
 - **Suggested flow:** New issues surfaced during L10 should be created via `ceos-ids` Create mode.
 
+### Accountability Chart (ceos-accountability)
+
+- **Read:** `ceos-l10` reads `data/accountability.md` during IDS (Step 7c) to validate that To-Do owners match seat responsibilities. When assigning action items, the person who owns the relevant seat should own the To-Do.
+- **Suggested flow:** If a To-Do is assigned to someone outside the responsible seat, flag it: "This action falls under the [Seat] responsibilities. Should [Seat Owner] own it instead?"
+
 ### Orchestration Principle
 
 `ceos-l10` is the orchestrator — it reads data from multiple skills during the meeting but defers to each skill for formal create/update operations. The meeting file at `data/meetings/l10/YYYY-MM-DD.md` is the only file `ceos-l10` writes directly.

skills/ceos-process/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: ceos-process
 description: Use when documenting core processes or reviewing process followability
-file-access: [data/processes/, templates/process.md, data/vision.md]
+file-access: [data/processes/, templates/process.md, data/vision.md, data/accountability.md]
 tools-used: [Read, Write, Glob]
 ---
 
@@ -35,6 +35,7 @@ If `.ceos` is not found, stop and tell the user: "Not in a CEOS repository. Clon
 | `data/processes/` | Process documentation files |
 | `data/vision.md` | V/TO document (Core Focus and Proven Process for alignment) |
 | `templates/process.md` | Template for creating new process files |
+| `data/accountability.md` | Accountability Chart (seat owners for process-owner alignment) |
 
 ### Process File Format
 
@@ -102,6 +103,7 @@ For the steps, guide the user:
 - **One owner.** If the user tries to assign multiple owners, explain: "Each process has one owner — the person accountable for it being documented, simplified, and followed. Who should own this?"
 - **Step count.** If more than 30 steps, warn: "This process has 30+ steps. Consider splitting into sub-processes or simplifying."
 - **Duplicate check.** If a process with a similar title already exists, ask: "A process called '[title]' already exists. Update that one, or create a new one?"
+- **Seat alignment.** Cross-reference the process owner against `data/accountability.md`. The owner should hold the seat whose responsibilities align with the process's domain. Flag mismatches: "This process falls under [Seat] responsibilities. Should [Seat Owner] own it?"
 
 #### Step 5: Generate the ID
 
@@ -296,6 +298,11 @@ This skill manages process documentation independently. No other CEOS skills rea
 - **Read:** `ceos-process` reads `data/vision.md` for Core Focus and Proven Process alignment when documenting new processes. It does not write to the V/TO file.
 - **Suggested flow:** If a process doesn't align with the Core Focus, suggest reviewing the V/TO with `ceos-vto`.
 
-### Why Self-Contained?
+### Accountability Chart (ceos-accountability)
 
-Unlike other EOS components that cross-reference each other (Rocks → V/TO, Scorecard → L10), core processes are standalone documentation. They may be referenced informally during L10 meetings or annual planning, but there are no formal data dependencies between process files and other CEOS data files.
+- **Read:** `ceos-process` reads `data/accountability.md` when documenting or auditing processes to validate that process owners match seat responsibilities. A sales process should be owned by whoever holds the Sales & Marketing seat; a delivery process by the Delivery seat owner.
+- **Suggested flow:** If a process owner doesn't match the responsible seat, suggest: "This process falls under [Seat] responsibilities. Should [Seat Owner] own it?"
+
+### Why Mostly Self-Contained?
+
+Unlike other EOS components that cross-reference each other (Rocks → V/TO, Scorecard → L10), core processes are standalone documentation. They reference the V/TO for alignment and the Accountability Chart for owner validation, but there are no formal data dependencies between process files and other CEOS data files.

skills/ceos-quarterly-planning/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: ceos-quarterly-planning
 description: Use when conducting or reviewing a quarterly planning session for the leadership team
-file-access: [data/quarterly/, templates/quarterly-planning.md, data/rocks/, data/scorecard/, data/vision.md, data/issues/]
+file-access: [data/quarterly/, templates/quarterly-planning.md, data/rocks/, data/scorecard/, data/vision.md, data/issues/, data/accountability.md]
 tools-used: [Read, Write, Glob]
 ---
 
@@ -43,6 +43,7 @@ If `.ceos` is not found, stop and tell the user: "Not in a CEOS repository. Clon
 | `data/issues/open/` | Open issues (read for IDS sweep) |
 | `data/issues/solved/` | Solved issues (count for quarter summary) |
 | `templates/quarterly-planning.md` | Template for new quarterly planning files |
+| `data/accountability.md` | Accountability Chart (seat owners for Rock-owner alignment) |
 
 ### Planning File Format
 
@@ -117,6 +118,7 @@ Use when conducting the full quarterly planning session with the structured 6-se
    - `data/scorecard/metrics.md` — metric definitions and goals
    - `data/vision.md` — 1-Year Plan goals (for alignment)
    - `data/issues/open/` — open issues list (for IDS)
+   - `data/accountability.md` — seat owners (for Rock-owner alignment in Section 5)
 
 5. **Create the quarter directory** if it doesn't exist: `data/quarterly/`
 
@@ -266,6 +268,7 @@ This is a **light alignment check**, not a full V/TO refresh (that's annual).
    - **3-7 Rocks per person.** Flag if outside range: "Brad has 8 Rocks — consider consolidating."
    - **Alignment.** Each Rock should connect to a 1-Year Plan goal. Flag any that don't: "This Rock doesn't align to a specific 1-Year goal. Is it still a priority?"
    - **Measurability.** Each Rock should have a clear done/not-done criteria.
+   - **Seat alignment.** Cross-reference Rock owners against `data/accountability.md`. Each Rock's subject area should match the owner's seat responsibilities. Flag mismatches: "This Rock falls under [Seat] responsibilities. Should [Seat Owner] own it?"
 
 5. **Display the full Rock list** for approval:
 
@@ -482,6 +485,11 @@ If yes, write the summary. If a planning file already exists for this quarter, a
 
 - **Related:** Annual planning is the yearly superset that includes V/TO refresh, year-in-review, and Q1 Rock setting. Quarterly planning fills the 3 inter-annual quarters (Q2, Q3, Q4 planning). Annual planning sets the 1-Year Plan; quarterly planning executes against it.
 
+### Accountability Chart (ceos-accountability)
+
+- **Read:** `ceos-quarterly-planning` reads `data/accountability.md` during Section 5 (Set Next Quarter Rocks) to validate that Rock owners match seat responsibilities. Each Rock's subject area should map to the owner's seat in the Accountability Chart.
+- **Suggested flow:** If a Rock doesn't align with the owner's seat, suggest: "This Rock falls under [Seat] responsibilities. Should [Seat Owner] own it instead?"
+
 ### Orchestration Principle
 
 `ceos-quarterly-planning` reads data from multiple skills during the planning session (rocks, scorecard, vision, issues) but writes only to `data/quarterly/`. Individual skills handle their own operational artifacts — `ceos-rocks` creates Rock files, `ceos-scorecard` updates metrics, `ceos-ids` manages issues. The quarterly planning file captures decisions; the skills create the operational follow-through.

skills/ceos-rocks/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: ceos-rocks
 description: Use when setting, tracking, or scoring quarterly Rocks
-file-access: [data/rocks/, templates/rock.md, data/vision.md]
+file-access: [data/rocks/, templates/rock.md, data/vision.md, data/accountability.md]
 tools-used: [Read, Write, Glob]
 ---
 
@@ -35,6 +35,7 @@ If `.ceos` is not found, stop and tell the user: "Not in a CEOS repository. Clon
 | `data/rocks/QUARTER/` | Rock files for each quarter (e.g., `data/rocks/2026-Q1/`) |
 | `data/vision.md` | V/TO document (1-Year Plan for alignment checks) |
 | `templates/rock.md` | Template for creating new Rock files |
+| `data/accountability.md` | Accountability Chart (seat owners for Rock-owner alignment) |
 
 ### Rock File Format
 
@@ -113,6 +114,7 @@ For each Rock, collect:
 - **3-7 Rocks per person.** If someone has fewer than 3, ask if they should own more. If more than 7, flag: "Too many Rocks for [person]. EOS recommends 3-7. Which ones are the real priorities?"
 - **Alignment check.** Does each Rock connect to a 1-Year Plan goal? Flag any that don't.
 - **Due date.** Set to the last day of the quarter.
+- **Seat alignment.** Cross-reference Rock owners against `data/accountability.md`. Flag mismatches if a Rock's subject area doesn't match the owner's seat responsibilities, for example: "This Rock falls under the [Seat] responsibilities. Should [Seat Owner] own it instead?"
 
 #### Step 5: Generate the ID
 
@@ -262,6 +264,11 @@ If completion rate is below 80%, flag it: "Below the 80% target. Consider: Were
 
 - **Related:** Rock milestones may generate To-Dos during L10 meetings. These To-Dos are tracked in `data/todos/` via `ceos-todos` with `source: l10`.
 
+### Accountability Chart (ceos-accountability)
+
+- **Read:** `ceos-rocks` reads `data/accountability.md` when setting Rocks to validate that Rock owners match seat responsibilities. A Rock about sales pipeline should belong to whoever owns the Sales & Marketing seat.
+- **Suggested flow:** If a Rock doesn't align with the owner's seat, suggest: "This Rock falls under the [Seat] responsibilities. Should [Seat Owner] own it instead?"
+
 ### Read-Only Principle
 
 Other skills read `data/rocks/` for reference. **Only `ceos-rocks` writes to Rock files.** This preserves a single source of truth for quarterly priorities.

skills/ceos-scorecard/SKILL.md

@@ -1,7 +1,7 @@
 ---
 name: ceos-scorecard
 description: Use when defining metrics, logging weekly scorecard numbers, or analyzing trends
-file-access: [data/scorecard/, templates/scorecard-metrics.md, templates/scorecard-week.md]
+file-access: [data/scorecard/, templates/scorecard-metrics.md, templates/scorecard-week.md, data/accountability.md]
 tools-used: [Read, Write, Glob]
 ---
 
@@ -36,6 +36,7 @@ If `.ceos` is not found, stop and tell the user: "Not in a CEOS repository. Clon
 | `data/scorecard/weeks/YYYY-WNN.md` | Weekly scorecard entries |
 | `templates/scorecard-metrics.md` | Template for metrics definition file |
 | `templates/scorecard-week.md` | Template for weekly entries |
+| `data/accountability.md` | Accountability Chart (seat owners for metric ownership validation) |
 
 ### Week Format
 
@@ -78,6 +79,7 @@ For each new metric, collect:
 - **One owner per metric.** Not shared.
 - **Measurable.** Must be a specific number, not subjective.
 - **Prefer leading indicators.** Activity metrics (calls made, demos scheduled) predict results better than lagging metrics (revenue).
+- **Seat alignment.** Cross-reference metric owners against `data/accountability.md`. Each metric should map to a seat's responsibilities. Flag mismatches, e.g., "This metric seems to fall under [Seat] responsibilities. Should [Seat Owner] own it?". If a metric doesn't fit any seat, it may indicate a gap in the Accountability Chart.
 
 #### Step 4: Update the File
 
@@ -197,6 +199,11 @@ If any metric has been off-track 3+ consecutive weeks:
 
 - **Read:** `ceos-annual` reviews Scorecard metrics during the annual planning session. The team evaluates whether existing metrics are still the right numbers to track and adds or removes metrics for the new year.
 
+### Accountability Chart (ceos-accountability)
+
+- **Read:** `ceos-scorecard` reads `data/accountability.md` when defining metrics to validate that metric owners match seat responsibilities. Revenue metrics belong to whoever owns the Sales & Marketing seat; delivery metrics belong to the Delivery seat owner.
+- **Suggested flow:** If a metric owner doesn't map to a seat, suggest: "This metric doesn't align with any seat in the Accountability Chart. Should it belong to the [Seat] owner?"
+
 ### Read-Only Principle
 
 Other skills read `data/scorecard/` for reference. **Only `ceos-scorecard` writes to scorecard files.** This preserves a single source of truth for business metrics.