codex-work-os

codex-work-os is a practical work-system repository for Codex. It is built for situations where information arrives in fragments: loose meeting notes, partial research, half-formed support cases, unclear ownership, and unfinished reply drafts.

The goal is not to make Codex sound more confident. The goal is to help Codex turn unstructured work into reviewable drafts and structured artifacts such as sales replies, PM briefs, executive summaries, decision memos, and support escalations.

This repository is not primarily a prompt pack, not a generic PM framework, and not a random business templates library. It is a Codex-native operating layer for structured work.

This project is a strong fit for people who want Codex to help with operational work beyond coding and who prefer reusable working structure over one-off prompting.

• People who want sales, PM, research, executive, or support outputs to follow a stable shape.
• Teams using Codex in workflows where information is messy and work products need review before use.
• Builders who want flows, gates, and output types to be explicit rather than implied.
• Anyone who wants AI outputs that are easier to review, hand off, adapt, or archive.

It is a weaker fit if you are looking for a broad life-assistant prompt pack, a generic business advice library, or a coding-only helper repository.

codex-work-os is intentionally organized as a skills-first system. The primary unit is the domain pack under skills/, and the rest of the repository supports those packs.

There is no top-level playbooks/ directory because this repository is not built around one linear pipeline. It is built around reusable work domains.

The easiest way to use codex-work-os is to treat it as a structured system rather than a collection of unrelated files.

1. Start with README.md and AGENTS.md to understand the repository's operating model.
2. Read docs/architecture.md and docs/pack-mapping.md to understand how packs, flows, gates, and artifacts relate.
3. Open examples/end-to-end/pilot-rollout/ to see one messy situation move across multiple packs.
4. Choose the pack that matches your primary work type.
5. Apply the relevant flow, gate, and artifact when turning raw input into a draft deliverable.

If you only want the quickest overview, start with the end-to-end example. If you want to use the system in real work, read the architecture and pack mapping first, then move through the worked scenario.

The main worked scenario in this repository is pilot-rollout. It starts from a messy operational situation involving:

• a prospect asking for a lightweight pilot,
• an internal choice between two setup paths,
• unclear PM ownership, and
• a support issue involving intermittent missed alerts.

That one situation is then transformed into a research memo, a PM brief, an executive brief, a sales reply draft, and a CS escalation note.

This is the fastest way to understand what codex-work-os is trying to do: not just generate text, but reshape noisy work into reusable draft artifacts from multiple operational angles.

NicheWorks publishes small, practical tools and workflow assets intended to be useful in real work. codex-work-os fits that model as a working repository asset that can keep improving through stronger examples, better structure, and clearer operational use notes.

The repository opens on GitHub. GitHub's own terms, privacy policy, and availability apply.

If this page or repository helps your workflow, you can support future maintenance, documentation updates, and additional worked examples through the links below. OFUSE and Ko-fi are external services, and their own terms and privacy policies apply.