@gonrocca/zero-pi 0.1.42 → 0.1.44
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@gonrocca/zero-pi",
|
|
3
|
-
"version": "0.1.
|
|
3
|
+
"version": "0.1.44",
|
|
4
4
|
"description": "zero-pi — an installable layer for pi (pi.dev): the zero spec-driven development workflow, per-phase model autotune, and skill auto-learning. Adds capability to pi without modifying pi.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"keywords": [
|
package/prompts/orchestrator.md
CHANGED
|
@@ -103,6 +103,15 @@ and the adversarial veredicto. Delegate each phase to its sub-agent and wait
|
|
|
103
103
|
for its result. The orchestrator keeps control of phase order and the round
|
|
104
104
|
count — the sub-agents only carry out their own phase.
|
|
105
105
|
|
|
106
|
+
**Thin briefs — reference, never re-paste.** A sub-agent reads the
|
|
107
|
+
`.sdd/<slug>/` artifacts itself, so its brief carries only what it needs to
|
|
108
|
+
start: the feature slug, the artifact directory, and — for a build batch — the
|
|
109
|
+
batch's task numbers (plus, on a `corregir` re-run, the veredicto's defect
|
|
110
|
+
list). Never paste artifact contents — requirements, design, task text, prior
|
|
111
|
+
findings, file dumps — into a brief; reference them by path. Re-passing context
|
|
112
|
+
the sub-agent can read for itself is wasted tokens on every invocation, and a
|
|
113
|
+
batched build issues many briefs.
|
|
114
|
+
|
|
106
115
|
## Build batching
|
|
107
116
|
|
|
108
117
|
The **build** phase is not one monolithic sub-agent that implements every
|
|
@@ -1,33 +0,0 @@
|
|
|
1
|
-
---
|
|
2
|
-
name: skill-loop
|
|
3
|
-
description: zero's skill auto-learning loop — distill, store, surface, and refine reusable skills
|
|
4
|
-
---
|
|
5
|
-
|
|
6
|
-
# zero — Skill Auto-Learning
|
|
7
|
-
|
|
8
|
-
zero gives the agent a closed learning loop so solutions are reused, not
|
|
9
|
-
re-derived.
|
|
10
|
-
|
|
11
|
-
## Distill
|
|
12
|
-
|
|
13
|
-
When a substantial task completes, **distill** a reusable skill from it: capture
|
|
14
|
-
the solution pattern, the ordered steps, and the non-obvious gotchas into a
|
|
15
|
-
single skill document. If the task did only routine or one-off work with no
|
|
16
|
-
reusable pattern, do not create a skill.
|
|
17
|
-
|
|
18
|
-
## Store
|
|
19
|
-
|
|
20
|
-
Store each learned skill in the per-user skill library so it persists across
|
|
21
|
-
sessions and is available to every agent zero has configured.
|
|
22
|
-
|
|
23
|
-
## Surface
|
|
24
|
-
|
|
25
|
-
When a new task begins, surface the stored skills relevant to it — match by the
|
|
26
|
-
skill's subject and description — so the agent consults a known solution before
|
|
27
|
-
re-deriving one. Surface nothing when no stored skill is relevant.
|
|
28
|
-
|
|
29
|
-
## Refine
|
|
30
|
-
|
|
31
|
-
When a run re-applies an existing skill, **refine** that skill rather than
|
|
32
|
-
create a duplicate: merge new gotchas and steps without repeating what is
|
|
33
|
-
already there, and prefer the newer learning when it contradicts the old.
|