@leing2021/super-pi 0.19.4 → 0.19.5

package/README.md

@@ -275,7 +275,7 @@ Three CE skills auto-trigger rule loading at their entry points:
 
 | Skill | Rules pre-loaded |
 |-------|-----------------|
-| `02-plan` | `common/development-workflow.md` + `common/testing.md` |
+| `02-plan` | `common/` rules + language detection + matching language rules (e.g. `rules/typescript/`) |
 | `03-work` | Language-specific rules matching the active codebase |
 | `04-review` | `common/code-review.md` + language rules for changed files |
 
@@ -381,6 +381,12 @@ Not a fork. Not a wrapper. Methodologies extracted and rebuilt with Pi's native
 
 ## Changelog
 
+### 0.19.5 — Plan skill missing language rules fix
+- Fixed `02-plan` not loading language-specific rules (e.g. `rules/typescript/`) during the planning phase — only `common/` rules were loaded.
+- Updated `10-rules` SKILL.md Pre-flight to require language detection in the planning phase.
+- Updated `02-plan` SKILL.md Core rules to a 4-step progressive loading strategy (common → language detection → language rules → web rules).
+- Synced `README.md` and `README_CN.md` skill table to reflect the change.
+
 ### 0.19.4 — Read output filter markdown truncation fix
 - Fixed `read-output-filter` over-truncating markdown files: raised markdown threshold from 2KB → 8KB.
 - Improved `filterMarkdown()` to fully preserve list items (`-`, `*`, numbered) and keep first 3 lines of paragraphs (was 1).

package/package.json

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

package/skills/02-plan/SKILL.md

@@ -11,7 +11,11 @@ See [shared pipeline instructions](../references/pipeline-config.md) for model r
 
 ## 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.
+- Before planning, read the `10-rules` skill and load:
+  1. `rules/common/development-workflow.md` and `rules/common/testing.md`
+  2. **Detect the project's primary language** (check for `tsconfig.json` → typescript, `package.json` without tsconfig → javascript, `Cargo.toml` → rust, `go.mod` → golang, `pubspec.yaml` → dart, `pom.xml`/`build.gradle` → java, `*.sln`/`*.csproj` → csharp, `Package.swift` → swift, `requirements.txt`/`pyproject.toml`/`setup.py` → python, `composer.json` → php, `Makefile.PL`/`cpanfile` → perl, `build.gradle.kts` → kotlin)
+  3. Load all files in the matching language-specific rules directory (e.g. `rules/typescript/`)
+  4. If the task involves frontend/browser concerns, also load `rules/web/` files
 - Search `docs/brainstorms/` for a relevant requirements artifact first.
 - Search solutions with grep-first strategy: extract keywords from the task → `bash grep -rl "tags:.*keyword" docs/solutions/ ~/.pi/agent/docs/solutions/` → read only frontmatter (first 15 lines) of matching files → score by severity + tag relevance → fully read top 3. Search both project-level (`docs/solutions/`) and global-level (`~/.pi/agent/docs/solutions/`). If no matches, report "No relevant solutions found" and proceed.
 - Write the final plan to `docs/plans/`.

package/skills/10-rules/SKILL.md

@@ -23,6 +23,8 @@ Do not load the entire rules tree by default. Read only the files needed for the
 Read at minimum:
 - `rules/common/development-workflow.md`
 - `rules/common/testing.md`
+- **Detect the active language** from the project: check for `tsconfig.json` → typescript, `package.json` (without tsconfig) → javascript, `Cargo.toml` → rust, `go.mod` → golang, `pubspec.yaml` → dart, `pom.xml`/`build.gradle` → java, `*.sln`/`*.csproj` → csharp, `Package.swift` → swift, `requirements.txt`/`pyproject.toml`/`setup.py` → python, `composer.json` → php, `Makefile.PL`/`cpanfile` → perl, `build.gradle.kts` → kotlin. Load all files in the matching language directory (e.g. `rules/typescript/`).
+- `rules/web/` files if the task involves frontend/browser concerns
 
 ### Before implementation (03-work)