القائمة
Use when managing the rolling market calendar - conferences, launches, fundraising milestones, partner events, and team constraints
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when running or reviewing a Level 10 weekly leadership meeting
Use when analyzing EOS health trends over time - Rock completion rates, scorecard consistency, checkup progression, and issue resolution patterns
Use when setting, tracking, or scoring quarterly Rocks
Use when defining metrics, logging weekly scorecard numbers, or analyzing trends
Use when taking a Clarity Break — stepping back from day-to-day work for strategic thinking time
Use when documenting core processes or reviewing process followability
| name | ceos-calendar |
| description | Use when managing the rolling market calendar - conferences, launches, fundraising milestones, partner events, and team constraints |
| file-access | ["data/calendar/","templates/calendar-events.md","data/vision.md","data/rocks/","data/accountability.md"] |
| tools-used | ["Read","Write","Glob"] |
Manage the rolling 6-month market calendar — external events, partner milestones, fundraising deadlines, and team constraints that affect quarterly planning and Rocks.
Search upward from the current directory for the .ceos marker file. This file marks the root of the CEOS repository.
If .ceos is not found, stop and tell the user: "Not in a CEOS repository. Clone your CEOS repo and run setup.sh first."
Sync before use: Once you find the CEOS root, run git -C <ceos_root> pull --ff-only --quiet 2>/dev/null to get the latest data from teammates. If it fails (conflict or offline), continue silently with local data.
| File | Purpose |
|---|---|
data/calendar/events.md | Market calendar events (dates, types, owners, status) |
templates/calendar-events.md | Template for initial calendar file |
data/vision.md | Strategic context for event relevance |
data/rocks/QUARTER/ | Current Rocks for alignment checks |
data/accountability.md | Seat owners for event-owner validation |
Events are stored in a single markdown table in data/calendar/events.md. Each row is one event:
| Field | Type | Required | Description |
|---|---|---|---|
| Date | YYYY-MM-DD | Yes | Event date (ISO 8601) |
| Event | string | Yes | Short event name |
| Type | enum | Yes | partner, market, fundraising, constraint |
| Owner | string | Yes | Person responsible, or "Team" for constraints |
| Status | enum | Yes | upcoming, past, cancelled |
| Notes | string | No | Brief context or outcome |
Type values:
partner — partner milestones, reviews, joint eventsmarket — conferences, industry events, product launchesfundraising — investor meetings, round targets, pitch deadlinesconstraint — team-wide holidays, office closures, blackout periodsStatus values:
upcoming — event has not occurred yetpast — event has passed (update notes with outcome)cancelled — event was cancelled or no longer relevantSorting: Rows are sorted chronologically by Date, oldest first.
Use when the user wants to see upcoming events or review the calendar.
Read data/calendar/events.md and parse the events table.
Compute the rolling window: 3 months before today through 3 months after today. Filter events to this window.
Group events by month and display:
Market Calendar (Dec 2025 - Jun 2026)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
January 2026
15 CES 2026 [market] — Ryan Martens (past)
Attended; explored AI agent partnerships
March 2026
08 GHC Registration Deadline [partner] — Dan Forman (upcoming)
31 Seed Round Close Target [fundraising] — Ryan Martens (upcoming)
April 2026
10 AnitaB.org Quarterly Review [partner] — Dan Forman (upcoming)
Read data/rocks/[current-quarter]/ and highlight any events that relate to current Rocks. For example, if a Rock is "Raise $2.5M Seed Round" and there's a fundraising event, note the connection.
Use when creating new calendar events.
For each event, collect:
YYYY-MM-DD)partner, market, fundraising, constraintdata/accountability.md (or is "Team" for constraints)Read the existing events table. Insert the new row at the correct chronological position.
Show the user the updated table with the new row highlighted. Ask: "Add this event?"
If approved, write data/calendar/events.md.
Ask: "Add another event, or are we done?"
When finished, display a summary of events added this session.
Use when changing event status, editing details, or removing events.
Show all events (not just the rolling window) so the user can find what they want to update.
Common updates:
past (add outcome to notes) or cancelledShow the specific row changes. Ask: "Update this event?"
If approved, write data/calendar/events.md.
View: Calendar grouped by month with type tags and status indicators. Past events dimmed. Upcoming events within 2 weeks highlighted. Rock cross-references noted. Add: Show the new row in context. End with a summary of events added. Update: Show the diff of changed fields. Confirm before writing.
data/calendar/events.md without showing the change and getting approval.partner, market, fundraising, constraint. If the user provides another type, show the allowed values and ask which fits.YYYY-MM-DD format and confirm.ceos-rocks and ceos-quarterly-planning when relevant, but let the user decide when to switch.ceos-calendar before finalizing Rocks."ceos-calendar reads data/accountability.md to validate that event owners match seat responsibilities.Only ceos-calendar writes to data/calendar/events.md. Other skills read calendar data for reference.