Use when reviewing or updating the company Vision/Traction Organizer
Review and update the Vision/Traction Organizer (V/TO) — the single document that captures where your company is going and how it plans to get there.
Search upward from the current directory for the .ceos marker file. This file marks the root of the CEOS repository.
current_dir → parent → parent → ... until .ceos found
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/vision.md | The V/TO document (source of truth) |
data/accountability.md | Who owns what (reference for role alignment) |
data/rocks/ | Current quarter's Rocks (for alignment checks) |
templates/vision.md | Template structure (reference only) |
The V/TO has 8 sections, each covering a different planning horizon:
| Section | Horizon | Key Question |
|---|---|---|
| Core Values | Permanent | What do we stand for? |
| Core Focus | Permanent | Why do we exist? What's our niche? |
| 10-Year Target | 10 years | What's our big audacious goal? |
| Marketing Strategy | Ongoing | Who do we serve? How are we different? |
| 3-Year Picture | 3 years | What does the company look like? |
| 1-Year Plan | 1 year | What must be true in 12 months? |
| Quarterly Rocks | 90 days | See data/rocks/ (managed by ceos-rocks) |
| Issues List | Ongoing | See data/issues/ (managed by ceos-ids) |
Read data/vision.md from the CEOS repository root. If the file doesn't exist, tell the user to run setup.sh init first.
Display a summary of the current state:
| User Intent | Action |
|---|---|
| "Review the V/TO" | Display full document, ask which sections to discuss |
| "Update [section]" | Jump to that section for editing |
| "Check alignment" | Cross-reference Rocks against 1-Year Plan |
| "What's our [specific item]?" | Read and present that section |
When the user wants to change a section:
data/vision.md with the approved changeWhen reviewing the V/TO or when specifically asked about alignment:
data/vision.mddata/rocks/[current-quarter]/Report findings clearly:
Alignment Check:
- 4/5 Rocks map to 1-Year Plan goals ✓
- Rock "Build Mobile App" doesn't connect to any 1-Year goal ⚠️
- 1-Year goal "Expand to 3 new markets" has no supporting Rock ⚠️
After any update:
git commit to save this update"When displaying the V/TO, use the document's existing markdown structure. For updates, show a clear before/after diff of the changed section only (not the entire document).
For alignment checks, use the summary format shown in Step 4.
data/vision.md without showing the user what will change and getting explicit approval.data/rocks/ and data/issues/. Direct the user to ceos-rocks or ceos-ids for those.ceos-rocks, ceos-ids, and ceos-annual when relevant, but let the user decide when to switch workflows.ceos-rocks reads the 1-Year Plan section from data/vision.md when setting Rocks to check alignment. Each Rock should connect to a 1-Year Plan goal.ceos-rocks Tracking mode."ceos-people reads Core Values from data/vision.md to evaluate team members against the company's values.ceos-people."ceos-annual facilitates a full V/TO refresh during the annual planning session. The annual skill guides the team through updating each section.ceos-quarterly references V/TO goals during quarterly conversations to assess alignment between individual performance and company direction.Only ceos-vto writes to data/vision.md. Other skills read it for reference (Core Values, 1-Year Plan, Core Focus). The annual planning session is the one structured time to do a full V/TO refresh, but ad-hoc updates via ceos-vto are appropriate for corrections and minor changes.