refactor pi resource wiring by directory

pi/extensions/subagent/prompts/implement-and-review.md

@@ -0,0 +1,10 @@
+---
+description: Implementer makes the change, reviewer critiques it, implementer applies the review
+---
+Use the `subagent` tool with `chain` mode for this workflow:
+
+1. Run `implementer` to implement: $@
+2. Run `reviewer` to review the implementation output using `{previous}`
+3. Run `implementer` again to apply the review feedback using `{previous}`
+
+Use a chain so each step receives the prior step's output via `{previous}`.

pi/extensions/subagent/prompts/implement.md

@@ -0,0 +1,10 @@
+---
+description: Scout gathers context, planner creates a plan, implementer applies it
+---
+Use the `subagent` tool with `chain` mode for this workflow:
+
+1. Run `scout` to gather the most relevant code paths for: $@
+2. Run `planner` to turn the findings into an implementation plan for: $@
+3. Run `implementer` to execute the plan from the previous step using `{previous}`
+
+Use a chain so each step receives the prior step's output via `{previous}`.

pi/extensions/subagent/prompts/parallel-scout.md

@@ -0,0 +1,9 @@
+---
+description: Run scout and librarian in parallel, then summarize their findings
+---
+Use the `subagent` tool with `tasks` mode to run these in parallel for: $@
+
+- `scout`: identify the most relevant files, flows, and entrypoints
+- `librarian`: find related patterns, prior art, tests, or docs
+
+After both results return, synthesize them into one concise summary with recommended next steps.

pi/extensions/subagent/prompts/research.md

@@ -0,0 +1,28 @@
+---
+description: Run local scout and external librarian research in parallel, then synthesize grounded guidance
+---
+Use the `subagent` tool with `tasks` mode to run these in parallel for: $@
+
+- `scout`: inspect the current repository and identify the most relevant local files, entrypoints, constraints, and likely change surface
+- `librarian`: gather external references and coding prior art, using `exa_search` for docs/web research and `exa_code` for implementation examples when useful
+
+After both results return:
+
+1. Synthesize them into one grounded response.
+2. Clearly separate:
+   - local repository findings
+   - external references and docs
+   - recommended implementation patterns
+3. Prefer official docs and high-signal sources over generic summaries.
+4. Call out where external advice may not fit this repository's existing architecture.
+5. Do **not** implement changes unless the user explicitly asks.
+
+Return the final answer in this structure:
+
+## Goal
+## Local Findings
+## External References
+## Recommended Pattern
+## Risks / Caveats
+## Next Steps
+## Sources

pi/extensions/subagent/prompts/scout-and-plan.md

@@ -0,0 +1,9 @@
+---
+description: Scout gathers context, planner turns it into a concrete plan without implementation
+---
+Use the `subagent` tool with `chain` mode for this workflow:
+
+1. Run `scout` to gather the most relevant code paths for: $@
+2. Run `planner` to create a concrete implementation plan for: $@ using `{previous}` as context
+
+Return the plan only. Do not implement changes.