fix(skills): require isolated review and test workers
This commit is contained in:
@@ -32,8 +32,8 @@ Done when the chosen change set is explicit and reviewers have enough input to j
|
|||||||
Run independent dimension reviewers through whatever real context boundary the current harness provides.
|
Run independent dimension reviewers through whatever real context boundary the current harness provides.
|
||||||
A separate agent, worker, subprocess, or documented headless session is sufficient when each reviewer can inspect its dimension without seeing the parent review's intermediate conclusions.
|
A separate agent, worker, subprocess, or documented headless session is sufficient when each reviewer can inspect its dimension without seeing the parent review's intermediate conclusions.
|
||||||
Use one reviewer per dimension when practical.
|
Use one reviewer per dimension when practical.
|
||||||
If no real context boundary is available, state that limitation before reviewing.
|
If no real context boundary is available, stop before reviewing and report that independent review cannot be completed in the current runtime.
|
||||||
Proceed in-process only as an explicitly degraded fallback, and preserve separate report sections.
|
Do not replace independent reviewers with in-process role switches.
|
||||||
|
|
||||||
Use these reviewer files:
|
Use these reviewer files:
|
||||||
|
|
||||||
|
|||||||
@@ -13,9 +13,9 @@ The supported tool names are `subagent_spawn`, `subagent_batch`, `subagent_list`
|
|||||||
|
|
||||||
If these tools are unavailable, do not pretend that an in-process role switch is a subagent.
|
If these tools are unavailable, do not pretend that an in-process role switch is a subagent.
|
||||||
State that Pi subagent tools are unavailable in the current runtime.
|
State that Pi subagent tools are unavailable in the current runtime.
|
||||||
Do not perform the delegated subagent work in-process unless the caller explicitly permits a degraded fallback.
|
Do not perform the delegated subagent work in-process.
|
||||||
|
|
||||||
Done when the run has either a supported subagent tool path or a caller-approved degraded mode.
|
Done when the run has a supported subagent tool path.
|
||||||
|
|
||||||
## 2. Prepare a bounded prompt
|
## 2. Prepare a bounded prompt
|
||||||
|
|
||||||
|
|||||||
@@ -17,8 +17,8 @@ Tests are always written by someone other than the agent doing implementation.
|
|||||||
|
|
||||||
Launch an independent test writer through whatever real context boundary the current harness provides.
|
Launch an independent test writer through whatever real context boundary the current harness provides.
|
||||||
A separate agent, worker, subprocess, or documented headless session is sufficient when it cannot see the implementation agent's private backlog.
|
A separate agent, worker, subprocess, or documented headless session is sufficient when it cannot see the implementation agent's private backlog.
|
||||||
If no real context boundary is available, state that limitation before writing tests.
|
If no real context boundary is available, stop before writing tests and report that test-driven development cannot be completed in the current runtime.
|
||||||
Proceed in-process only as an explicitly degraded fallback, and preserve role separation as much as possible.
|
Do not replace the independent test writer with an in-process role switch.
|
||||||
Do not silently skip the independent-test-writer requirement.
|
Do not silently skip the independent-test-writer requirement.
|
||||||
|
|
||||||
The implementation agent may keep a private behavior backlog.
|
The implementation agent may keep a private behavior backlog.
|
||||||
|
|||||||
Reference in New Issue
Block a user