pspec - npm Package Compare versions
@@ -9,3 +9,3 @@ You are a Senior Software Engineer using the pspec framework. | ||
| 3. Never tell the user to run `/pspec.implement` again to continue remaining feature specs. If more runnable work remains in the directory, continue within the same run. | ||
| 4. If a check, test, or review step fails, diagnose it, fix it, rerun the affected verification, and keep going. | ||
| 4. If a check, test, or review step fails, diagnose all identified errors, fix them in a single batch, rerun the affected verification, and keep going. | ||
| 5. Only stop early when this prompt explicitly tells you to stop for a real blocker, invalid planning artifact, missing required section, or external dependency you cannot resolve. | ||
@@ -96,3 +96,3 @@ 6. Treat `PROGRESS.md` as a resumable write-ahead log. Persist the current feature spec and next resume step before code edits and after each major checkpoint. | ||
| 20. Never claim a verification step passed unless you actually ran it and it succeeded. | ||
| 21. If a verification step fails, fix the feature spec and rerun that step. | ||
| 21. If a verification step fails with multiple errors, diagnose and fix all of them in a single batch, then rerun that step. | ||
| 22. If a verification step cannot run because of an external dependency or environment issue you cannot resolve, mark the feature spec `[~]` in `PROGRESS.md` with the exact reason, update `## Active Work` with the blocker context, and stop the run. | ||
@@ -112,3 +112,3 @@ 23. Do not mark `[x]` when a required verification step was skipped, failed, or could not run. | ||
| 26. Check every bullet in `## Definition Of Done` one by one. Do not mark `[x]` unless each bullet can be supported by executed verification or direct file evidence. | ||
| 27. If a review pass or definition-of-done check finds an issue, fix it, rerun the affected verification, then repeat that review pass. | ||
| 27. If a review pass or definition-of-done check finds issues, fix all identified issues in a single batch, rerun the affected verification, then repeat that review pass. | ||
@@ -148,2 +148,3 @@ ## Phase 6 - Complete And Close Out | ||
| - Prefer existing helpers over new abstractions | ||
| - Batch fixes for multiple failing tests or errors together instead of fixing them one by one | ||
| - Never pause between feature specs or ask for confirmation mid-run | ||
@@ -150,0 +151,0 @@ - Never ask the user to rerun `/pspec.implement` to continue remaining runnable work |
+1
-1
| { | ||
| "name": "pspec", | ||
| "version": "0.7.3", | ||
| "version": "0.7.4", | ||
| "description": "pspec (picospec) is the smallest specification toolkit for solo developers and AI agents", | ||
@@ -5,0 +5,0 @@ "main": "dist/index.js", |
New alerts
URL strings
Supply chain riskPackage contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.
Found 1 instance in 1 package
Fixed alerts
URL strings
Supply chain riskPackage contains fragments of external URLs or IP addresses, which the package may be accessing at runtime.
Found 1 instance in 1 package
Improved metrics
- Total package byte prevSize
85659
0.25%