@henryqw/pi-subagent 15.0.3 → 15.1.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
CHANGED
|
@@ -78,7 +78,17 @@ See the [orchestration guide](./docs/orchestration.md) for full delegation, tran
|
|
|
78
78
|
|
|
79
79
|
### Skills
|
|
80
80
|
|
|
81
|
-
The bundled [`pi-subagent-delegated-development`](./skills/pi-subagent-delegated-development/SKILL.md) Skill guides Main's planning and orchestration. It adds no runtime code, config, or Role installation.
|
|
81
|
+
The bundled [`pi-subagent-delegated-development`](./skills/pi-subagent-delegated-development/SKILL.md) Skill guides Main's planning and orchestration. It adds no runtime code, config, or Role installation.
|
|
82
|
+
|
|
83
|
+
Its ordinary review loop is optional. Use it only when the caller or repository policy explicitly requires judgment review.
|
|
84
|
+
|
|
85
|
+
- Call `delegate_task` with `role: "reviewer"` to select the effective `reviewer` Role.
|
|
86
|
+
- Its task packet must state the read-only scope and exact `PASS` or findings contract. Include exact acceptance criteria and validation evidence.
|
|
87
|
+
- The Reviewer must see exact candidate evidence from its working directory. Use `delegate_flow` for an isolated candidate, not an ordinary review from Main's unchanged checkout.
|
|
88
|
+
- Fix initial findings together. Validate repaired inputs once before focused re-review. Include the original findings and acceptance criteria, exact repaired-candidate evidence, and validation evidence.
|
|
89
|
+
- Only `PASS` completes the loop. Surface and block on re-review findings or empty output. Retry empty output only when explicit caller policy requires one. A second empty result blocks. Do not add another round.
|
|
90
|
+
|
|
91
|
+
Flow is separate. It owns exact review evidence, exact `PASS` approval, validation replay, one repair continuation, and no automatic retry.
|
|
82
92
|
|
|
83
93
|
## Flow
|
|
84
94
|
|
package/package.json
CHANGED
|
@@ -1,11 +1,11 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: pi-subagent-delegated-development
|
|
3
|
-
description:
|
|
3
|
+
description: Use Delegate Flow, or coordinate explicitly required judgment review for ordinary delegated implementation.
|
|
4
4
|
---
|
|
5
5
|
|
|
6
6
|
# Delegated Development
|
|
7
7
|
|
|
8
|
-
You are Main, the planner/orchestrator: slice work and
|
|
8
|
+
You are Main, the planner/orchestrator: slice work and choose `delegate_flow` or `delegate_task` as described below. Do not implement child work yourself or use external model tools, push, publish, or release.
|
|
9
9
|
|
|
10
10
|
## Slice
|
|
11
11
|
|
|
@@ -36,3 +36,24 @@ A cleanup warning does not undo successful integration. Report a cleanup warning
|
|
|
36
36
|
## Ordinary delegation
|
|
37
37
|
|
|
38
38
|
Use `delegate_task` for a single bounded task, independent parallel tasks, or dependent chain work that is not a Flow. Give each entry its objective, exact scope and exclusions, relevant context and constraints, expected deliverable, and focused validation. Choose `modelClass` according to the delegation tool's guidance. A direct `model` replaces only the selected route's model. The route keeps its thinking level. Keep integration and cross-cutting decisions in Main, and use the minimum number of Subagents needed.
|
|
39
|
+
|
|
40
|
+
### Optional evidence loop for implementation
|
|
41
|
+
|
|
42
|
+
Use this caller-managed loop only when the caller or repository policy explicitly requires judgment review. It is not required for every ordinary implementation.
|
|
43
|
+
|
|
44
|
+
After implementation and focused validation, launch `delegate_task` with `role: "reviewer"` to select the effective `reviewer` Role. A same-named user Role remains effective. The task packet must state:
|
|
45
|
+
|
|
46
|
+
- the read-only scope;
|
|
47
|
+
- the exact acceptance criteria;
|
|
48
|
+
- exact candidate evidence visible from the Reviewer's working directory and the supplied validation evidence;
|
|
49
|
+
- the exact output contract: return `PASS` alone on approval, or findings only.
|
|
50
|
+
|
|
51
|
+
Do not launch the Reviewer unless it can see the actual candidate. For an isolated implementation candidate, use `delegate_flow` instead of composing an ordinary review against Main's unchanged checkout.
|
|
52
|
+
|
|
53
|
+
Empty Reviewer output is a failure. Retry only when explicit caller policy requires one; otherwise surface the failure and block completion. If that retry is also empty, surface the second empty result and block completion.
|
|
54
|
+
|
|
55
|
+
If the initial review returns findings, repair them together. Run one focused validation of the repaired inputs before one focused re-review. Its task packet must restate the read-only scope, exact output contract, original findings, original acceptance criteria, exact repaired-candidate evidence, and validation evidence.
|
|
56
|
+
|
|
57
|
+
Only `PASS` completes the loop. Focused re-review findings block completion and must be surfaced. Do not start another repair/review round.
|
|
58
|
+
|
|
59
|
+
Do not layer this loop onto `delegate_flow`. Flow already owns exact review evidence, exact `PASS` approval, validation replay, one repair continuation, and no automatic retry.
|