pi-gsd 1.1.0 → 1.2.2

package/skills/gsd-remove-phase/SKILL.md

@@ -11,7 +11,7 @@ Output: Phase deleted, all subsequent phases renumbered, git commit as historica
 </objective>
 
 <execution_context>
-@.pi/get-shit-done/workflows/remove-phase.md
+@.pi/gsd/workflows/remove-phase.md
 </execution_context>
 
 <context>
@@ -21,6 +21,6 @@ Roadmap and state are resolved in-workflow via `init phase-op` and targeted read
 </context>
 
 <process>
-Execute the remove-phase workflow from @.pi/get-shit-done/workflows/remove-phase.md end-to-end.
+Execute the remove-phase workflow from @.pi/gsd/workflows/remove-phase.md end-to-end.
 Preserve all validation gates (future phase check, work check), renumbering logic, and commit.
 </process>

package/skills/gsd-remove-workspace/SKILL.md

@@ -13,10 +13,10 @@ Remove a workspace directory after confirmation. For worktree strategy, runs `gi
 </objective>
 
 <execution_context>
-@.pi/get-shit-done/workflows/remove-workspace.md
-@.pi/get-shit-done/references/ui-brand.md
+@.pi/gsd/workflows/remove-workspace.md
+@.pi/gsd/references/ui-brand.md
 </execution_context>
 
 <process>
-Execute the remove-workspace workflow from @.pi/get-shit-done/workflows/remove-workspace.md end-to-end.
+Execute the remove-workspace workflow from @.pi/gsd/workflows/remove-workspace.md end-to-end.
 </process>

package/skills/gsd-research-phase/SKILL.md

@@ -36,7 +36,7 @@ Normalize phase input in step 1 before any directory lookups.
 ## 0. Initialize Context
 
 ```bash
-INIT=$(node ".pi/get-shit-done/bin/gsd-tools.cjs" init phase-op "$ARGUMENTS")
+INIT=$(node ".pi/gsd/bin/pi-gsd-tools.cjs" init phase-op "$ARGUMENTS")
 if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fi
 ```
 
@@ -45,13 +45,13 @@ Extract from init JSON: `phase_dir`, `phase_number`, `phase_name`, `phase_found`
 Resolve researcher model:
 
 ```bash
-RESEARCHER_MODEL=$(node ".pi/get-shit-done/bin/gsd-tools.cjs" resolve-model gsd-phase-researcher --raw)
+RESEARCHER_MODEL=$(node ".pi/gsd/bin/pi-gsd-tools.cjs" resolve-model gsd-phase-researcher --raw)
 ```
 
 ## 1. Validate Phase
 
 ```bash
-PHASE_INFO=$(node ".pi/get-shit-done/bin/gsd-tools.cjs" roadmap get-phase "${phase_number}")
+PHASE_INFO=$(node ".pi/gsd/bin/pi-gsd-tools.cjs" roadmap get-phase "${phase_number}")
 ```
 
 **If `found` is false:** Error and exit. **If `found` is true:** Extract `phase_number`, `phase_name`, `goal` from JSON.

package/skills/gsd-resume-work/SKILL.md

@@ -17,11 +17,11 @@ Routes to the resume-project workflow which handles:
   </objective>
 
 <execution_context>
-@.pi/get-shit-done/workflows/resume-project.md
+@.pi/gsd/workflows/resume-project.md
 </execution_context>
 
 <process>
-**Follow the resume-project workflow** from `@.pi/get-shit-done/workflows/resume-project.md`.
+**Follow the resume-project workflow** from `@.pi/gsd/workflows/resume-project.md`.
 
 The workflow handles all resumption logic including:
 

package/skills/gsd-review/SKILL.md

@@ -12,7 +12,7 @@ planning via /gsd-plan-phase --reviews.
 </objective>
 
 <execution_context>
-@.pi/get-shit-done/workflows/review.md
+@.pi/gsd/workflows/review.md
 </execution_context>
 
 <context>
@@ -27,5 +27,5 @@ Phase number: extracted from $ARGUMENTS (required)
   </context>
 
 <process>
-Execute the review workflow from @.pi/get-shit-done/workflows/review.md end-to-end.
+Execute the review workflow from @.pi/gsd/workflows/review.md end-to-end.
 </process>

package/skills/gsd-review-backlog/SKILL.md

@@ -32,7 +32,7 @@ milestone sequence or remove stale entries.
    - Find the next sequential phase number in the active milestone
    - Rename the directory from `999.x-slug` to `{new_num}-slug`:
      ```bash
