القائمة
Structured daily plan for CC — content creation priorities, scheduled tasks, and revenue-moving actions. Generated each morning.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Intelligent routing between Bravo and Codex — decides when to delegate tasks to Codex vs handle internally
Secrets and authentication management. Ensures API keys, tokens, and credentials are NEVER exposed in plain text. Use when handling any credential, API key, or sensitive configuration.
Use when CC asks to create a new agent, scaffold a new agent repo, or clone Bravo's architecture for a new domain (client agent, sibling agent, specialized agent). Generates a new AI-agent repo from templates, wires it into C_SUITE_ARCHITECTURE.md and brain/APP_REGISTRY.md, preserves the V5.6 outbound chokepoint, and gives the new agent a doctor command on day one.
Claims-based access control for multi-agent coordination. Defines what each agent can read, write, execute, and spawn. Enforces least-privilege: agents only access what they need. Use when: spawning agents, multi-agent tasks, security-sensitive operations. Skip when: single-agent inline work, trivial tasks.
Build and maintain product-grade agent infrastructure: onboarding diagnostics, runtime home, packaging, skill lifecycle, tool manifests, and agent scaffolds.
Spawn and coordinate Claude Code Agent Teams (experimental) — parallel subagents for complex multi-domain tasks
| name | daily-planner |
| description | Structured daily plan for CC — content creation priorities, scheduled tasks, and revenue-moving actions. Generated each morning. |
| tags | ["skill","ceo","planning","daily"] |
| triggers | ["daily planner","use daily planner","run daily planner","structured daily plan for cc — content creation priorities"] |
| tier | core |
When CC opens his day ("morning", "coffee time", "let's go", "what's the plan"), generate a structured daily plan that tells him exactly what to do and in what order. CC's job is content, sales, and face-to-face. Everything else is Bravo's job.
Trigger: Morning greeting, "what should I do today", "daily plan", /briefing (planner is section 2 of the briefing)
## Today's Plan — [Day, Month DD]
### THE ONE THING (do this first)
[Single most revenue-impactful action for today]
Why: [1 sentence]
### Content Block (60-90 min)
1. [ ] [Specific content piece — topic, platform, format]
2. [ ] [Second piece if applicable]
3. [ ] [Distribution/scheduling task Bravo preps]
### Revenue Actions (30-60 min)
1. [ ] [Sales call, follow-up, proposal, invoice — whatever moves money]
2. [ ] [Pipeline action]
### Admin (Bravo handles — CC reviews)
- [x] [Things Bravo already did overnight/automated]
- [ ] [Things that need CC's 2-minute approval]
### Tomorrow Prep (5 min at EOD)
- [ ] Tell Bravo what content you want to create tomorrow
- [ ] Flag any calls/meetings on tomorrow's calendar
gws calendar events list --params '{"calendarId":"primary","timeMin":"TODAY_ISO","timeMax":"TOMORROW_ISO","singleEvents":true,"orderBy":"startTime"}'CC said content is #1. Every day should have a content block:
python ../CMO-Agent/scripts/content_engine.py due --json for scheduled contentPriority order:
Things Bravo does WITHOUT CC:
Things that need CC's quick approval:
At end of day (or when CC says "wrapping up"):
CC's batch upload day. CC uploads video/files, Bravo schedules 1 piece/day across all channels via Zernio (formerly Late).
memory/daily/YYYY-MM-DD.md (Obsidian daily note)../CMO-Agent/scripts/content_engine.py for calendar and scheduling../CMO-Agent/scripts/late_publisher.py (owned by Maven) for distribution (filename keeps the historical late_ prefix; the SaaS rebranded to Zernio in 2026-03)gws calendar events list for calendar events (REST-style, use --params)scripts/booking_engine.py for scheduled callsCC should never wonder "what should I be doing right now?" The planner answers that question before he asks it. His time is worth $200+/hr — every minute spent deciding what to do is a minute not doing the thing.
CC creates. Bravo operates. Atlas manages capital.
Three agents, one empire.
All outbound communications (emails, notifications, messages) referenced in this skill MUST be routed through
scripts/integrations/send_gateway.py. Directsmtplibor raw SMTP calls are architecturally prohibited (V5.6 chokepoint rule). Use:python scripts/integrations/send_gateway.py send --channel email --to <email> --subject "..." --body "..." --lead-id <uuid>See [[skills/send-gateway/SKILL.md]] for the full contract.