@jwilger/pi-development-system 0.77.0 → 0.78.0

package/README.md

@@ -13,6 +13,18 @@ and adds per-spawn `model` and `thinkingLevel`. **Remove the original from the
 entry), then `/reload`; otherwise both register `agent_spawn` and pi refuses the
 duplicate.
 
+## You do not need the slash commands
+
+Everything the system offers is reachable without remembering a command. Describe the work in
+plain words: when a prompt asks for new work, a fix or a review, the system adds a guideline
+naming the tool to use (`devsys_intake`, `devsys_review_start`). A `devsys` tool always shows
+what the current phase expects. When you say a slice is finished with no review round recorded,
+it tells you to start one. The slash commands (`/devsys-start`, `/devsys-plan`, `/devsys-review`)
+are shortcuts to the same tools.
+
+With `codemode` enabled (`"defaultTools": ["+codemode"]` in pi settings), rarely used tools and
+the `judge_*` Jev wrappers are reached through scripts; without it they are declared directly.
+
 ## Development
 
 ```sh

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@jwilger/pi-development-system",
-  "version": "0.77.0",
+  "version": "0.78.0",
   "description": "A pi extension package representing a seasoned approach to software development using a full AI SDLC.",
   "keywords": [
     "pi-package"

package/skills/strict-lints/SKILL.md

@@ -42,6 +42,11 @@ A warning is an error that has not been triaged yet. Before every commit:
   is made type-clean and lint-clean, dropped from the list, and removed from the
   `!src/subagents/...` exclusions in `biome.json`.
 
+## Running all the checks at once
+
+`references/verify.md` has a codemode script that runs the project's checks in parallel and
+returns `{tool, exit, firstFailures}` for each. Prefer it to five separate calls.
+
 ## What the extension does
 
 Editing a file so that it adds `#[allow(`, `#[expect(`, `// biome-ignore`,

package/skills/strict-lints/references/verify.md

@@ -0,0 +1,36 @@
+# Verify script (codemode)
+
+Run every check the project has in one go, in parallel, and get back only what failed.
+Paste this into the `codemode` tool. Each nested `bash` call still passes through the
+development-system guards, and the test-evidence tracker records each run, so a green result
+here is evidence a later "all checks pass" claim can rest on.
+
+Adjust `CHECKS` to the project profile (see the profile skill: TypeScript, Rust, ...).
+
+```js
+const CHECKS = [
+  { tool: "tsc", command: "npx tsc --noEmit" },
+  { tool: "biome", command: "biome check --error-on-warnings ." },
+  { tool: "tests", command: "npm test 2>&1 | tail -n 60" },
+];
+
+const results = await Promise.all(
+  CHECKS.map(async ({ tool, command }) => {
+    const r = await tools.bash({ command });
+    const lines = r.output.split("\n").filter((l) => l.trim() !== "");
+    return {
+      tool,
+      exit: r.exit_code,
+      firstFailures: r.exit_code === 0 ? [] : lines.slice(0, 15),
+    };
+  }),
+);
+
+return results;
+```
+
+Read the result before saying anything passed: every `exit` must be `0`. A non-zero `exit`
+means fix `firstFailures` first, then run the script again.
+
+Keep to checks that only read: a script may call any tool, and its nested calls are guarded
+like direct ones, but a verify script that edits files hides the edit inside one tool call.