← ClaudeAtlas

team-ceo-viewlisted

Use when a team-* skill (team-refactor, team-council, team-council-plan, team-kickoff) reaches a CEO gate and the human must approve, decline, or choose between options. Also when the user asks for a visual, HTML, or browser view of a decision, backlog, or plan.
TokiDEV/team-skills · ★ 4 · AI & Automation · score 77
Install: claude install-skill TokiDEV/team-skills
# team-ceo-view Turns a CEO gate into a local HTML decision page. Every decision, tension and rejected idea is a card the human decides on. Each card carries its own evidence: arguments for and against, metrics, before/after code, figures and screenshots. A sidebar holds search, filters and an overview whose item chips jump to their cards. The human decides in the browser and pastes the decisions back. **Markdown stays the source of truth.** Agents read and git diffs the `.md` record. The HTML is the human's view of the same gate, and never holds a decision the `.md` doesn't get. ## Procedure 1. **Write the gate JSON** to `.council/gates/YYYY-MM-DD-<topic>.ceo.json` (create the folder if absent), with `source` set to the record it belongs to. Contract below. **Evidence goes on the item it supports.** Arguments, metrics, code and figures belong to the decision, tension or rejected item they concern, never to a page-level section. Copy every screenshot an item relies on into `.council/gates/YYYY-MM-DD-<topic>/`: scratchpad and `/tmp` are wiped after the session. 2. **Render:** `node <this skill's directory>/render.js .council/gates/<file>.ceo.json` (`~/.claude/skills/team-ceo-view/` for a manual install; the plugin cache when installed as a plugin). It prints the `.html` path and rejects invalid JSON with a list of errors. It also rejects any item whose text mentions a screenshot or "figure N" but carries no `figures`. Re-rendering after the JSON changes gives the human