@leing2021/super-pi 0.19.0 → 0.19.1

package/README.md

@@ -35,6 +35,38 @@ Super Pi's answers:
 
 Each step has a dedicated skill + tool pair. Not just prompts — structured toolchains.
 
+### New: Stage model routing + optional auto-continue
+
+Configure once in `.pi/settings.json`:
+
+```json
+{
+  "modelStrategy": {
+    "01-brainstorm": "claude-sonnet-4-20250514",
+    "02-plan": "claude-opus-4-20250115",
+    "03-work": "claude-sonnet-4-20250514",
+    "04-review": "claude-sonnet-4-20250514",
+    "05-learn": "claude-haiku-4-20250414",
+    "default": "claude-sonnet-4-20250514"
+  },
+  "pipeline": {
+    "autoContinue": false
+  }
+}
+```
+
+How it works:
+- Each stage picks `modelStrategy[stage]`, or `modelStrategy.default` as fallback.
+- Every stage prints a `📊 Pipeline Status` block with `Current / Output / Next`.
+- If `pipeline.autoContinue=true`, super-pi can trigger the next stage automatically.
+- Auto-continue is gate-aware: it will NOT skip required approvals (brainstorm approval, plan/review A/B/C choices).
+
+Quick example:
+1. Run `/skill:01-brainstorm`
+2. Approve the design
+3. If `autoContinue=true`, it moves to `/skill:02-plan` automatically
+4. If `autoContinue=false`, it stops after status output and waits for your command
+
 ---
 
 ## What Each Step Does

package/extensions/ce-core/index.ts

@@ -282,8 +282,8 @@ export default function ceCoreExtension(pi: ExtensionAPI) {
           allowCustom: params.allowCustom,
         },
         {
-          input: async (question) => ctx.ui.input(question),
-          select: async (question, options) => ctx.ui.select(question, options),
+          input: async (question) => (await ctx.ui.input(question)) ?? null,
+          select: async (question, options) => (await ctx.ui.select(question, options)) ?? null,
         },
       )
 
