@leing2021/super-pi 0.22.0 → 0.23.0

package/skills/06-next/SKILL.md

@@ -1,11 +1,11 @@
 ---
 name: 06-next
-description: Inspect workflow state and recommend the single best next Compound Engineering skill.
+description: "Inspect workflow state and recommend the single best next Compound Engineering skill. Use --verbose for a full status report."
 ---
 
 # Next
 
-Use this skill when the user wants to know what to run next in the Compound Engineering workflow.
+Use this skill when the user wants to know what to run next in the Compound Engineering workflow, or wants a full status report of the current project state.
 
 ## Core rules
 
@@ -15,18 +15,43 @@ Use this skill when the user wants to know what to run next in the Compound Engi
 - Do not execute the recommended skill — only suggest it.
 - If the workflow state suggests multiple valid paths, pick the one closest to completing a full loop.
 
-## Workflow
+## Two modes
+
+### Default mode: "what's next?"
+
+When the user asks "what should I do next?", "continue", or runs `/skill:06-next`:
+
+1. Call `workflow_state` with the repo root.
+2. Apply the recommendation logic from `references/recommendation-logic.md`.
+3. Return:
+   - **Recommended skill name**
+   - **Why** this is the next step
+   - **Brief** summary of current workflow state (1-2 lines)
+
+### Verbose mode: "full status"
+
+When the user asks "show status", "what's the current state", or explicitly requests a detailed report:
 
 1. Call `workflow_state` with the repo root.
-2. Read the structured state: brainstorm count, plan count, solution count, run count, and latest artifact per category.
-3. Apply the recommendation logic from `references/recommendation-logic.md`.
-4. Return the recommended skill and why.
+2. Call `session_history` with `latest` operation to check recent executions.
+3. Return:
+   - Latest relevant brainstorm (path + brief summary)
+   - Latest relevant plan (path + brief summary)
+   - Latest relevant solution (path + brief summary)
+   - Latest runtime artifacts under `.context/compound-engineering/`
+   - Recommended next step with reason
+   - Overall workflow phase summary
 
-## Output format
+## Artifact locations
 
-- Recommended skill name
-- Why this is the next step
-- Brief summary of current workflow state
+| Artifact | Path |
+|---|---|
+| Brainstorm | `docs/brainstorms/` |
+| Plan | `docs/plans/` |
+| Solution | `docs/solutions/` |
+| Runtime | `.context/compound-engineering/` |
+
+If `workflow_state` is not available, fall back to `bash` with `ls` and `find` to check which directories and recent files exist, then use `read` on the most relevant recent artifact.
 
 ## Available skills
 
@@ -35,3 +60,6 @@ Use this skill when the user wants to know what to run next in the Compound Engi
 - `03-work` — execute the plan
 - `04-review` — review changes with structured findings
 - `05-learn` — capture learnings as solution artifacts
+- `07-worktree` — isolated git worktree development
+
+Before finishing this skill, apply the completion checklist in [shared pipeline instructions](../references/pipeline-config.md).

package/skills/06-next/references/recommendation-logic.md

@@ -42,5 +42,5 @@ If brainstorm, plan, and solution all exist:
 ## Fallback
 
 If no rule matches cleanly:
-- Recommend `08-status`
-- Reason: State is ambiguous. Get a detailed report before deciding.
+- Summarize the ambiguous state
+- Ask the user what they want to focus on

package/skills/07-worktree/SKILL.md

@@ -3,25 +3,26 @@ name: 07-worktree
 description: Create and manage git worktrees for isolated feature development.
 ---
 
-# 03-worktree
+# Worktree
 
-Use this skill when you need to create an isolated git worktree for feature work, merge changes back, or clean up after completion.
+Use this skill when you need optional isolated git worktree development for large, risky, or parallel feature work, then merge changes back or clean up after completion.
 
 ## Core rules
 
 - Use the `worktree_manager` tool for all git worktree operations.
-- Default behavior is to **automatically create** a worktree with a descriptive branch name derived from the plan or task.
+- Create a worktree only when the user explicitly asks for isolation, or when the task is large/risky enough and the user confirms.
+- Use a descriptive branch name derived from the plan or task.
 - After creation, report the worktree path so that `03-work` can execute inside it.
-- On completion, merge back and clean up.
+- On completion, offer to merge back and clean up; ask for confirmation before changing the main worktree or deleting branches.
 - Never force operations — if a worktree already exists, report its status instead of creating a duplicate.
 
 ## Workflow
 
