refactor: switch pi-subagents to generic subagents

This commit is contained in:
pi
2026-04-12 07:00:10 +01:00
parent c8859b626b
commit d80367037c
11 changed files with 26 additions and 204 deletions

View File

@@ -1,10 +1,10 @@
---
description: Implement, review, then revise using subagents
description: Implement, review, then revise using generic subagents
---
Use the `subagent` tool in chain mode:
1. `worker` to implement: $@
2. `reviewer` to review `{previous}` and identify issues
3. `worker` to revise the implementation using `{previous}`
1. Run a generic subagent to implement: $@
2. Run a generic subagent to review `{previous}` and identify issues
3. Run a generic subagent to revise the implementation using `{previous}`
User request: $@

View File

@@ -1,10 +1,10 @@
---
description: Scout, plan, and implement using subagents
description: Inspect, plan, and implement using generic subagents
---
Use the `subagent` tool to handle this request in three stages:
Use the `subagent` tool in chain mode:
1. Run `scout` to inspect the codebase for: $@
2. Run `planner` in chain mode, using `{previous}` from the scout output to produce a concrete implementation plan
3. Run `worker` in chain mode, using `{previous}` from the planner output to implement the approved plan
1. Run a generic subagent to inspect the codebase for: $@
2. Run a generic subagent to turn `{previous}` into a concrete implementation plan for: $@
3. Run a generic subagent to implement the approved plan using `{previous}`
User request: $@

View File

@@ -1,9 +1,9 @@
---
description: Scout the codebase, then produce a plan using subagents
description: Inspect the codebase, then produce a plan using generic subagents
---
Use the `subagent` tool in chain mode:
1. `scout` to inspect the codebase for: $@
2. `planner` to turn `{previous}` into an implementation plan
1. Run a generic subagent to inspect the codebase for: $@
2. Run a generic subagent to turn `{previous}` into a concrete implementation plan for: $@
User request: $@