@plannotator/pi-extension 0.19.23 → 0.19.24

package/skills/plannotator-compound/SKILL.md

@@ -21,9 +21,10 @@ Research integrity is paramount — every file must be read, no skipping.
 
 Before starting the analysis, determine which data source is available.
 
-1. **Plannotator mode (first-class)** — Check `~/.plannotator/plans/`. If it
-   exists and contains `*-denied.md` files, use this mode. The entire workflow
-   below is written for Plannotator data.
+1. **Plannotator mode (first-class)** — Determine the Plannotator data directory:
+   use `$PLANNOTATOR_DATA_DIR` if set, otherwise `~/.plannotator`. Check the
+   `plans/` subdirectory there. If it exists and contains `*-denied.md` files,
+   use this mode. The entire workflow below is written for Plannotator data.
 
 2. **Claude Code fallback mode** — If the Plannotator archive is absent or
    contains no denied plans, check `~/.claude/projects/`. If present, read
@@ -54,7 +55,7 @@ In either mode, proceed to Previous Report Detection below.
 After locating the plans directory, check for existing reports:
 
 ```
-ls ~/.plannotator/plans/compound-planning-report*.html
+ls ${PLANNOTATOR_DATA_DIR:-~/.plannotator}/plans/compound-planning-report*.html
 ```
 
 Reports follow a versioned naming scheme:
@@ -518,10 +519,10 @@ every future planning session automatically.
 The hook file lives at:
 
 ```
-~/.plannotator/hooks/compound/enterplanmode-improve-hook.txt
+${PLANNOTATOR_DATA_DIR:-~/.plannotator}/hooks/compound/enterplanmode-improve-hook.txt
 ```
 
-Create the `~/.plannotator/hooks/compound/` directory if it doesn't exist.
+Create the `hooks/compound/` directory inside the data directory if it doesn't exist.
 
 The file contents should be the corrective prompt instructions from Phase 3 —
 the same numbered list that appears in section 7 of the HTML report. Write them

package/skills/plannotator-compound/references/claude-code-fallback.md

@@ -3,7 +3,7 @@
 Read this file only when the user does **not** have a usable Plannotator archive.
 
 This is the secondary path for ordinary Claude Code users whose denial history
-exists in `~/.claude/projects/` rather than `~/.plannotator/plans/`.
+exists in `~/.claude/projects/` rather than the Plannotator plans directory (`$PLANNOTATOR_DATA_DIR/plans/` or `~/.plannotator/plans/`).
 
 The goal is the same as the main skill:
 
@@ -107,7 +107,7 @@ does not contain those artifacts.
 ### Previous Report Detection In Fallback Mode
 
 Previous report detection still applies. Check the user's home directory or
-`~/.plannotator/plans/` for existing `compound-planning-report*.html` files. If
+the Plannotator plans directory (`${PLANNOTATOR_DATA_DIR:-~/.plannotator}/plans/`) for existing `compound-planning-report*.html` files. If
 found, offer the same incremental vs full choice as Plannotator mode. In
 incremental mode, filter the parser output by timestamp rather than by filename
 date — use the `timestamp` field in each JSON record.
@@ -246,7 +246,7 @@ feedback and therefore could not contribute to the pattern analysis.
 ### Versioned Report Naming
 
 Versioned naming (`v2`, `v3`, etc.) applies to fallback mode too. Save reports
-to `~/.plannotator/plans/` (create the directory if it doesn't exist) so that
+to the Plannotator plans directory (`${PLANNOTATOR_DATA_DIR:-~/.plannotator}/plans/`, create the directory if it doesn't exist) so that
 all compound planning reports live in the same location regardless of data source.
 
 ## Summary In Fallback Mode