@trevonistrevon/pi-loop 0.5.2 → 0.5.3
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.
|
@@ -15,7 +15,10 @@ Fields:
|
|
|
15
15
|
promptGuidelines: [
|
|
16
16
|
"Use TaskCreate to track complex multi-step work across turns.",
|
|
17
17
|
"When the user gives a broad goal, use multiple TaskCreate calls to decompose it into a small backlog of concrete tasks rather than one oversized task.",
|
|
18
|
+
"If the user supplies a shared goal or meta-goal, preserve it explicitly using the user's wording and tie each created task back to that goal in its description.",
|
|
19
|
+
"If several tasks share one goal, keep subjects short and put the shared goal in the first sentence of each description or as an equivalent explicit framing.",
|
|
18
20
|
"Prefer 2-5 tasks that separate investigation, implementation, validation, and reporting or commit-prep when those phases are distinct.",
|
|
21
|
+
"When the user asks to break work into tasks, create the backlog directly and do not pivot to loops, monitors, or other automation unless the user also asked for ongoing automation.",
|
|
19
22
|
"Make each `subject` a short verb-object action.",
|
|
20
23
|
"Make each `description` include the expected artifact, outcome, or done condition so another turn can pick the task up cleanly.",
|
|
21
24
|
"Break work into small, independently completable tasks. A task should be finishable in one focused session — if a task would take multiple turns, split it further.",
|
package/package.json
CHANGED
|
@@ -32,7 +32,10 @@ Fields:
|
|
|
32
32
|
promptGuidelines: [
|
|
33
33
|
"Use TaskCreate to track complex multi-step work across turns.",
|
|
34
34
|
"When the user gives a broad goal, use multiple TaskCreate calls to decompose it into a small backlog of concrete tasks rather than one oversized task.",
|
|
35
|
+
"If the user supplies a shared goal or meta-goal, preserve it explicitly using the user's wording and tie each created task back to that goal in its description.",
|
|
36
|
+
"If several tasks share one goal, keep subjects short and put the shared goal in the first sentence of each description or as an equivalent explicit framing.",
|
|
35
37
|
"Prefer 2-5 tasks that separate investigation, implementation, validation, and reporting or commit-prep when those phases are distinct.",
|
|
38
|
+
"When the user asks to break work into tasks, create the backlog directly and do not pivot to loops, monitors, or other automation unless the user also asked for ongoing automation.",
|
|
36
39
|
"Make each `subject` a short verb-object action.",
|
|
37
40
|
"Make each `description` include the expected artifact, outcome, or done condition so another turn can pick the task up cleanly.",
|
|
38
41
|
"Break work into small, independently completable tasks. A task should be finishable in one focused session — if a task would take multiple turns, split it further.",
|