@pmelab/gtd 12.2.0 → 12.4.0
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 +8 -0
- package/dist/gtd.bundle.mjs +2 -2
- package/package.json +3 -1
package/README.md
CHANGED
|
@@ -325,6 +325,14 @@ noted in steps 2, 3, and 4 below.
|
|
|
325
325
|
every one of these correctly: it shows you the message and stops, same as any
|
|
326
326
|
other question.
|
|
327
327
|
|
|
328
|
+
The `gtd --entry fix-precheck` side door (below) repairs a red baseline
|
|
329
|
+
through this same loop's own green check, and that check also runs a
|
|
330
|
+
qualitative review lap first: one configured skill per turn, each looking at
|
|
331
|
+
the change from its own angle (a security checklist, a simplification pass)
|
|
332
|
+
and fixing what it finds once, with no re-review after the fix. It never
|
|
333
|
+
replaces step 4 — your review stays the final gate, and nothing here skips
|
|
334
|
+
it.
|
|
335
|
+
|
|
328
336
|
A red suite that keeps failing past a few fix attempts escalates instead of
|
|
329
337
|
retrying forever: an agent turn reads the failing output and writes
|
|
330
338
|
`.gtd/ESCALATION.md` — what's failing, why the earlier attempts didn't fix
|