phronesis

The Phronesis CLI. Ports the pming scaffold (ESM + enquirer/chalk/fs-extra/slugify) forward to the three-layer installation layout, leaving pming's two-layer context/ assumptions behind.

Usage

npx phronesis init [dir]            # default dir: phronesis-installation
npx phronesis init . --force        # replace a non-empty target
npx phronesis init . --domain pm    # choose the domain workspace (default: pm)

# Minimal operator profile (fills USER.md + AGENTS.md §1; no [Name]/[Role] dead air):
npx phronesis init . --name "Ada Lovelace" --role "Founder"
#   optional, USER.md-only:  --company "Analytical Engines"  --working-style "async, terse"
#   On a terminal, a missing --name/--role is prompted. A non-interactive (scripted/CI) init
#   never prompts or blocks — it completes and leaves the placeholders.

The published V1.0 package exposes only the phronesis binary; pming remains the historical reference name, not a public install alias.

What init creates (specs/workspace-substrate.md)

<dir>/
├── codex/            Layer 3 — shared across all domains (seed/ + personal/)
├── domains/
│   └── pm/           a domain workspace
│       ├── raw/      Layer 1 — append-only source material
│       ├── compiled/ Layer 2 — durable current state
│       ├── memory/   session-scoped working memory
│       └── exports/  disposable renders
├── skills/
└── .phronesis/       runtime + configuration (registry.json)

Source of truth is the folder: plain Markdown, no database, no upload step.

Scope

init only — the three-layer structure (core-0001 / T1.1). Deliberately deferred to later packets:

• Session-file content — AGENTS.md, the CLAUDE.md / .cursorrules symlinks, USER.md, MEMORY.md, codex/INDEX.md (T1.2).
• Immutable PM-shaped seed principles in codex/seed/ (T5.4).
• Daemon (phronesisd), hooks, action types, event log (T2.x / T4.x).
• MIGRATION.md for existing pming workspaces (T1.x follow-up).

Tests

npm run -w phronesis test           # node --test: asserts the generated layout
npm run -w phronesis sync-package-assets

The same end-to-end scaffold is exercised by harness/fitness/validate-workspace, which graduated from a docs-only stub to enforcing the export-shape invariant (plain folders, no legacy context/) once this CLI landed. Model-swap and skill-portability stay PENDING until the compile/retrieve loop exists (ADR 0001).

sync-package-assets refreshes the tracked publish assets from their canonical sources: root skills/ into templates/skills/, and packages/core into vendor/core. The fitness gate fails if either tracked copy drifts.