-     NEW_NUM=$(node ".pi/get-shit-done/bin/gsd-tools.cjs" phase add "${DESCRIPTION}" --raw)
+     NEW_NUM=$(node ".pi/gsd/bin/pi-gsd-tools.cjs" phase add "${DESCRIPTION}" --raw)
      ```
    - Move accumulated artifacts to the new phase directory
    - Update ROADMAP.md: move the entry from `## Backlog` section to the active phase list
@@ -46,7 +46,7 @@ milestone sequence or remove stale entries.
 6. **Commit changes:**
 
    ```bash
-   node ".pi/get-shit-done/bin/gsd-tools.cjs" commit "docs: review backlog - promoted N, removed M" --files .planning/ROADMAP.md
+   node ".pi/gsd/bin/pi-gsd-tools.cjs" commit "docs: review backlog - promoted N, removed M" --files .planning/ROADMAP.md
    ```
 
 7. **Report summary:**

package/skills/gsd-session-report/SKILL.md

@@ -8,9 +8,9 @@ Generate a structured SESSION_REPORT.md document capturing session outcomes, wor
 </objective>
 
 <execution_context>
-@.pi/get-shit-done/workflows/session-report.md
+@.pi/gsd/workflows/session-report.md
 </execution_context>
 
 <process>
-Execute the session-report workflow from @.pi/get-shit-done/workflows/session-report.md end-to-end.
+Execute the session-report workflow from @.pi/gsd/workflows/session-report.md end-to-end.
 </process>

package/skills/gsd-set-profile/SKILL.md

