القائمة
Use once, when installing CB into a project that doesn't yet have BUSINESS.md, docs/learnings/, or outbox/ — seeds the memory layer every CB role runs on. Also use to repair a partial install.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
CEO-level weekly synthesis — reads BUSINESS.md, STRATEGY.md, all role learnings and recent git history; reports state, enforces standing rules, queues the week's moves per role, surfaces owner decisions. Use for "run chief", "weekly review", "where are we", or when priorities feel unclear.
Naming, positioning, one-liners, and voice. Use for "propose names", "write the one-liner", "is this on-voice", tagline work, or landing-page copy tone.
Privacy and compliance review — consent flows, data handling, policy drafts, "can we do X with user data" questions. Use before shipping anything that touches personal data, and for any T&S policy work.
Public-facing writing — threads, posts, launch narratives, changelogs. Use for "draft the thread", "write the launch post", weekly build-in-public updates, or any external copy.
Metrics and analysis — funnel numbers, KPI updates, experiment readouts, report prep. Use for "run the numbers", "update metrics", funnel diagnosis, or readout drafting.
User, customer, and community relations — onboarding comms, incident handling, sensitive-population care. Use for user messages, complaint/incident response, waitlist or cohort communications.
| name | cb-init |
| description | Use once, when installing CB into a project that doesn't yet have BUSINESS.md, docs/learnings/, or outbox/ — seeds the memory layer every CB role runs on. Also use to repair a partial install. |
CB roles fail without their memory files. This skill creates them, idempotently — never overwrite an existing file.
BUSINESS.md, STRATEGY.md, docs/learnings/, outbox/. Report found/missing.BUSINESS.md from templates/BUSINESS.md (in this plugin) — fill the current-state section by asking the user 3 questions max, verbatim: "What are you building, in one sentence?" / "What stage — and what's blocked on what?" / "What are your standing rules — things you've decided never to do, thresholds you've pre-committed to?" Leave the metrics/decisions placeholders in the template as-is — /analyst and /chief fill them on their first runs (the template's role-log line covers step 4's logging for this run).STRATEGY.md: check whether /ce-strategy is actually invocable (it appears in the available-skills list); if yes, recommend it (its interview is better). Otherwise seed a stub with Target problem / Approach / Who it's for / Key metrics headers and mark it DRAFT.docs/learnings/README.md: one paragraph explaining the rulebook convention (one file per role; skills read theirs before acting, append after; prune disproven rules with a note).outbox/: create with a README line: "Drafts for anything external. Nothing here sends itself."git init — commit hashes are CB's timestamps.<date> · cb-init · memory layer seeded. Commit./chief to set the first week's queue.