@gonrocca/zero-pi 0.1.44 → 0.1.46
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/README.md +7 -1
- package/assets/preview.png +0 -0
- package/package.json +4 -2
- package/prompts/phases/explore.md +10 -0
package/README.md
CHANGED
|
@@ -13,7 +13,13 @@
|
|
|
13
13
|
|
|
14
14
|
**The zero spec-driven development workflow, packaged for [pi](https://pi.dev).**
|
|
15
15
|
|
|
16
|
-
[](https://www.npmjs.com/package/@gonrocca/zero-pi) [](https://github.com/gonzalonicolasr/zero-pi) [](./LICENSE) [](https://nodejs.org)
|
|
16
|
+
[](https://www.npmjs.com/package/@gonrocca/zero-pi) [](https://github.com/gonzalonicolasr/zero-pi) [](https://discord.gg/aNFCZBZVT3) [](./LICENSE) [](https://nodejs.org)
|
|
17
|
+
|
|
18
|
+
### 💬 Join the community
|
|
19
|
+
|
|
20
|
+
Questions, ideas, or want to debate workflow design? Come hang out:
|
|
21
|
+
|
|
22
|
+
[](https://discord.gg/aNFCZBZVT3)
|
|
17
23
|
|
|
18
24
|
</div>
|
|
19
25
|
|
|
Binary file
|
package/package.json
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@gonrocca/zero-pi",
|
|
3
|
-
"version": "0.1.
|
|
4
|
-
"description": "zero-pi — an installable layer for pi (pi.dev): the zero spec-driven development workflow
|
|
3
|
+
"version": "0.1.46",
|
|
4
|
+
"description": "zero-pi — an installable layer for pi (pi.dev): the zero spec-driven development workflow (explore → plan → build → veredicto) with per-phase model autotune and token-efficient batched builds. Adds capability to pi without modifying pi.",
|
|
5
5
|
"type": "module",
|
|
6
6
|
"keywords": [
|
|
7
7
|
"pi",
|
|
@@ -22,6 +22,7 @@
|
|
|
22
22
|
"themes": [
|
|
23
23
|
"./themes"
|
|
24
24
|
],
|
|
25
|
+
"image": "https://raw.githubusercontent.com/gonzalonicolasr/zero-pi/main/assets/preview.png",
|
|
25
26
|
"extensions": [
|
|
26
27
|
"./extensions/zero-banner.ts",
|
|
27
28
|
"./extensions/zero-statusline.ts",
|
|
@@ -39,6 +40,7 @@
|
|
|
39
40
|
"prompts",
|
|
40
41
|
"skills",
|
|
41
42
|
"themes",
|
|
43
|
+
"assets/preview.png",
|
|
42
44
|
"extensions/zero-banner.ts",
|
|
43
45
|
"extensions/zero-statusline.ts",
|
|
44
46
|
"extensions/working-phrases.ts",
|
|
@@ -14,6 +14,16 @@ Investigate the codebase and the feature request read-only. Do not modify any
|
|
|
14
14
|
files. Map the relevant modules, the existing patterns and conventions, the
|
|
15
15
|
integration points, and the constraints. Identify the risks and the unknowns.
|
|
16
16
|
|
|
17
|
+
**Size exploration to the request.** Match breadth to what the change actually
|
|
18
|
+
needs. A localized change — copy/text, one component, a config value, a single
|
|
19
|
+
endpoint — needs only the files that render or define it plus their immediate
|
|
20
|
+
wiring; do not map the full permission/billing model or unrelated subsystems
|
|
21
|
+
unless the request touches them. A cross-cutting or architectural change earns
|
|
22
|
+
full breadth. Stop once you can name the exact files to change and their
|
|
23
|
+
constraints — reading past that point burns tokens without improving the plan.
|
|
24
|
+
As a rough gauge, a localized change rarely needs more than ~20 tool calls; if
|
|
25
|
+
you blow past that on a small request, you are over-exploring.
|
|
26
|
+
|
|
17
27
|
Produce a concise findings report the **plan** phase can build on: what exists,
|
|
18
28
|
what is relevant to the request, and what to watch out for.
|
|
19
29
|
|