Menú
CEO-only: publish workspace content to all executives via the corporate repo. EXPLICIT INVOCATION ONLY - never auto-trigger.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Backup the entire workspace to GitHub. EXPLICIT INVOCATION ONLY - never auto-trigger from natural language.
CEO-only: Push all workspace updates to all executives. Single command that commits, classifies, publishes to corporate repo, bumps BUILD.json, pushes CRM, aggregates CRM, syncs exec workspaces, and reports. EXPLICIT INVOCATION ONLY - never auto-trigger.
Manually trigger workspace sync - git pull of the code/data clones, then a push-all backup. EXPLICIT INVOCATION ONLY - never auto-trigger.
Pre-implementation gate: recommended structured checkpoint between plan approval and /implement. Use before any non-trivial implementation: combines success-criteria definition, an inline contrarian stress-test (the /devil discipline), an optional /council architecture review with Kimi as devil's advocate, harness gap audit, and test-contract writing. Produces a GO/NO-GO artifact with a ready-to-paste /implement prompt. Skip for trivial one-liner fixes, typo corrections, and config-only changes.
Ultrathink principal-engineer review gate. Runs a Validate-Identify-Improve-Adjust (VIIA) pass over a target - a plan awaiting approval, just-executed work, a specific file or directory, or the entire workspace - then runs an adversarial refutation layer (Phase 2.5) with cross-family judge rotation (Claude and Kimi k3) and optional two-agent debate on BLOCKER + HIGH findings before presenting findings with concrete proposed fixes for batched approval. Blocks forward progress until approved. Triggers on "scrutinize", "stress-test this", "principal review", "validate and improve", "review the plan before I approve", "audit what you just did", "ultrathink review". Do NOT trigger for artifact grading alone (use /evaluate), fact-checking drafts (use /validate), or strategic reasoning (use /deep-think). Usage: /scrutinize [plan | execution | file:<path> | dir:<path> | workspace | trajectory:<run_id>] [--relentless] [--no-refute] [--include-low-confidence] [--include-ambiguous]
Second-opinion advisor. Default roster is Kimi k3 alongside Claude's own view; Gemini and Grok are opt-in via --gemini / --grok / --all. Two modes: independent (the models see the problem only, reason fresh) and critique (they stress-test a draft). Distinct from /deep-think (Claude reasoning structured, alone) and /odin (Claude + the curated knowledge brain). Trigger when the user says: "council", "/council", "second opinion on", "consult the council", "what would Gemini/Grok/Kimi say about", "stress-test this with Gemini/Grok/Kimi", "council vote".
| name | publish-corporate |
| disable-model-invocation | true |
| description | CEO-only: publish workspace content to all executives via the corporate repo. EXPLICIT INVOCATION ONLY - never auto-trigger. |
| metadata | {"author":"Misha Hanin","email":"misha.hanin@odinix.com","version":"1.1"} |
| argument-hint | [description of what to publish] |
| allowed-tools | Read, Write, Edit, Bash(python3:*), Bash(git:*), Glob, Grep |
| model | haiku |
| x-heading-orchestration | {"parallel_safe":false,"shared_state":["../heading-os-corporate/"],"triggers":["publish corporate","publish to executives","push to corporate"]} |
| x-heading-capability | {"what":"CEO-only: copies corporate-classified content from the DATA overlay (.heading-os-data) to the ../heading-os-corporate/ repo and pushes, so execs pull it with plain `git pull` (git-native; no scheduled hourly sync).\n","how":"Explicit invocation only - type /publish-corporate [what to publish]; never auto-triggers. It verifies admin role, runs a critical-leak scan, previews the file set for confirmation, then copies, commits, and pushes.\n","when":"Use for targeted selective publishing to executives. For a full versioned push including BUILD.json and CRM aggregate use /push-updates; for a personal workspace backup use /backup.\n"} |
| x-heading-routing | {"category":"Operations","triggers":["NEVER auto-trigger. Explicit `/publish-corporate` only."],"exclusions":["Full push with CRM -> /push-updates"],"compound":"No","router":"manual"} |
CEO-only skill. Copies corporate-classified content from the DATA overlay (.heading-os-data) to the heading-os-corporate repo for distribution to all executives. Canonical mechanism:
python scripts/publish-corporate.py --preview|--copy|--verify(reads the source from the data overlay, writes to ../heading-os-corporate/). Execs pull with plaingit pull— there is no scheduled sync.
.workspace-identity.json - verify role is "admin". If not, say "This skill is CEO-only." and stop.../heading-os-corporate/. If not, say "Corporate repo not found. Run initial setup first." and stop.$ARGUMENTS - Description of what to publish (e.g., "Updated strategy for Q2", "New competitor-intel skill", "Updated a competing vendor competitive document")Based on $ARGUMENTS, identify which files in ceo-main should be copied to the corporate repo.
Classification-driven publishing: classification resolves from config/routing-map.yaml (the single input; classification.json was removed in HEADING OS step 7). Post-cutover (step 8, 2026-06-14) publish ships ONLY files whose three-value routing destination is corporate — content, not code. Engine code is NOT published here; execs receive it by cloning the engine repo (.heading-os). The corporate set is content-only: datastore/, knowledge/shared/, the two context/ carve-outs, crm/ config/aliases/address-book, corporate/ daemon config. Use python scripts/classification-health.py --corporate-only to list it.
If $ARGUMENTS references a specific file currently classified as ceo-only (routed private), warn the CEO and ask if they want to reclassify it before publishing (add a rule to config/routing-map.yaml).
NEVER publish (safety check - overrides classification):
context/personal-info.md (CEO personal)context/people.md (CEO contacts)crm/contacts/* (CEO CRM data)datastore/books/* (CEO personal library)knowledge/fleeting/*, knowledge/meetings/*, knowledge/people/* (personal knowledge)knowledge/technology/*osint-api-credentials* (API keys).env (secrets).workspace-identity.json (per-workspace)outputs/* (CEO deliverables)threads/ (entire directory) - operational thread registry, ceo-only on every machinethreads/personal/** - explicitly listed even though covered by parent (defence in depth)private in config/routing-map.yaml (CEO-personal tooling — e.g. modem-tune.py, the fireside/service-host scripts, the one-off CEO-instance scripts, plus anything added later). Single source of truth: scripts.utils.workspace.get_ceo_only_scripts().Note: For full end-to-end push with BUILD.json versioning, use
/push-updatesinstead. This skill is for targeted selective publishing.
Show the user a clear list:
Files to publish to all executives:
1. context/strategy.md (modified 2026-03-19)
2. .claude/skills/competitor-intel/SKILL.md (new)
...
This will be available to executives the next time they run `git pull` on their corporate clone (git-native; no scheduled task).
Ask for confirmation: "Publish these files? (yes/no)"
Before copying, run the shared critical-leak scanner on every file in the publish set:
python scripts/sanitize-check.py <file1> <file2> ...
The scanner uses the primitives in scripts/utils/sanitize.py. It flags the narrow set of terms that must never land in corporate (vault codenames, ceo-only paths, private contact markers). On exit code 1, stop - surface the findings, ask the CEO to fix the source files, do not proceed to Step 3.
cd to corporate repo directorygit add -Agit diff --cached --stat to show what changed"Publish: {description from arguments}"VERSION file in corporate repoCHANGELOG.md:
## [1.0.1] - 2026-03-19
- {description from arguments}
- Files: {list of changed files}
"Bump version to 1.0.1""Published to the corporate repo. Executives will receive these updates the next time they run git pull on their corporate clone."