-1. **Create**: Use `worktree_manager` with operation `create` to spin up a new worktree with a feature branch.
-2. **Detect**: Use `worktree_manager` with operation `detect` to check if already inside a worktree.
+1. **Detect**: Use `worktree_manager` with operation `detect` to check if already inside a worktree.
+2. **Create**: When confirmed, use `worktree_manager` with operation `create` to spin up a new worktree with a feature branch.
 3. **Execute**: Run `03-work` inside the worktree directory.
-4. **Merge**: Use `worktree_manager` with operation `merge` to merge the feature branch back to main.
-5. **Cleanup**: Use `worktree_manager` with operation `cleanup` to remove the worktree and delete the branch.
+4. **Merge**: After user confirmation, use `worktree_manager` with operation `merge` to merge the feature branch back to main.
+5. **Cleanup**: After user confirmation, use `worktree_manager` with operation `cleanup` to remove the worktree and delete the branch.
 
 ## Output
 

package/skills/{09-help → 08-help}/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: 09-help
+name: 08-help
 description: Explain when to use each Compound Engineering Phase 1 skill and how they connect.
 ---
 
@@ -14,7 +14,7 @@ Use this skill when the user asks how to use the package, which workflow step co
 - `03-work` — use when there is a plan or a tightly scoped task ready for controlled execution.
 - `04-review` — use after code changes to produce structured findings. After code review, user can optionally extend to browser-based QA testing (find visual/functional bugs with agent-browser) and regression test generation.
 - `05-learn` — use after solving a problem so the repo gains a durable learning in `docs/solutions/`.
-- `08-status` — use when the user wants to know which artifact already exists and what the next workflow step should be.
+- `06-next` — use when the user wants to know what to run next, or wants a full status report of the current project state. Default mode recommends one next step; verbose mode (`--verbose` or ask "show status") shows full artifact details.
 
 ## Recommended flow
 
@@ -30,7 +30,7 @@ Use this skill when the user asks how to use the package, which workflow step co
    - Optionally extend to **Browser QA** for visual and functional bug finding.
    - Or **Browser QA + Regression Tests** to also generate automated test coverage.
 5. Capture key learnings with `05-learn`.
-6. Use `08-status` at any point to inspect repo-local workflow state.
+6. Use `06-next` at any point to check what to do next, or ask for a full status report.
 
 ## Output
 

package/skills/{09-help → 08-help}/references/workflow-sequence.md

@@ -6,4 +6,5 @@
 4. `04-review` → inspect the changes (optionally + Browser QA / QA + Regression Tests)
 5. `05-learn` → save key learnings
 
-Use `08-status` at any point to see where you are.
+Use `06-next` at any point to see where you are and what to do next.
+Use `07-worktree` for isolated feature development on a separate branch.

package/skills/references/language-detection.md

@@ -0,0 +1,44 @@
+# Language Detection
+
+Detect the project's primary language by checking for these files in the repo root:
+
+| File(s) | Language | Rules directory |
+|---------|----------|----------------|
+| `tsconfig.json` | TypeScript | `rules/typescript/` |
+| `package.json` (without `tsconfig.json`) | JavaScript | `rules/typescript/` |
+| `Cargo.toml` | Rust | `rules/rust/` |
+| `go.mod` | Go | `rules/golang/` |
+| `pubspec.yaml` | Dart | `rules/dart/` |
+| `pom.xml` / `build.gradle` | Java | `rules/java/` |
+| `*.sln` / `*.csproj` | C# | `rules/csharp/` |
+| `Package.swift` | Swift | `rules/swift/` |
+| `requirements.txt` / `pyproject.toml` / `setup.py` | Python | `rules/python/` |
+| `composer.json` | PHP | `rules/php/` |
+| `Makefile.PL` / `cpanfile` | Perl | `rules/perl/` |
+| `build.gradle.kts` | Kotlin | `rules/kotlin/` |
+
+## Rules loading strategy
+
+Rules are loaded from two locations with priority:
+
+1. **Project-level** `{repo-root}/rules/` — takes priority, survives `pi update`.
+2. **Package-level** `rules/` in the super-pi package — built-in defaults.
+
+Check project-level first. If a file exists there for the topic, use it. Otherwise fall back to package-level.
+
+## Rule precedence
+
+```
+language-specific > web > common
+```
+
+Override mapping by topic:
+- `common/testing.md` ← `web/testing.md` ← `<lang>/testing.md`
+- `common/coding-style.md` ← `web/coding-style.md` ← `<lang>/coding-style.md`
+- `common/patterns.md` ← `web/patterns.md` ← `<lang>/patterns.md`
+- `common/security.md` ← `web/security.md` ← `<lang>/security.md`
+- `common/hooks.md` ← `web/hooks.md` ← `<lang>/hooks.md`
+
+## Do not load all rules at once
+
+Only load what the current task needs. See each skill's SKILL.md for phase-specific loading instructions.