@@ -6,4 +6,4 @@ description: Switch model profile for GSD agents (quality/balanced/budget/inheri
 
 Show the following output to the user verbatim, with no extra commentary:
 
-!`node ".pi/get-shit-done/bin/gsd-tools.cjs" config-set-model-profile $ARGUMENTS --raw`
+!`node ".pi/gsd/bin/pi-gsd-tools.cjs" config-set-model-profile $ARGUMENTS --raw`

package/skills/gsd-settings/SKILL.md

@@ -16,11 +16,11 @@ Routes to the settings workflow which handles:
 </objective>
 
 <execution_context>
-@.pi/get-shit-done/workflows/settings.md
+@.pi/gsd/workflows/settings.md
 </execution_context>
 
 <process>
-**Follow the settings workflow** from `@.pi/get-shit-done/workflows/settings.md`.
+**Follow the settings workflow** from `@.pi/gsd/workflows/settings.md`.
 
 The workflow handles all logic including:
 1. Config file creation with defaults if missing

package/skills/gsd-setup-pi/SKILL.md

@@ -17,6 +17,7 @@ automatically copied into the consumer project's `.pi/extensions/` directory.
 This skill provides a manual fallback that performs the same wiring as `postinstall.js`.
 
 **What the extension does:**
+
 - `session_start` → background GSD update check (24 h cache in `~/.pi/cache/`)
 - `tool_call` (write/edit) → advisory workflow guard when `hooks.workflow_guard` is set
 - `tool_result` → context-usage monitor with debounced warnings
@@ -27,24 +28,25 @@ This skill provides a manual fallback that performs the same wiring as `postinst
 **Target location in the consumer project:**
 `.pi/extensions/gsd-hooks.ts`
 
-**settings.json entry (belt-and-suspenders — pi also auto-discovers from `.pi/extensions/`):**
+**settings.json entry (belt-and-suspenders - pi also auto-discovers from `.pi/extensions/`):**
 `{ "extensions": ["<absolute-path-to-.pi/extensions/gsd-hooks.ts>"] }`
 </context>
 
 <process>
 
-## Step 1 — Locate the pi-gsd package
+## Step 1 - Locate the pi-gsd package
 
 Resolve the pi-gsd package root (where `gsd-hooks.ts` lives):
-1. Try `node -e "console.log(require.resolve('pi-gsd/package.json'))"` — strip `/package.json` suffix to get PKG_DIR.
+
+1. Try `node -e "console.log(require.resolve('pi-gsd/package.json'))"` - strip `/package.json` suffix to get PKG_DIR.
 2. If that fails, try common global paths:
    - `~/.bun/install/global/node_modules/pi-gsd`
    - `/home/linuxbrew/.linuxbrew/lib/node_modules/pi-gsd`
    - Output of `npm root -g` + `/pi-gsd`
 3. Confirm the extension source exists at `<PKG_DIR>/.gsd/extensions/gsd-hooks.ts`.
-   If the source cannot be found, report the error clearly and stop — do not proceed to Step 2.
+   If the source cannot be found, report the error clearly and stop - do not proceed to Step 2.
 
-## Step 2 — Check current project extension status
+## Step 2 - Check current project extension status
 
 In the current working directory (the consumer project):
 
@@ -52,7 +54,7 @@ In the current working directory (the consumer project):
 - **Check B:** Does `.pi/settings.json` exist? If yes, does `extensions` array include an absolute path to the extension file?
 - **Check C:** Does `.pi/extensions/` directory exist?
 
-## Step 3 — Install or confirm
+## Step 3 - Install or confirm
 
 ### If extension is MISSING (Check A failed):
 
@@ -61,21 +63,21 @@ In the current working directory (the consumer project):
 3. Update `.pi/settings.json`:
    - If the file does not exist, create it as `{ "extensions": ["<absolute-path>/.pi/extensions/gsd-hooks.ts"] }`.
    - If the file exists but `extensions` array is missing or does not include the path, add the absolute path.
-   - Preserve all other existing settings — merge, do not overwrite.
+   - Preserve all other existing settings - merge, do not overwrite.
 4. Report: `✓ GSD extension installed at .pi/extensions/gsd-hooks.ts`
 5. Report: `✓ .pi/settings.json updated`
 
 ### If extension is PRESENT (Check A passed):
 
 1. Confirm the file is non-empty (not a zero-byte stub).
-2. Confirm it contains the marker comment `gsd-extension-version:` — indicating it is the genuine GSD extension, not a stale copy from another tool.
-3. Check Check B — if `settings.json` is missing or the extension path is absent, add it now (same logic as missing case, step 3).
+2. Confirm it contains the marker comment `gsd-extension-version:` - indicating it is the genuine GSD extension, not a stale copy from another tool.
+3. Check Check B - if `settings.json` is missing or the extension path is absent, add it now (same logic as missing case, step 3).
 4. Report:
    - `✓ GSD extension present at .pi/extensions/gsd-hooks.ts`
    - `✓ hooks: session_start (update-check), tool_call (workflow-guard), tool_result (context-monitor)`
-   - `✓ .pi/settings.json` — either "already registered" or "path added"
+   - `✓ .pi/settings.json` - either "already registered" or "path added"
 
-## Step 4 — Summarise status
+## Step 4 - Summarise status
 
 Print a concise status table:
 
@@ -90,7 +92,7 @@ Extension version  gsd-extension-version: X.Y.Z   (value)
 
 If any item is `✗` after repair attempts, explain what failed and the manual fix.
 
-## Step 5 — Route to first-time setup
+## Step 5 - Route to first-time setup
 
 Ask the user:
 
@@ -98,6 +100,6 @@ Ask the user:
 
 - **Yes / first time:** Run `/gsd-new-project` to initialise `.planning/`, requirements, and roadmap.
 - **Already set up:** Run `/gsd-progress` to show current project state and next steps.
-- **Just checking:** Report "All done — hooks verified." and stop.
+- **Just checking:** Report "All done - hooks verified." and stop.
 
 </process>

package/skills/gsd-ship/SKILL.md

@@ -10,7 +10,7 @@ Closes the plan → execute → verify → ship loop.
 </objective>
 
 <execution_context>
-@.pi/get-shit-done/workflows/ship.md
+@.pi/gsd/workflows/ship.md
 </execution_context>
 
-Execute the ship workflow from @.pi/get-shit-done/workflows/ship.md end-to-end.
+Execute the ship workflow from @.pi/gsd/workflows/ship.md end-to-end.

package/skills/gsd-stats/SKILL.md

@@ -8,13 +8,13 @@ Display comprehensive project statistics including phase progress, plan executio
 </objective>
 
 <execution_context>
-@.pi/get-shit-done/workflows/stats.md
+@.pi/gsd/workflows/stats.md
 </execution_context>
 
 <process>
-1. Run: `gsd-tools stats --output toon`
+1. Run: `pi-gsd-tools stats --output toon`
    - If successful, present the toon output to the user.
-   - If the command fails or toon output is unavailable, fall back to: `gsd-tools stats` (plain JSON output).
+   - If the command fails or toon output is unavailable, fall back to: `pi-gsd-tools stats` (plain JSON output).
 
-2. Execute the stats workflow from @.pi/get-shit-done/workflows/stats.md end-to-end.
+2. Execute the stats workflow from @.pi/gsd/workflows/stats.md end-to-end.
 </process>

package/skills/gsd-thread/SKILL.md

@@ -63,7 +63,7 @@ Create a new thread:
 1. Generate slug from description:
 
    ```bash
-   SLUG=$(node ".pi/get-shit-done/bin/gsd-tools.cjs" generate-slug "$ARGUMENTS")
+   SLUG=$(node ".pi/gsd/bin/pi-gsd-tools.cjs" generate-slug "$ARGUMENTS")
    ```
 
 2. Create the threads directory if needed:
@@ -105,7 +105,7 @@ Create a new thread:
 5. Commit:
 
    ```bash
-   node ".pi/get-shit-done/bin/gsd-tools.cjs" commit "docs: create thread - ${ARGUMENTS}" --files ".planning/threads/${SLUG}.md"
+   node ".pi/gsd/bin/pi-gsd-tools.cjs" commit "docs: create thread - ${ARGUMENTS}" --files ".planning/threads/${SLUG}.md"
    ```
 
 6. Report:

package/skills/gsd-ui-phase/SKILL.md

@@ -10,8 +10,8 @@ Flow: Validate → Research UI → Verify UI-SPEC → Done
 </objective>
 
 <execution_context>
-@.pi/get-shit-done/workflows/ui-phase.md
-@.pi/get-shit-done/references/ui-brand.md
+@.pi/gsd/workflows/ui-phase.md
+@.pi/gsd/references/ui-brand.md
 </execution_context>
 
 <context>
@@ -19,6 +19,6 @@ Phase number: $ARGUMENTS - optional, auto-detects next unplanned phase if omitte
 </context>
 
 <process>
-Execute @.pi/get-shit-done/workflows/ui-phase.md end-to-end.
+Execute @.pi/gsd/workflows/ui-phase.md end-to-end.
 Preserve all workflow gates.
 </process>

package/skills/gsd-ui-review/SKILL.md

@@ -10,8 +10,8 @@ Output: {phase_num}-UI-REVIEW.md
 </objective>
 
 <execution_context>
-@.pi/get-shit-done/workflows/ui-review.md
-@.pi/get-shit-done/references/ui-brand.md
+@.pi/gsd/workflows/ui-review.md
+@.pi/gsd/references/ui-brand.md
 </execution_context>
 
 <context>
@@ -19,6 +19,6 @@ Phase: $ARGUMENTS - optional, defaults to last completed phase.
 </context>
 
 <process>
-Execute @.pi/get-shit-done/workflows/ui-review.md end-to-end.
+Execute @.pi/gsd/workflows/ui-review.md end-to-end.
 Preserve all workflow gates.
 </process>

package/skills/gsd-update/SKILL.md

@@ -17,11 +17,11 @@ Routes to the update workflow which handles:
 </objective>
 
 <execution_context>
-@.pi/get-shit-done/workflows/update.md
+@.pi/gsd/workflows/update.md
 </execution_context>
 
 <process>
-**Follow the update workflow** from `@.pi/get-shit-done/workflows/update.md`.
+**Follow the update workflow** from `@.pi/gsd/workflows/update.md`.
 
 The workflow handles all logic including:
 1. Installed version detection (local/global)

package/skills/gsd-validate-phase/SKILL.md

@@ -13,7 +13,7 @@ Output: updated VALIDATION.md + generated test files.
 </objective>
 
 <execution_context>
-@.pi/get-shit-done/workflows/validate-phase.md
+@.pi/gsd/workflows/validate-phase.md
 </execution_context>
 
 <context>
@@ -21,6 +21,6 @@ Phase: $ARGUMENTS - optional, defaults to last completed phase.
 </context>
 
 <process>
-Execute @.pi/get-shit-done/workflows/validate-phase.md.
+Execute @.pi/gsd/workflows/validate-phase.md.
 Preserve all workflow gates.
 </process>

package/skills/gsd-verify-work/SKILL.md

@@ -12,8 +12,8 @@ Output: {phase_num}-UAT.md tracking all test results. If issues found: diagnosed
 </objective>
 
 <execution_context>
-@.pi/get-shit-done/workflows/verify-work.md
-@.pi/get-shit-done/templates/UAT.md
+@.pi/gsd/workflows/verify-work.md
+@.pi/gsd/templates/UAT.md
 </execution_context>
 
 <context>
@@ -25,6 +25,6 @@ Context files are resolved inside the workflow (`init verify-work`) and delegate
 </context>
 
 <process>
-Execute the verify-work workflow from @.pi/get-shit-done/workflows/verify-work.md end-to-end.
+Execute the verify-work workflow from @.pi/gsd/workflows/verify-work.md end-to-end.
 Preserve all workflow gates (session management, test presentation, diagnosis, fix planning, routing).
 </process>

package/skills/gsd-workstreams/SKILL.md

@@ -68,5 +68,5 @@ Set the workstream as active and suggest `/gsd-resume-work --ws <name>`.
 
 ## Step 3: Display Results
 
-Format the JSON output from gsd-tools into a human-readable display.
+Format the JSON output from pi-gsd-tools into a human-readable display.
 Include the `${GSD_WS}` flag in any routing suggestions.