소스 정보
- 저장소
- bradfeld/ceos
- 최근 소스 활동
- 2026년 2월 19일 15:44
- 감지된 SKILL.md 언어
- 영어
- 스타
- 144
- 포크
- 57
설치 방법
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
소스 파일 검토
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
메뉴
기본적으로 소스를 먼저 확인하는 Prompt가 선택됩니다. 직접 명령으로 전환하거나 로컬 사본을 다운로드할 수도 있습니다.
설치 여부를 결정하기 전에 SKILL.md와 SkillsMP에 표시된 보조 파일을 읽어 보세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/bradfeld/ceos --skill ceos-process명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
SOC 직업 분류 기준
SKILL.md 표시 중
| name | ceos-process |
| description | Use when documenting core processes or reviewing process followability |
| file-access | ["data/processes/","templates/process.md","data/vision.md","data/accountability.md"] |
| tools-used | ["Read","Write","Glob"] |
Document, simplify, and audit core company processes — the 6th EOS component. Every company has a handful of core processes that must be documented as checklists, simplified to their essential steps, and followed by all.
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/processes/ | Process documentation files |
data/vision.md | V/TO document (Core Focus and Proven Process for alignment) |
templates/process.md | Template for creating new process files |
data/accountability.md | Accountability Chart (seat owners for process-owner alignment) |
Each process is a markdown file with YAML frontmatter:
id: process-001
title: "Customer Onboarding"
owner: "brad"
fba_score: 85
last_audited: "2026-02-14"
status: active # draft | active | deprecated
created: "2026-01-15"
Status values:
draft — being documented, not yet in useactive — documented and in use, subject to FBA auditsdeprecated — no longer followed (kept for historical reference)File naming: process-NNN-slug.md where NNN is a zero-padded ID and slug is the title slugified (lowercase, hyphens, no special chars).
FBA (Followed-By-All) score: A percentage from 0-100 representing how consistently the team follows the documented process. Target: 80%+.
Use when creating a new process or updating an existing one.
Check the user's request:
For updates, read the existing process file, display the current content, and discuss what needs to change.
Before creating a new process, read and briefly reference:
data/vision.md — processes should align with how the company operatesdata/processes/ — avoid duplicates and ensure coverageDisplay a quick summary: "You currently have N documented processes: [titles]."
For a new process, collect:
For the steps, guide the user:
data/accountability.md. The owner should hold the seat whose responsibilities align with the process's domain. Flag mismatches: "This process falls under [Seat] responsibilities. Should [Seat Owner] own it?"Read existing process files in data/processes/. Find the highest process-NNN ID and increment. If no files exist, start at process-001.
Use templates/process.md as the template. Substitute:
Write to data/processes/process-NNN-slug.md.
Show the user the complete file before writing. Ask: "Create this process?"
Ask: "Create another process, or are we done for now?"
When finished, display a summary table of all documented processes:
| Process | Owner | Status | FBA |
|---|---|---|---|
| Customer Onboarding | brad | active | 85% |
| Sales Process | daniel | draft | — |
Use for reviewing FBA scores across all documented processes.
Read all process files from data/processes/. Parse the frontmatter for status, FBA score, and last audited date.
If no process files exist, display: "No processes documented yet. Use 'document a process' to create your first core process."
Show a status table of all processes:
| Process | Owner | Status | FBA | Last Audited |
|---|---|---|---|---|
| Customer Onboarding | brad | active | 85% | 2026-01-15 |
| Sales Process | daniel | active | 70% | 2025-12-01 |
| Deployment Pipeline | brad | active | 95% | 2026-02-01 |
Flag processes that need attention:
Offer to update scores: "Want to update any FBA scores?"
For each score update:
For each updated process:
fba_score in frontmatterlast_audited to today's date- YYYY-MM-DD: FBA audit — score updated to NN%If the user asks how to determine FBA scores, suggest:
Use to reduce a process to its essential steps — the 20% of steps that produce 80% of results.
If the user named a specific process, load it. Otherwise, list all processes and ask which one to simplify.
Show all current steps with numbering:
Current steps for "Customer Onboarding" (12 steps):
1. Send welcome email
2. Schedule kickoff call
3. Prepare onboarding packet
4. Run kickoff call
5. Set up user account
6. Send login credentials
7. Schedule training session
8. Run training session
9. Check in after 24 hours
10. Check in after 1 week
11. Send satisfaction survey
12. Review survey results
Guide the user through simplification:
"The 20/80 rule says roughly 20% of these steps produce 80% of the value. Which steps are absolutely essential — the ones that, if skipped, would break the process?"
Walk through each step and ask: "Keep or remove?"
For each step:
Display before and after:
Simplified "Customer Onboarding": 12 → 7 steps
Removed:
3. Prepare onboarding packet
9. Check in after 24 hours
11. Send satisfaction survey
12. Review survey results
Kept:
1. Send welcome email
2. Schedule kickoff call
4. Run kickoff call
5. Set up user account
6. Send login credentials
7. Schedule training session
8. Run training session
Show the complete updated file. Ask: "Apply this simplification?"
If approved:
- YYYY-MM-DD: Simplified from N to M stepsAfter simplification: "The process has changed — consider re-auditing FBA scores next week to see if the simplified version is easier to follow."
Document mode: Show the complete process file before writing. End with a summary table of all processes. Audit mode: FBA status table with highlighting for processes below target or overdue for audit. Simplify mode: Before/after diff of the step list, then the complete updated file.
data/vision.md. Processes should align with how the company operates.deprecated instead. Git history provides the audit trail.ceos-vto when relevant for Core Focus alignment, but let the user decide when to switch workflows.This skill manages process documentation independently. No other CEOS skills read from or write to data/processes/.
ceos-process reads data/vision.md for Core Focus and Proven Process alignment when documenting new processes. It does not write to the V/TO file.ceos-vto.ceos-process reads data/accountability.md when documenting or auditing processes to validate that process owners match seat responsibilities. A sales process should be owned by whoever holds the Sales & Marketing seat; a delivery process by the Delivery seat owner.Unlike other EOS components that cross-reference each other (Rocks → V/TO, Scorecard → L10), core processes are standalone documentation. They reference the V/TO for alignment and the Accountability Chart for owner validation, but there are no formal data dependencies between process files and other CEOS data files.