@@ -586,7 +586,7 @@ export default function ceCoreExtension(pi: ExtensionAPI) {
     return {
       content: [{ type: "text", text: result.output }],
       details: {
-        ...event.details,
+        ...(event.details && typeof event.details === "object" ? event.details : {}),
         bashFilter: {
           strategy: result.strategy,
           originalBytes: result.originalBytes,
@@ -623,7 +623,7 @@ export default function ceCoreExtension(pi: ExtensionAPI) {
     return {
       content: [{ type: "text", text: result.output }],
       details: {
-        ...event.details,
+        ...(event.details && typeof event.details === "object" ? event.details : {}),
         readFilter: {
           strategy: result.strategy,
           originalBytes: result.originalBytes,
@@ -633,10 +633,11 @@ export default function ceCoreExtension(pi: ExtensionAPI) {
     }
   })
 
-  // Compaction prompt optimizer — makes summaries more focused and useful
-  pi.on("session_before_compact", async (_event, _ctx) => {
+  // Tree summary prompt optimizer — keeps branch summaries focused
+  pi.on("session_before_tree", async (_event, _ctx) => {
     return {
       customInstructions: COMPACTION_FOCUS_INSTRUCTIONS,
+      replaceInstructions: false,
     }
   })
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@leing2021/super-pi",
-  "version": "0.19.0",
+  "version": "0.19.1",
   "private": false,
   "type": "module",
   "description": "Pi-native Compound Engineering package for iterative development workflows",

package/skills/01-brainstorm/SKILL.md

@@ -7,6 +7,8 @@ description: "Brainstorm requirements with three modes: CE discovery, Startup Di
 
 Use this skill when the request is ambiguous, needs requirements discovery before planning, or the user describes a new idea/product.
 
+See [shared pipeline instructions](../references/pipeline-config.md) for model routing and pipeline behavior.
+
 ## Core rules
 
 - Use **`brainstorm_dialog`** to manage multi-round conversations.
@@ -118,3 +120,5 @@ Before handing off to `02-plan`:
 ## Artifact contract
 
 Use `references/requirements-template.md` to structure the requirements document. Keep implementation details out unless the brainstorm is specifically about architecture or technical direction.
+
+Before finishing this skill, apply the completion checklist in [shared pipeline instructions](../references/pipeline-config.md).

package/skills/02-plan/SKILL.md

@@ -7,6 +7,8 @@ description: "Turn requirements into a plan. Optional CEO-style strategic review
 
 Use this skill when requirements are ready to become an execution-ready plan.
 
+See [shared pipeline instructions](../references/pipeline-config.md) for model routing and pipeline behavior.
+
 ## Core rules
 
 - Before planning, read the `10-rules` skill and load `rules/common/development-workflow.md` and `rules/common/testing.md` for coding standards context.
@@ -76,3 +78,5 @@ Every unit must include:
   6. Run unit-level verification
 - **Verification commands**: exact commands to run
 - **Expected results**: what success looks like
+
+Before finishing this skill, apply the completion checklist in [shared pipeline instructions](../references/pipeline-config.md).

package/skills/03-work/SKILL.md

@@ -7,6 +7,8 @@ description: Execute plan-driven work in a controlled Phase 1 workflow.
 
 Use this skill when there is a plan path or a tightly scoped bare prompt ready for execution.
 
+See [shared pipeline instructions](../references/pipeline-config.md) for model routing and pipeline behavior.
+
 ## Core rules
 
 - Before execution, read the `10-rules` skill and load language-specific rules matching the active codebase (e.g. `rules/typescript/` for TS work).
@@ -64,3 +66,5 @@ When all units are done, provide:
 - **Commands run**: all verification commands executed
 - **Verification results**: pass/fail status for each
 - **Follow-up work**: any remaining risks or open questions
+
+Before finishing this skill, apply the completion checklist in [shared pipeline instructions](../references/pipeline-config.md).

package/skills/04-review/SKILL.md

@@ -7,6 +7,8 @@ description: "Review code with structured findings. Optional browser QA and regr
 
 Use this skill after implementation to review changes against the diff, the relevant plan, and prior learnings.
 
+See [shared pipeline instructions](../references/pipeline-config.md) for model routing and pipeline behavior.
+
 ## Core rules
 
 - Before reviewing, read the `10-rules` skill and load `rules/common/code-review.md` plus language-specific rules matching the changed files.
@@ -71,3 +73,5 @@ After review (and optional QA) is complete, hand off using `references/handoff.m
 2. Note fix commits if any were applied.
 3. Recommend `05-learn` if learnings are worth capturing.
 4. Recommend `03-work` if fixes need further implementation.
+
+Before finishing this skill, apply the completion checklist in [shared pipeline instructions](../references/pipeline-config.md).

package/skills/05-learn/SKILL.md

@@ -7,6 +7,8 @@ description: Capture solved problems as reusable solution artifacts.
 
 Use this skill after solving a problem so the repository gains a reusable learning in `docs/solutions/`.
 
+See [shared pipeline instructions](../references/pipeline-config.md) for model routing and pipeline behavior.
+
 ## Core rules
 
 - Every solution MUST include YAML frontmatter per `references/solution-schema.yaml` (title, category, severity, tags, applies_when).
@@ -30,3 +32,5 @@ Use this skill after solving a problem so the repository gains a reusable learni
 5. Choose the correct category using `references/category-map.md`.
 6. Write or update the solution artifact under `docs/solutions/<category>/`.
 7. Mention how future `02-plan` and `04-review` runs should benefit from the new learning.
+
+Before finishing this skill, apply the completion checklist in [shared pipeline instructions](../references/pipeline-config.md).

package/skills/references/pipeline-config.md

@@ -0,0 +1,49 @@
+# Shared pipeline instructions
+
+Use these rules in all Phase 1 skills: `01-brainstorm` → `02-plan` → `03-work` → `04-review` → `05-learn`.
+
+## Start of skill: model routing
+
+Run this checklist before normal skill workflow:
+
+1. Read `.pi/settings.json` from the project root.
+2. Parse `modelStrategy` (if missing, skip switching).
+3. Resolve current stage key:
+   - `01-brainstorm`
+   - `02-plan`
+   - `03-work`
+   - `04-review`
+   - `05-learn`
+4. Pick `targetModel = modelStrategy[stageKey] ?? modelStrategy.default`.
+5. If `targetModel` exists and differs from the current model, run `/model <targetModel>`.
+6. If switching fails, continue with current model and mention the failure once.
+
+## End of skill: status + optional auto-continue
+
+Before final completion, always output this block (replace placeholders with real values, never output angle-bracket placeholders literally):
+
+```
+---
+📊 Pipeline Status
+- Current: <stageKey>
+- Output: <main artifact path or N/A>
+- Next: <next skill command or Completed>
+---
+```
+
+Next step mapping:
+- `01-brainstorm` → `/skill:02-plan`
+- `02-plan` → `/skill:03-work`
+- `03-work` → `/skill:04-review`
+- `04-review` → `/skill:05-learn`
+- `05-learn` → `Completed`
+
+Then read `.pi/settings.json` → `pipeline.autoContinue`:
+- If `false` or missing, stop after the status block and wait for user input.
+- If current stage is `05-learn`, stop after status block.
+- If `true` and current stage is not `05-learn`, auto-continue is allowed only after stage-specific gates are satisfied:
+  - `01-brainstorm`: user has explicitly approved the design handoff.
+  - `02-plan`: review choice is resolved (A/B/C flow completed) and user confirmed to proceed.
+  - `04-review`: optional QA choice is resolved (A/B/C flow completed) and user confirmed to proceed.
+  - Any unclear/ambiguous state: do not auto-continue; stop and ask.
+- When gates are satisfied, automatically trigger the mapped next skill command.