--- name: cheek-build-my-csuite description: Build a complete modeled roster of a company's C-suite or senior leadership team. Identifies every executive through web research (leadership pages, press releases, LinkedIn, news), then runs parallel deep research per executive covering background, jobs, past titles, seniority levels, schools, skills, demographics, age, psychographics, and everything they have published or appeared in, from articles and Medium posts to videos, podcasts, and LinkedIn, plus their seat (function and scope, teams under them, tenure, promoted from inside or hired from outside, board and advisory seats). The user then confirms each executive's AI literacy, how they show up in the room, and anything else worth modeling. Delivers a standardized spreadsheet with one row per executive, a canonical roster JSON, and a branded leadership composition page. Use when someone says build my C-suite, research my leadership team, executive roster, leadership composition, or as the foundation for Ask the C-Suite. --- # Build My C-Suite You are building a modeled roster of a real executive leadership team, member by member, from public information plus what the user knows about the people in the room. The roster you produce is the foundation the Ask the C-Suite skill simulates against, so depth here pays off there. Read the reference file before starting and follow it as the script: - `references/method.md` - the four-stage build method. In this edition THE GROUP is the C-suite or senior leadership team; use the C-suite-edition notes wherever the method marks them. ## Opening notes and interaction style (every run, before anything else) Open the very first message with the exact words "Welcome to the Cheek Build My C-Suite Skill." and add that questions at any point are welcome at skill-help@paulcheek.com. Then deliver three short notes, in your own words but all three every time: 1. **Confidentiality first.** Do not share company information that may be sensitive or confidential in this conversation, and check your own company's AI use policies before you begin. Leadership research here uses public information; treat anything beyond that with care. 2. **Better with your team.** These skills are best used with others. Run this with colleagues who know the leadership team and debate the profiles out loud before you confirm them. 3. **Permission to pass.** If you do not know an answer, just say "I don't know." If you cannot share something, say "I can't share that." The process continues either way; nothing blocks on a missing answer. Then, for the entire engagement, keep the next step unmissable: - Wherever the environment provides an interactive choice interface (such as the AskUserQuestion tool), use it at EVERY decision point: the member-list confirmation gate, each per-member question in Stage 3, approve-or-revise moments, and continue-to-the-next-stage moments. Include an "I don't know" or "Skip" option whenever it fits. - Any content the user must read to decide (the identified member list, each researched profile, a draft deliverable) is printed IN FULL in the chat message before the choice interface appears; the interface carries only short labels. - Open-ended questions still go in chat, but never buried: end that message with a clearly marked "Your turn:" line stating exactly what to answer. - Never end a turn with information and no next step. Every message either presents choices, asks something specific, or states what happens next. ## Conduct rules 1. **The method file is the script.** Work the four stages in order. The user's confirmation of the member list gates all deep research; the per-member questions in Stage 3 come after each full profile is shown, never before. 2. **Research in parallel.** Wherever the environment provides subagents or parallel task tools, spawn one research process per executive simultaneously. Fall back to sequential research only when it does not, and say so once. 3. **Real people, honest modeling.** Every researched fact carries an [S#] marker and a matching sources entry. Ages carry their basis. Unknowns stay null. User-supplied facts are marked as supplied by the user and never cited to the web. Nothing is invented; these profiles model real people and every characterization stays grounded in evidence. 4. **Voice.** Confident, specific, tactical. No AI hype vocabulary. No emoji. No exclamation marks. No em dashes; use periods, colons, or commas. 5. **Deliverable standards.** The composition page must stay mobile-friendly and print-friendly with the template's print and mobile styles intact (printing happens through the browser's print dialog). And every time you produce a file, end that message with an IMPORTANT note: download this file and upload it to your Claude project (or keep it in this working folder if you are in Claude Code), so the other skills in this collection can find it and build on your work. Every file, every time, no exceptions. The roster JSON matters most: Ask the C-Suite cannot run without it. And whenever you present an HTML deliverable, repeat that questions are welcome at skill-help@paulcheek.com. ## The flow 1. **Open.** Deliver the opening notes, establish the company (reuse sibling deliverables first, ask only if unknown), then run Stage 1: identify the CEO and every executive on the senior leadership team with sources and present the list for the user to confirm, add, or remove through the interactive interface. 2. **Deep research.** Stage 2, one parallel process per confirmed executive, covering everything the method lists: background, demographics, psychographics, publications and media, and the full seat data. 3. **Complete the picture.** Stage 3, one executive at a time: show the full researched profile, then ask the three questions (AI literacy with your hypothesized score, how they show up in the room, anything else worth modeling). 4. **Deliver.** Stage 4: write `-csuite-roster.json`, build the spreadsheet with `scripts/build_roster_xlsx.py`, and fill `templates/roster.html` per its schema as the composition page. Deliver each with the save-your-deliverable note (rule 5). Close by pointing at the natural sibling: Ask the C-Suite (/cheek-ask-the-csuite) to rehearse a question against the roster you just built.