project-os19.3 KB
View saved version →
---
name: project-os
description: Use this when Codex engineering work must survive multiple sessions, preserve verified repository state or transfer reviewed failure lessons between the user's own projects. Explain, inspect, bootstrap, adopt, validate, upgrade or maintain the repository-local control plane. ChatGPT is a companion for explanations, supplied project files and portable knowledge bundles. Do not use for ordinary one-session coding, generic project management or automatic global knowledge sharing.
---
# Project OS
Engineering Project OS was built for Codex. Create and maintain a small repository control plane that lets Codex resume real engineering work from visible state without changing application behavior unless the user separately asks for application work. ChatGPT can use the same skill as a companion over project material supplied in the conversation.
## Invocation boundary
In Codex, `$project-os` explicitly selects the bundled skill. In ChatGPT, `@Engineering Project OS` explicitly selects the plugin or bundled skill. The request text is ordinary natural language in any language. It is not a shell command, environment variable, rigid command grammar or persistent mode.
Installing the plugin makes the skill available in Codex and exposes its companion workflow in ChatGPT. It does not modify a repository. Once Project OS is connected, ordinary Codex engineering requests follow applicable `AGENTS.md` instructions without requiring `$project-os`.
Use this skill only for Project OS requests. The host may expose it automatically when the installed plugin is selected or the request clearly matches, but do not apply it to unrelated coding work.
Before inspecting or changing a repository, identify the available project input. In Codex, use the repository workspace selected for the current task and accept an explicit path to another schema 5 repository as a read-only knowledge source. In ChatGPT, setup advice and a new starter package may begin from the user's project description, selected project files or an archive provided in the current chat. Ask only for the missing details required to choose a safe setup and mark conclusions that are not backed by files as unverified. Reviewing, validating, repairing, adopting or upgrading an existing Project OS setup requires the relevant repository files, normally `AGENTS.md` and `.agents/`; ask for them when they are missing. Knowledge import requires an approved reusable bundle plus the destination Project OS context. Knowledge export requires the source reusable registry. Never inspect an empty host workspace or claim that the plugin is unavailable. Installation alone does not attach or connect a repository on either surface.
## Recovery capabilities
Identify readable project files, the selected helper and permitted execution before choosing a recovery route. When helper execution is available and allowed, use the compact inspection below. If the selected older helper genuinely lacks `brief`, keep that helper selected, run its supported `check` and `checkpoint --check` commands and read the configured record owners. Disclose unsupported checks. If a required validation or writeback command is also unsupported, leave that operation incomplete and request a suitable selected helper. A failed integrity check is not an older-helper compatibility case; never silently substitute another helper.
For read-only Python checks, use `python3 -B` or `PYTHONDONTWRITEBYTECODE=1`, including inline helper imports. Compare each protected tree's complete path set and file hashes before and after execution; an added `__pycache__` is a mutation. Preserve existing caches and required input files rather than deleting or excluding them to hide a mismatch.
When execution is unavailable or forbidden, or the selected helper is missing, inspect only readable supplied files. Describe recorded work and permissions as file-derived observations; mark integrity, checkpoint freshness and readin
Preview of the first 4,000 characters. Read full instructions →
Referenced files: 37 — file references are metadata, not package contents.
