pi-herdsman 0.7.0 → 0.7.2
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/SKILL.md +23 -4
- package/dist/index.js +101 -72
- package/docs/concepts/agents.md +4 -3
- package/docs/concepts/delegation.md +22 -8
- package/docs/concepts/lifecycle.md +45 -14
- package/docs/development/smoke-testing.md +26 -9
- package/docs/guides/recovery.md +13 -1
- package/docs/reference/agent-states.md +32 -8
- package/docs/reference/agent.md +12 -9
- package/docs/reference/status-widget.md +11 -6
- package/package.json +1 -1
package/SKILL.md
CHANGED
|
@@ -54,6 +54,12 @@ Use steer only to change active work. Use reply only to answer a valid
|
|
|
54
54
|
outstanding ask_owner question. Use close only for intentional teardown or
|
|
55
55
|
abandonment.
|
|
56
56
|
|
|
57
|
+
A lost agent is a managed assignment whose exact physical execution is proven
|
|
58
|
+
gone before a durable terminal result resolved it. Loss is not completion or
|
|
59
|
+
task failure. Treat the assignment as unresolved. Use close to abandon the
|
|
60
|
+
lost generation before replacing it or continuing its saved session. Unknown
|
|
61
|
+
evidence remains fail-closed and is not proof of loss.
|
|
62
|
+
|
|
57
63
|
Never guess identities, paths, sessions, or control state. Treat unknown or
|
|
58
64
|
conflicting evidence as unresolved. Keep one writer per worktree or file-
|
|
59
65
|
ownership boundary. Use a capable definition or report blocked when a required
|
|
@@ -67,10 +73,23 @@ assignment when practical. If genuinely new follow-up work emerges after
|
|
|
67
73
|
completion and previous context is valuable, continue the exact returned session
|
|
68
74
|
only when the completion is not marked retired. A retired session requires a
|
|
69
75
|
fresh delegation; pass its resultRef/handoff and relevant files instead.
|
|
70
|
-
|
|
71
|
-
|
|
72
|
-
|
|
73
|
-
|
|
76
|
+
Each active delegated assignment has one executor: that agent. Do not repeat
|
|
77
|
+
its assigned work locally or delegate substantially overlapping work elsewhere.
|
|
78
|
+
|
|
79
|
+
After starting an agent assignment or receiving an agent result or attention
|
|
80
|
+
event, reassess the remaining work. Handle required agent control when needed.
|
|
81
|
+
If another concrete, necessary objective is independent of active agent
|
|
82
|
+
assignments and an authorized agent is the right owner, delegate it. If a
|
|
83
|
+
concrete, necessary independent objective is best handled locally and doing it
|
|
84
|
+
now materially advances the task, do that work, then reassess.
|
|
85
|
+
|
|
86
|
+
If further useful progress depends on active agents, or no other concrete,
|
|
87
|
+
necessary independent work remains, end your turn without concluding the task.
|
|
88
|
+
Agent results or attention will resume this session automatically. Do not
|
|
89
|
+
conclude or produce the final synthesis while unresolved agent work remains.
|
|
90
|
+
Do not invent side work, broaden scope, perform speculative or precautionary
|
|
91
|
+
exploration, list or inspect merely for progress, steer merely for status, sleep,
|
|
92
|
+
poll, or otherwise keep the turn alive while agent results are pending.
|
|
74
93
|
|
|
75
94
|
If list reports result_error, do not start a new delegation over unresolved
|
|
76
95
|
work. Resolve mailbox persistence first, then close the exact agent before
|