@gonrocca/zero-pi 0.1.17 → 0.1.18

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gonrocca/zero-pi",
-  "version": "0.1.17",
+  "version": "0.1.18",
   "description": "zero-pi — an installable layer for pi (pi.dev): the zero spec-driven development workflow, skill auto-learning, and an animated ZERO startup banner. Adds capability to pi without modifying pi.",
   "type": "module",
   "keywords": [

package/prompts/forge.md

@@ -1,34 +1,17 @@
 ---
-description: Run an automatic spec-driven development pipeline for a feature request
+description: Run the zero spec-driven development pipeline for a feature request
 ---
 
-Run the zero SDD pipeline for the feature request in the arguments.
-
-**Parse the arguments first.** If the arguments start with `--continue`, this is
-a **resume** run, not a fresh one:
-
-- `--continue` with no slug → resume mode: hand control to the orchestrator's
-  `## Resuming a run` section, which scans `.sdd/*/` for an unfinished run.
-- `--continue <slug>` → resume mode targeting `.sdd/<slug>/` directly. If that
-  directory does not exist, report "no such run: <slug>" and stop — do **not**
-  start a fresh run under that slug.
-- Anything else (a feature request, or no arguments) → a fresh run, exactly
-  today's behaviour: the arguments are the feature request.
-
-Follow the zero SDD orchestrator instructions: drive the run through the
-explore → plan → build → veredicto phases, honour the build/veredicto iteration
-cap, and use the execution mode (interactive or automatic) the user chose.
-
-Delegate each phase to its dedicated sub-agent so the phase runs on the model
-it is configured for: `zero-explore`, `zero-plan`, `zero-build`, and
-`zero-veredicto`. You stay the orchestrator — you decide phase order and count
-the rounds; the sub-agents only execute their phase.
-
-In interactive mode, pause after each phase with a summary and ask before
-continuing. Never report success unless the veredicto phase returned a `pasa`
-verdict; if the cap is reached first, report that the result is not verified.
-
-To change the per-phase models, the user runs the `/zero-models` command — do
-not handle model configuration here.
+Run the zero SDD pipeline for the feature request below — you are the
+orchestrator. Drive it through four phases in order: **explore → plan → build →
+veredicto**, delegating each to its sub-agent (`zero-explore`, `zero-plan`,
+`zero-build`, `zero-veredicto`). A `corregir` verdict re-runs `build`; a
+`replantear` verdict re-runs `plan`; after a few rounds with no `pasa`, stop and
+report the result as not verified. Ask the user for interactive or automatic
+mode up front; in interactive mode pause after each phase for approval. Never
+claim success unless veredicto returned `pasa`.
+
+If the request begins with `--continue [slug]`, resume that unfinished run from
+its `.sdd/<slug>/` artifacts instead of starting fresh.
 
 Feature request: $ARGUMENTS