praxis-workflow

Praxis Workflow Plugin

Portable Praxis workflow package for Codex, Claude Code, and OMP.

The package keeps platform adapters thin. Shared Praxis rules, profile sync logic, IFC MOM/AOTU assets, RTK fallback guidance, and vendored Ponytail 4.8.4 assets live in one portable core. Project-specific facts stay in each workspace: praxis.projects.toml, branch names, paths, verification commands, database names, and requirement records are never sourced from the plugin.

Contents

• praxis.plugin.toml: shared plugin metadata rendered into platform adapters.
• .codex-plugin/plugin.json: Codex manifest for root skills/.
• .claude-plugin/plugin.json and .claude-plugin/marketplace.json: Claude Code manifest and local marketplace projection.
• package.json: OMP plugin entry with omp.extensions and omp.skills.
• skills/: Praxis, RTK, and vendored Ponytail skills.
• commands/*.toml: canonical command prompts; commands/*.md are generated for Markdown-command platforms.
• runtime/praxis_core/: platform-neutral task-policy and quick-task state contracts synced into workspaces.
• hooks/, pi-extension/, and adapters/omp/: Ponytail runtime plus Praxis session-start profile integration.
• profiles/: portable profile assets such as ifc-mom.
• scripts/: adapter generation, Ponytail vendoring, workspace init/check/sync scripts.
• templates/: project-neutral starter files and agent contracts.
• workspaces.local.json: ignored local registry for syncing this checkout to known workspaces.

Install locally

Codex:

uv run python scripts/praxis_build_adapters.py --check
uv run --with PyYAML python "$HOME/.codex/skills/.system/plugin-creator/scripts/validate_plugin.py" "$PWD"

Claude Code:

claude plugin validate "$PWD"
claude --plugin-dir "$PWD" --no-session-persistence -p "/praxis-help"

OMP:

omp plugin link "$PWD"
omp plugin doctor --json
omp plugin list --json

Remote OMP distribution after configuring and publishing a remote repository:

omp plugin install github:faustofanb/praxis

Do not publish an .omp-plugin/marketplace.json projection until OMP marketplace installs load package.json#omp.extensions; otherwise Ponytail runtime would be silently omitted.

Automatic workspace integration

After the plugin is installed and its lifecycle hook is trusted, opening an existing Praxis workspace automatically:

1. detects the workspace root from praxis.toml and praxis.projects.toml;
2. detects the installed packaged profile, such as ifc-mom;
3. compares only profile-managed files with the plugin copy;
4. repairs drift and prunes obsolete managed files under a PID lock;
5. leaves praxis.projects.toml, branches, database settings, requirements and business documents untouched.

Codex and Claude Code run the generated SessionStart hook from hooks/hooks.json. OMP runs adapters/omp/praxis-auto-sync.mjs and displays Praxis active · <profile> · <status>. Existing MOM/AOTU workspaces therefore do not need a manual profile-distribution command for each development session. A brand-new workspace still needs one initialization or an explicit profile marker.

Workspace opt-out:

# .praxis/plugin-sync.toml
schema_version = 1
id = "ifc-mom"
auto_sync = false

Codex custom instructions such as @~/.codex/RTK.md and @~/.codex/Praxis.md are no longer required after installing and trusting the plugin; keeping them would duplicate plugin rules. Workspace-local @AGENTS.md remains the source of project facts and should stay enabled.

Workspace operations

python scripts/praxis_check_workspace.py <workspace> --json
python scripts/praxis_init_workspace.py <workspace> --name "IFC MOM" --profile ifc-mom
python scripts/praxis_sync_profile.py <workspace> ifc-mom --force
python scripts/praxis_sync_workspaces.py ifc-mom --force --dry-run
python scripts/praxis_sync_workspaces.py ifc-mom --force

praxis_sync_workspaces.py resolves the registry in this order: explicit --registry, PRAXIS_WORKSPACES_REGISTRY, then root workspaces.local.json. Missing all three is a hard configuration error. Single-workspace praxis_sync_profile.py <workspace> <profile> does not require a registry.

Task modes

Workspace-local praxis.projects.toml remains the source of project paths, branches, commands and databases. Praxis adds two explicit execution modes:

# L0: isolated worktree + resumable .praxis/tasks/<id>.toml; no requirement docs
task project -- quick <project> <short-task-name>
task project -- quick-check <project> <short-task-name>

# L1/L2: retained requirement docs and the formal delivery lifecycle
task project -- start <project> <requirement-name> <original-user-request>