메뉴
Build, run, and drive pi-project-workflows. Use when asked to run the pi-context CLI, start or smoke-test the monorepo, exercise the pi extensions via tool dispatch, verify a build end-to-end, or check that the substrate tooling works on this machine.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Schema-driven project state management with typed JSON blocks, schema validation, substrate config, lens views, closure-table relations, and cross-block referential integrity. Use when managing substrate blocks, scaffolding project structure, installing block kinds from the packaged samples catalog, validating project state, rendering lens views, or adding work items.
Orchestrates multi-step agent workflows defined in YAML with DAG-based execution, typed data flow, checkpoint/resume, and output validation. Use when running workflows, authoring workflow specs, debugging step failures, or inspecting agent configurations.
Sibling Pi extension that registers in-pi agent-as-tool dispatch, capability composition, real-check execution, attested commits, and the bounded north-star work-order loop. Use when authoring agent specs, granting tool capabilities, running deterministic checks, committing with writer attestation, loading config-declared composite operations, or driving end-to-end work-orders through their bounded retry loop.
Meta-package re-exporting pi-context (schema-driven project state), pi-workflows (workflow orchestration), and pi-behavior-monitors (autonomous behavior monitoring). Install once to get all three extensions.
Audit the active pi-context substrate for currency — stored-vs-derived status divergence, fired stale-conditions, lagging feature/gap buckets, stale filing text — and enact user-granted corrections. Use when asked to confirm substrate currency or accuracy, run a currency audit, check for stale statuses, or reconcile substrate state with shipped reality.
Cut a release of the pi-project-workflows monorepo — lockstep version bump, CHANGELOG roll, tag, operator promote, credentialed verification, and the publish/push handoff. Use when asked to release, cut a version, bump and tag the monorepo, or prepare a publish.
| name | run-pi-project-workflows |
| description | Build, run, and drive pi-project-workflows. Use when asked to run the pi-context CLI, start or smoke-test the monorepo, exercise the pi extensions via tool dispatch, verify a build end-to-end, or check that the substrate tooling works on this machine. |
This monorepo ships two deployable surfaces from one lockstep build: the pi-context CLI (a binary) and a set of pi-runtime extensions (loaded by the pi agent runtime from this tree per package.json pi.extensions). Drive both via .claude/skills/run-pi-project-workflows/driver.mjs — it builds, installs the CLI into a throwaway prefix, and exercises each surface against the repo's live .context substrate, read-only.
All paths are relative to the repo root.
node --version; CI matrix). No OS packages beyond that — the build is pure tsc.pi CLI on PATH and ~/.pi/agent/auth.json (model credentials). Without them that step reports GATED and everything else still runs.npm install
node .claude/skills/run-pi-project-workflows/driver.mjs
What it does, in order (each step prints PASS/FAIL/GATED; exits non-zero on first FAIL):
npm run promote:cli with PROMOTE_PREFIX at a throwaway dir: builds the whole tree and installs the packed CLI there (~90s). This is the same mechanism that installs the real operator binary; the throwaway prefix keeps the machine's global untouched.--version (must match the tree version), context-bootstrap-state (substrate resolves, state: ready), context-validate (verdict returned), read-config --registry block_kinds --id tasks (one registry entry addressed).pi -p "call the context-status tool once and then stop" --mode json --no-skills --model openrouter/anthropic/claude-haiku-4.5) proving the extensions load from this tree and a tool round-trips. Spends real (haiku-priced) credits; GATED when pi or auth.json is absent.Flags:
node .claude/skills/run-pi-project-workflows/driver.mjs --skip-promote # reuse the last prefix (skips the ~90s build)
node .claude/skills/run-pi-project-workflows/driver.mjs --full # also run the full test suite
Most changes here touch library internals, not the binary. Call them straight off the built dist:
npm run build
npx tsx -e "import {contextState} from '@davidorex/pi-context/context-sdk'; console.log(JSON.stringify(contextState('.').position ?? 'ok'))"
Workspace subpath imports (@davidorex/pi-context/context-sdk, /block-api, …) resolve to this tree's dist/ via workspaces — rebuild before invoking (pi and the CLI load dist/, never src/).
The operator installs the CLI into the real global prefix:
npm run promote:cli # then: pi-context <op> --json
A npm run release:* run does this automatically as its final step.
npm test # tsx --test + vitest across all packages; must be 0 failures
npm run check # biome + tsc --noEmit
--tools read on pi -p restricts to BUILTINS — extension tools (context-status etc.) disappear and the model reports "I don't have that tool". Omit --tools for extension dispatch; pin --model openrouter/anthropic/claude-haiku-4.5 and --no-skills for cost control..context is a live substrate with enforcement hooks (PreToolUse guards fire repo-wide in Claude Code sessions). The driver is read-only against it by design; don't add write steps to it — sanctioned writes go through the pi-context ops with --writer, and planning-block writes are provenance-gated.execSync + stdio: "inherit" returns null on success AND failure — the driver pipes output instead so success is discriminable (the same hazard bit scripts/release.mjs step 5 during its implementation).pi-context can lag the tree after edits — it's a packed copy, not a link. Re-run npm run promote:cli (releases self-promote since v0.32.0).context-validate returning warnings is the healthy steady state here (a known pre-existing advisory backlog); invalid is the red flag.binary reports '…', tree is X from the version step → a stale prefix was reused; run without --skip-promote.--skip-promote: no prior prefix found → first run must do the promote; drop the flag.pi CLI and/or provision ~/.pi/agent/auth.json; everything else has already verified the build.npm run promote:cli fails with EACCES on a real-global install → your npm global prefix isn't writable; the driver never hits this (throwaway prefix), only the human path does.