ceo
/ceo
Prowadzi Critical Engineer Orchestrator z biurka: status, otwarte pytania, zatwierdzenia i nowe plany w schemacie critical-engineer.
- Autor
- critical-engineer ↗
- Repozytorium
- critical-engineer-orchestrator ↗
- Licencja
- Apache-2.0
- Ostatnia zmiana repozytorium
- 06.11.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 06.11.2026, bez odwołań do wycofanych modeli i API.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
Co robi i kiedy
Prowadzi Critical Engineer Orchestrator z biurka: status, otwarte pytania, zatwierdzenia i nowe plany w schemacie critical-engineer.
Oryginalny opis (EN)
Drive the Critical Engineer Orchestrator (CEO) from the desk. Use when the engineer asks about CEO status, open questions or approvals, wants to answer or approve something CEO asked, or wants to start a new CEO plan (an OpenSpec change with the critical-engineer schema).
Jak działa
- Commands
- Starting a plan
Podgląd SKILL.md
--- name: ceo description: Drive the Critical Engineer Orchestrator (CEO) from the desk. Use when the engineer asks about CEO status, open questions or approvals, wants to answer or approve something CEO asked, or wants to start a new CEO plan (an OpenSpec change with the critical-engineer schema). --- # CEO skill You help the **Critical Engineer** drive CEO: an orchestrator where an approved plan, not a ticket, coordinates work. The engineer owns judgment; you help them see clearly. **You never decide for them.** Never answer a question or approve a gate on your own initiative. Only run `answer` with words the engineer has given you for that question. CEO runs on a box the engineer reaches over SSH. The engineer's SSH config has a host (below: `ceo-box`) whose key is pinned to CEO's command entry point, so only these commands work and the engineer's identity comes from the key. ## Commands | Command | Use | |---|---| | `ssh ceo-box status` | Plans, task counts by status, open gates and questions (JSON) | | `ssh ceo-box questions` | Open questions; a gate question includes the exact payload and its SHA-256 (JSON) | | `ssh ceo-box answer <n> <text...>` | Answer Q<n> with the engineer's words | For a **gate** question (it has a `gate` field) the only valid answers are `approve` or `deny <reason>`. Before the engineer decides, help them judge it: 1. Show the gate's `kind` and its exact `payload`. Don't paraphrase it away. 2. Point at what could be wrong, with locations where you can: a flawed design, a concurrency or consistency assumption, a constraint nobody encoded, an assumption the plan never sanctioned. Say how confident you are. Then stop: the engineer decides. 3. A denial needs a reason; it goes back to the worker, so make it specific. ## Starting a plan Plans live in the engineer's repo as OpenSpec changes using the `critical-engineer` schema. Run these locally, not on the box: 1. `openspec new change <name>` (with telemetry off: `OPENSPEC_TELEMETRY=0`). 2. Fill the artifacts the schema asks for. In `design.md` every constraint is `C<n>`, every failure mode row names a constraint, decision or task as its mitigation, and every decision `D<n>` lists what was rejected and why. 3. Write tasks a **small model** can execute: small, specific about where they work, each with a meaningful `check` in `ceo.yaml`. A task a small model can't do is a planning failure. 4. Validate: `openspec validate <name> --strict`, then `python -m ceo.validate openspec/changes/<name>`. 5. Open a PR. Approval is the engineer merging it to protected `main`.
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · critical-engineer/critical-engineer-orchestrator | 90 | Apache-2.0 |
| tamnguyendinh/Anvien | 100 | MIT |
| dudwns0921/claude-gamedev-kit | 100 | MIT |
| AtlasScope/agent-kit | 95 | MIT |
| iankiku/forwward-teams | 90 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki 772e2043f0ee (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 96ceo-delegation
Prowadzi pracę w stylu CEO: zamiast wykonywać zadanie samodzielnie, deleguje je podagentom, monitoruje postęp, raportuje i odbiera wyniki, co pomaga przy równoległym przetwarzaniu wielu zadań. - 100yourteam
Uruchamia zespół wielu agentów AI, od CEO po QA, który buduje produkt etapami, z panelem w przeglądarce. - 100l4
Daje skrótowe wejście CEO poziomu 4: uruchamia w tle jednego sub-orkiestratora izolowanego w worktree, który bez nadzoru prowadzi dev-flow i zwraca werdykt, a kontekst CEO pozostaje czysty. - 100ceo-loop
Prowadzi jedną iterację pętli decyzyjnej CEO w NXTG-Forge (OBSERVE, REASON, BUILD, INSPECT, TURN) i klasyfikuje oczekujące decyzje według głębokości, wpływu i odwracalności. - 90ceo-advisor
Daje strategiczne doradztwo na poziomie prezesa i weryfikuje założenia użytkownika co do kierunku, priorytetów i dużych decyzji. - 100ao-answer
Znajduje sesje Orchestratora czekające na odpowiedź użytkownika i pokazuje pytania oraz zatwierdzenia jako gotowe opcje do wyboru.