BIG pi update with claude chat

pi/.pi/agent/skills/implementor/SKILL.md

@@ -0,0 +1,50 @@
+---
+name: implementor
+description: "Delegate implementation of a fix or feature to the implementor agent. Use when you have a clear plan, bug fix, or feature to implement and want a focused agent to handle the full coding + build-verify cycle."
+---
+
+# Implementor
+
+When you need to implement a fix, feature, or refactoring with full build verification:
+
+## What to include in the prompt
+
+1. **Goal** — what needs to be built or fixed, in 1-2 sentences
+2. **Context** — relevant files, functions, or modules (include the actual code or file paths)
+3. **Plan** — step-by-step description of the changes to make (if you have one)
+4. **Constraints** — any project conventions, patterns to follow, or things to avoid
+5. **Verification** — how to confirm the implementation is correct (build command, test names, etc.)
+
+The `implementor` agent has `Read`, `Bash`, `Edit`, and `Write` tools only — it can read code, run commands, and make changes. It cannot use semantic search or web search.
+
+## How to call
+
+```
+ask_claude({
+  agent: "implementor",
+  question: "Implement [brief description of the fix or feature].",
+  prompt: `
+## Goal
+[What needs to be done]
+
+## Context
+[Relevant files and code snippets]
+
+## Plan
+[Step-by-step changes, or "investigate and determine the best approach"]
+
+## Constraints
+[Project conventions, patterns to follow, things to avoid]
+
+## Verification
+[Build command, tests to run, how to confirm correctness]
+`
+})
+```
+
+## After the review
+
+- Check whether the agent reported successful build/verification
+- If it failed, either re-invoke with the error details or fix the remaining issues directly
+- Summarize for the user: what files changed, what was verified, and any remaining concerns
+- For complex implementations, consider running `diagnostics` sub-agent or relevant tests afterward as a second pass