@janvitos/pi-plan-build 0.1.43 → 0.1.45
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 +1 -1
- package/prompts.ts +4 -1
package/package.json
CHANGED
package/prompts.ts
CHANGED
|
@@ -43,7 +43,10 @@ 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 a
|
|
46
|
+
- Include a brief \`## Verification\` section describing the smallest credible proof that the changed basic functionality works. Group related validation and avoid exhaustive regression, edge-case, performance, or compatibility testing.
|
|
47
|
+
- Structure the section with:
|
|
48
|
+
- \`### Agent\` — Checks the agent should perform after implementation. Prefer one targeted behavior-level test or smoke check with an exact repository-supported command and a short expected observable result. If no behavioral command exists, use the smallest relevant build, type-check, configuration validation, or dry run. Never invent commands.
|
|
49
|
+
- \`### User\` — Only essential validation the agent cannot safely or realistically perform because it requires user access, credentials, judgment, hardware, privileged operations, or could affect running services, data, external systems, or machine state. Give an exact known command or action and expected result. The agent must not perform these items unless separately requested. Omit this subsection when unnecessary.
|
|
47
50
|
- 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
51
|
|
|
49
52
|
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.
|