pi-btw 0.4.0 → 0.5.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "pi-btw",
-  "version": "0.4.0",
+  "version": "0.5.0",
   "description": "A pi extension for parallel side conversations with /btw",
   "type": "module",
   "license": "MIT",
@@ -22,6 +22,7 @@
   ],
   "files": [
     "extensions",
+    "skills",
     "docs",
     "README.md",
     "LICENSE"
@@ -30,7 +31,8 @@
     "access": "public"
   },
   "scripts": {
-    "test": "vitest --run"
+    "test": "vitest --run",
+    "typecheck": "tsc --noEmit"
   },
   "pi": {
     "extensions": [
@@ -42,11 +44,14 @@
     "image": "https://raw.githubusercontent.com/dbachelder/pi-btw/main/docs/btw-overlay.png"
   },
   "peerDependencies": {
-    "@earendil-works/pi-ai": "^0.74.0",
-    "@earendil-works/pi-coding-agent": "^0.74.0",
-    "@earendil-works/pi-tui": "^0.74.0"
+    "@earendil-works/pi-ai": ">=0.85.1 <1",
+    "@earendil-works/pi-coding-agent": ">=0.85.1 <1",
+    "@earendil-works/pi-tui": ">=0.85.1 <1"
   },
   "devDependencies": {
+    "@earendil-works/pi-ai": "0.85.1",
+    "@earendil-works/pi-coding-agent": "0.85.1",
+    "@earendil-works/pi-tui": "0.85.1",
     "typescript": "^6.0.2",
     "vitest": "^4.1.0"
   }

package/skills/btw/SKILL.md

@@ -0,0 +1,170 @@
+---
+name: btw
+description: Helps you use the /btw side-conversation workflow effectively. Use when you want to think in parallel, ask side questions without interrupting ongoing work, or inject a side thread back into the main agent.
+---
+
+# BTW
+
+Use this skill when the user wants to work in parallel with the main agent instead of derailing the current turn.
+
+## When to use BTW
+
+Prefer the BTW workflow when the user wants to:
+
+- ask a side question while the main agent keeps working
+- brainstorm or compare options without interrupting the current run
+- prepare a plan or summary before handing it back to the main agent
+- keep exploratory discussion out of the main transcript/context
+
+## Commands
+
+Use these commands in your guidance to the user:
+
+```text
+/btw <question>
+/btw --save <question>
+/btw:new [question]
+/btw:tangent <question>
+/btw:tangent --save <question>
+/btw:clear
+/btw:model [<provider> <model> <api> | clear]
+/btw:thinking [<level> | clear]
+/btw:inject [instructions]
+/btw:summarize [instructions]
+```
+
+## How to guide the user
+
+### For a quick side question
+
+Recommend:
+
+```text
+/btw <question>
+```
+
+Use this when the user wants an immediate aside and does not need a visible saved note.
+
+### For a saved one-off note
+
+Recommend:
+
+```text
+/btw --save <question>
+```
+
+Use this when the user wants the exchange to appear as a visible BTW note in the session transcript.
+
+### For a fresh side thread
+
+Recommend:
+
+```text
+/btw:new
+```
+
+or
+
+```text
+/btw:new <question>
+```
+
+Use this when the previous BTW discussion is no longer relevant, but you still want the new side thread to inherit the current main-session context.
+
+### For a contextless tangent thread
+
+Recommend:
+
+```text
+/btw:tangent <question>
+```
+
+or
+
+```text
+/btw:tangent --save <question>
+```
+
+Use this when the user wants a side conversation that does not include the current main-session context.
+
+### To hand the full thread back to the main agent
+
+Recommend:
+
+```text
+/btw:inject <instructions>
+```
+
+Use this when the exact discussion matters and the user wants the main agent to act on it.
+
+### To hand back a condensed version
+
+Recommend:
+
+```text
+/btw:summarize <instructions>
+```
+
+Use this when the thread is long and only the distilled outcome should go back into the main agent.
+
+### To make BTW cheaper or faster than the main thread
+
+Recommend:
+
+```text
+/btw:model <provider> <model> <api>
+/btw:thinking <level>
+```
+
+Use these when the main thread should keep its current model or thinking level, but BTW should run with a different cost/speed profile.
+
+## Recommendation rules
+
+- Prefer `/btw` over normal chat when the user explicitly wants a side conversation.
+- Prefer `/btw:tangent` when the user wants that side conversation to be contextless.
+- Prefer `/btw:summarize` over `/btw:inject` for long exploratory threads.
+- Prefer `/btw:inject` when precise wording, detailed tradeoffs, or a full plan matters.
+- Suggest `/btw:new` before starting a totally unrelated side topic when main-session context is still useful.
+- Suggest `/btw:clear` when the widget/thread should be dismissed.
+- Suggest `/btw:model` or `/btw:thinking` when the user wants BTW to be cheaper, faster, or less deliberative than the main thread.
+
+## Response style
+
+When helping the user use BTW:
+
+- give the exact slash command to run
+- explain briefly why that command fits
+- keep the guidance short and operational
+
+## Examples
+
+### Example: brainstorm while coding continues
+
+```text
+/btw what are the risks of switching this to optimistic updates?
+```
+
+### Example: create a clean new thread
+
+```text
+/btw:new sketch a safer migration plan
+```
+
+### Example: start a contextless tangent
+
+```text
+/btw:tangent think through this from first principles without using the current chat context
+```
+
+### Example: send the result back
+
+```text
+/btw:summarize implement the recommended migration plan
+```
+
+### Example: make BTW cheaper than the main thread
+
+```text
+/btw:model openai gpt-5-mini openai-responses
+/btw:thinking low
+```