@nightink/pi-spec-flow0.5.0

Pi adapter: spec-flow lifecycle tools, notifications and the autonomous-delivery skill

nightink Published 1 day ago MIT ~295 downloads/mo

Untested on omp

This is a pi package. No one has reported whether it works on omp yet. If you try it, add your result below.

Reports 0

No reports yet.

Readme

@nightink/pi-spec-flow

Pi adapter for spec-flow: nine lifecycle/allocation/review tools, the /spec command, commit-gate interception and the bundled autonomous-delivery skill. The harness-neutral engine/CLI is a separate dependency, @nightink/spec-flow-core@^0.5.0.

Lazy discovery (0.5.0 candidate)

The nine original tool names and schemas remain available under the spec namespace. On current Pi they use deferred exposure: codemode searchTools("spec"), describeTool("spec_review") and describeNamespace("spec") load details on demand. Without active codemode/tool_search, session-local activation keeps tools accessible; no global settings are changed. Nested calls still pass validation, tool_call hooks, cancellation, paid-review authorization and the real attestation confirmation.

spec_new defaults to a meaningful filename and external verification; explicit numeric projects retain inline compatibility. spec_begin({id,rework:true}) starts a new delivery of a completed external Spec without inheriting approval or resetting budgets. Migrate legacy v2 state explicitly with core/CLI externalize first.

Install

Requires Node.js >=22.19.0, Git and a trusted Pi 1.x host. This source is the unpublished 0.5.0 candidate, requiring core ^0.5.0. Real SDK acceptance uses Pi 1.5.0; other host versions are not fully certified. Version 0.4.1 is an existing published release, not this candidate.

# Only after the maintainer publishes and verifies 0.5.0:
pi install npm:@nightink/pi-spec-flow@0.5.0
pi list
# In an existing Pi session, reload explicitly:
# /reload

Git installation is also supported via the private workspace root's Pi manifest. Do not install the root pi-spec-flow package from npm. Host-provided @earendil-works/pi-coding-agent and typebox are optional peers, not bundled dependencies; Pi supplies their module mappings. No build step is required for the TypeScript extension.

Use

Run /spec to inspect the project. The tools are spec_alloc, spec_new, spec_begin, spec_impl, spec_review, spec_audit, spec_attest, spec_done and spec_board. Use /skill:autonomous-delivery for the delivery workflow. Tools return typed structured results; impl/audit failures use isError, not success text containing an emoji.

The default v4 review checks the complete Spec and each acceptance, carrying the complete previous report and worker responses between rounds. It does not require paragraph coverage or restoration of private artifact chains. last_review and ordinary repository-relative previousReport JSON preserve continuity across agents/clones. Old review jobs keep their original interpretation.

spec_audit {action:"prepare",id} is free. Running a reviewer requires an existing, explicitly authorized finite grant; installation or simulation does not authorize paid calls. spec_attest requires actual human confirmation and evidence. Headless/declined confirmation never writes attestation. Static review is not runtime acceptance or completed delivery.

Commit interception executes the target project's real gates. It is a workflow guard, not a security sandbox: extensions run with the host's OS permissions. The adapter does not install target-project dependencies, alter host settings or restart production processes.

Release acceptance

The repository's npm run release:verify -- /absolute/local-output packs both npm packages, installs them outside the source tree, and checks exports/CLI, package discovery, real Pi tool execution, gate failures, UI/confirmation boundaries, synthetic-review attachment and three provider serializers. Supply SPECFLOW_PI_SDK pointing to an already-installed trusted Pi package; the verifier never installs a SDK or calls a model. Synthetic tool/reviewer inputs exercise plumbing, not model comprehension or real human verification.

The 0.5.0 candidate changes default creation/storage; it is a new minor, not an overwrite of published 0.4.1. Existing inline Specs remain compatible. Upgrade both the adapter and CLI/core before explicit externalize; old 0.4.x cannot read the new verification references. Never roll back by deleting those references or inventing approval. Publish core first, then this adapter. Registry authentication and publication remain maintainer actions. Tests on macOS/Linux do not certify Windows or a production daemon's loaded version.