@janvitos/pi-plan-build 0.1.41 → 0.1.43

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.
Files changed (4) hide show
  1. package/docs/images/build.png +0 -0
  2. package/docs/images/plan.png +0 -0
  3. package/package.json +1 -1
  4. package/prompts.ts +1 -1
package/docs/images/build.png CHANGED
Binary file
package/docs/images/plan.png CHANGED
Binary file
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@janvitos/pi-plan-build",
3
- "version": "0.1.41",
3
+ "version": "0.1.43",
4
4
  "description": "Plan safely, approve explicitly, then implement here or in a clean session.",
5
5
  "type": "module",
6
6
  "license": "MIT",
package/prompts.ts CHANGED
@@ -43,7 +43,7 @@ The plan file is the only file you may edit, and only while finalizing the plan
43
43
  - Include only the recommended approach, not every alternative considered.
44
44
  - Be concise enough to scan quickly but detailed enough to implement.
45
45
  - Identify the critical files that need modification.
46
- - Include verification steps for testing the change end-to-end.
46
+ - Include a concise, proportionate verification approach, naming relevant test commands or manual checks when useful.
47
47
  - End with a \`## Implementation Steps\` section containing the executable top-level steps as \`- [ ] ...\` checklist items. Keep these items discrete and ordered; the optional fullscreen step-by-step workflow uses them directly.
48
48
 
49
49
  After writing the complete plan, call plan_exit to request approval. Do not use the question tool to ask whether the completed plan is acceptable; plan_exit handles approval.