ticlawk 0.1.17-dev.16 → 0.1.17-dev.17
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
CHANGED
|
@@ -19,7 +19,8 @@ const STEP_GUIDES = {
|
|
|
19
19
|
- Judge "due now" against the current owner-local time above. Produce only what is due now; do NOT pre-produce a future occurrence — each one is produced when its own reminder fires and wakes you at that time.
|
|
20
20
|
- If there is concrete work to do NOW, make sure the next unit exists as a task (\`ticlawk task ...\`), then report outcome=gap.
|
|
21
21
|
- If nothing needs doing this instant but the goal is ONGOING/STANDING — its job is to keep something maintained and work recurs (e.g. an active recurring reminder above already covers the next occurrence) — report outcome=wait. Do NOT report no_gap for a standing goal: it has no "done", and parking on no_gap would stop it from waking at the next occurrence. If nothing is scheduled to resume it yet, schedule a reminder first, then report wait.
|
|
22
|
-
- Report outcome=no_gap ONLY if the goal is genuinely, permanently met and will never need action again (an achievement goal that is finished). The completed result is something the owner is waiting on — surface it per the briefing rule below
|
|
22
|
+
- Report outcome=no_gap ONLY if the goal is genuinely, permanently met and will never need action again (an achievement goal that is finished). The completed result is something the owner is waiting on — surface it per the briefing rule below.
|
|
23
|
+
- Judge done-ness by the goal's real deliverable — the work itself and the dashboard — NOT by whether the task board is tidy. A task still showing open, or one you could not close, is not by itself remaining work: if the deliverable is met, report no_gap. Never keep the loop alive, or spend this turn, just to reconcile the board.`,
|
|
23
24
|
outcomes: ['gap', 'no_gap', 'wait'],
|
|
24
25
|
},
|
|
25
26
|
execute: {
|
|
@@ -33,7 +34,7 @@ const STEP_GUIDES = {
|
|
|
33
34
|
review: {
|
|
34
35
|
title: 'REVIEW',
|
|
35
36
|
body: `Review the work that was just completed against the task and the goal.
|
|
36
|
-
- If it meets the bar,
|
|
37
|
+
- If it meets the bar, report outcome=accepted. Mark the task done if the board supports it (\`ticlawk task update ... --status done\`), but a close that fails or does not apply must NOT stop you from reporting accepted — the board is a coordination aid, not a gate.
|
|
37
38
|
- If it needs rework, return it with a clean, specific redo instruction, then report outcome=rejected.`,
|
|
38
39
|
outcomes: ['accepted', 'rejected'],
|
|
39
40
|
},
|