@pareto4/pp-core 1.5.2 → 1.5.4

package/agents/pp-verifier.md

@@ -235,7 +235,7 @@ overrides:
 
 ## Step 4: Verify Artifacts (Three Levels)
 
-Use `gsd-tools query` for artifact verification against must_haves in PLAN frontmatter:
+Use `pp-tools query` for artifact verification against must_haves in PLAN frontmatter:
 
 ```bash
 ARTIFACT_RESULT=$(pp_run query verify.artifacts "$PLAN_PATH")
@@ -341,7 +341,7 @@ grep -r -A 3 "<${COMPONENT_NAME}" "${search_path:-src/}" --include="*.tsx" 2>/de
 
 Key links are critical connections. If broken, the goal fails even with all artifacts present.
 
-Use `gsd-tools query` for key link verification against must_haves in PLAN frontmatter:
+Use `pp-tools query` for key link verification against must_haves in PLAN frontmatter:
 
 ```bash
 LINKS_RESULT=$(pp_run query verify.key-links "$PLAN_PATH")
@@ -601,7 +601,7 @@ Classify status using this decision tree IN ORDER (most restrictive first):
 
 **A ⚠️ PRESENT_BEHAVIOR_UNVERIFIED truth is never FAILED and never VERIFIED.** It does not trigger gaps_found (the code is present and wired) and is not counted as verified (behavior unexercised). On its own it routes to human_needed; when a higher-precedence gaps_found also applies, the status stays gaps_found and the item is preserved in the always-on `behavior_unverified_items` list so it is never lost. Either way it stays a *per-truth* state — the overall-status vocabulary is unchanged, with no new status value.
 
-> **Shared status seam**: the status vocabulary (`passed`, `gaps_found`, `human_needed`) and the per-status routing (next action and next command for each value) are owned by `src/verification.cts` via `pp_run query verification.status`. This agent is the single emitter of the frontmatter status field; consumers (ship.md, execute-phase.md) read routing from that query instead of re-deriving it.
+> **Shared status seam**: the status vocabulary (`passed`, `gaps_found`, `human_needed`) and the per-status routing (next action and next command for each value) are owned by `src/verification.cts` via `pp-tools query verification.status`. This agent is the single emitter of the frontmatter status field; consumers (ship.md, execute-phase.md) read routing from that query instead of re-deriving it.
 
 **Score (presence- vs behavior-verified split):**
 
@@ -700,7 +700,7 @@ Deferred items are informational only — they do not require closure plans.
 USER_STORY_VALID=$(pp_run query user-story.validate --story "$PHASE_GOAL" --pick valid)
 ```
 
-If `valid != true`, refuse to verify. Surface the discrepancy and ask the user to run `/gsd mvp-phase ${PHASE}` to set a proper User Story goal. The verb owns the canonical regex `/^As a .+, I want to .+, so that .+\.$/` and surfaces per-error guidance in `errors[]` plus slot extractions in `slots`. Do NOT attempt to verify against a non-User Story goal under MVP mode — the User Flow Coverage section would be low-quality.
+If `valid != true`, refuse to verify. Surface the discrepancy and ask the user to run `/pp:mvp-phase ${PHASE}` to set a proper User Story goal. The verb owns the canonical regex `/^As a .+, I want to .+, so that .+\.$/` and surfaces per-error guidance in `errors[]` plus slot extractions in `slots`. Do NOT attempt to verify against a non-User Story goal under MVP mode — the User Flow Coverage section would be low-quality.
 
 **Mode is all-or-nothing per phase** (PRD decision Q1, inherited from Phase 1). The MVP Mode Verification rules apply to the whole phase or not at all.
 

package/bin/install.js

@@ -386,7 +386,7 @@ const _profileArgRaw = (() => {
 // 1. --minimal / --core-only → 'core' (back-compat alias)
 // 2. --profile=<name> → named profile
 // 3. neither → 'full' (default, back-compat)
-// Note: when re-running as `gsd update` the marker is read later (after
+// Note: when re-running as `pp update` the marker is read later (after
 // configDir is resolved) and may override 'full' — see writeActiveProfile call below.
 const _profileIsCore = _profileArgRaw === 'core';
 const _requestedProfileName = (hasMinimal || _profileIsCore) ? 'core' : (_profileArgRaw || null);
@@ -534,15 +534,15 @@ function getGlobalDir(runtime, explicitDir = null) {
   return getGlobalConfigDir(runtime, explicitDir);
 }
 const banner = '\n' +
-  cyan + '   ██████╗ ███████╗██████╗\n' +
-  '  ██╔════╝ ██╔════╝██╔══██╗\n' +
-  '  ██║  ███╗███████╗██║  ██║\n' +
-  '  ██║   ██║╚════██║██║  ██║\n' +
-  '  ╚██████╔╝███████║██████╔╝\n' +
-  '   ╚═════╝ ╚══════╝╚═════╝' + reset + '\n' +
+  cyan + '  ██████╗ ██████╗      ██████╗ ██████╗ ██████╗ ███████╗\n' +
+  '  ██╔══██╗██╔══██╗    ██╔════╝██╔═══██╗██╔══██╗██╔════╝\n' +
+  '  ██████╔╝██████╔╝    ██║     ██║   ██║██████╔╝█████╗\n' +
+  '  ██╔═══╝ ██╔═══╝     ██║     ██║   ██║██╔══██╗██╔══╝\n' +
+  '  ██║     ██║         ╚██████╗╚██████╔╝██║  ██║███████╗\n' +
+  '  ╚═╝     ╚═╝          ╚═════╝ ╚═════╝ ╚═╝  ╚═╝╚══════╝' + reset + '\n' +
   '\n' +
-  '  GSD Core ' + dim + 'v' + pkg.version + reset + '\n' +
-  '  Git. Ship. Done.\n' +
+  '  pp-core ' + dim + 'v' + pkg.version + reset + '\n' +
+  '  The Pareto delivery framework.\n' +
   '  A meta-prompting, context engineering and spec-driven\n' +
   '  development workflows for Claude Code, OpenCode, Gemini, Kimi CLI, Kilo, Codex, Copilot, Antigravity, Cursor, Windsurf, Augment, Trae, Qwen Code, Hermes Agent, Cline and CodeBuddy.\n';
 
@@ -601,7 +601,7 @@ if (hasUninstall) {
 
 // Show help if requested
 if (hasHelp) {
-  console.log(`  ${yellow}Usage:${reset} npx ${pkg.name} [options]\n\n  ${yellow}Options:${reset}\n    ${cyan}-g, --global${reset}              Install globally (to config directory)\n    ${cyan}-l, --local${reset}               Install locally (to current directory)\n    ${cyan}--claude${reset}                  Install for Claude Code only\n    ${cyan}--opencode${reset}                Install for OpenCode only\n    ${cyan}--gemini${reset}                  Install for Gemini only\n    ${cyan}--kilo${reset}                    Install for Kilo only\n    ${cyan}--codex${reset}                   Install for Codex only\n    ${cyan}--kimi${reset}                    Install for Kimi CLI only\n    ${cyan}--copilot${reset}                 Install for Copilot only\n    ${cyan}--antigravity${reset}             Install for Antigravity only\n    ${cyan}--cursor${reset}                  Install for Cursor only\n    ${cyan}--windsurf${reset}                Install for Windsurf only\n    ${cyan}--augment${reset}                 Install for Augment only\n    ${cyan}--trae${reset}                    Install for Trae only\n    ${cyan}--qwen${reset}                    Install for Qwen Code only\n    ${cyan}--hermes${reset}                  Install for Hermes Agent only\n    ${cyan}--cline${reset}                   Install for Cline only\n    ${cyan}--codebuddy${reset}              Install for CodeBuddy only\n    ${cyan}--all${reset}                     Install for all runtimes\n    ${cyan}-u, --uninstall${reset}           Uninstall GSD (remove all GSD files)\n    ${cyan}-c, --config-dir <path>${reset}   Specify custom config directory\n    ${cyan}-h, --help${reset}                Show this help message\n    ${cyan}--force-statusline${reset}        Replace existing statusline config\n    ${cyan}--portable-hooks${reset}          Emit \$HOME-relative hook paths in settings.json\n                              (for WSL/Docker bind-mount setups; also GSD_PORTABLE_HOOKS=1)\n    ${cyan}--profile=<name>${reset}         Install a named skill profile. Profiles:\n                              core     — ${PROFILES.core.length} main-loop skills incl. phase (~130 desc tokens)\n                              standard — ${PROFILES.standard.length} skills incl. phase, review, config (~700)\n                              full     — all skills (default)\n                              Composable: --profile=core,audit installs union of closures.\n                              Profile is persisted and respected by \`gsd update\`.\n    ${cyan}--minimal${reset}                 Alias for --profile=core (back-compat).\n                              Cuts cold-start overhead from ~12k tokens to ~700.\n                              Alias: --core-only.\n\n  ${yellow}Examples:${reset}\n    ${dim}# Interactive install (prompts for runtime and location)${reset}\n    npx ${pkg.name}\n\n    ${dim}# Install for Claude Code globally${reset}\n    npx ${pkg.name} --claude --global\n\n    ${dim}# Install for Gemini globally${reset}\n    npx ${pkg.name} --gemini --global\n\n    ${dim}# Install for Kilo globally${reset}\n    npx ${pkg.name} --kilo --global\n\n    ${dim}# Install for Codex globally${reset}\n    npx ${pkg.name} --codex --global\n\n    ${dim}# Install for Kimi CLI globally${reset}\n    npx ${pkg.name} --kimi --global\n\n    ${dim}# Install for Kimi CLI under ~/.kimi-code${reset}\n    npx ${pkg.name} --kimi --global --config-dir ~/.kimi-code\n\n    ${dim}# Install for Copilot globally${reset}\n    npx ${pkg.name} --copilot --global\n\n    ${dim}# Install for Copilot locally${reset}\n    npx ${pkg.name} --copilot --local\n\n    ${dim}# Install for Antigravity globally${reset}\n    npx ${pkg.name} --antigravity --global\n\n    ${dim}# Install for Antigravity locally${reset}\n    npx ${pkg.name} --antigravity --local\n\n    ${dim}# Install for Cursor globally${reset}\n    npx ${pkg.name} --cursor --global\n\n    ${dim}# Install for Cursor locally${reset}\n    npx ${pkg.name} --cursor --local\n\n    ${dim}# Install for Windsurf globally${reset}\n    npx ${pkg.name} --windsurf --global\n\n    ${dim}# Install for Windsurf locally${reset}\n    npx ${pkg.name} --windsurf --local\n\n    ${dim}# Install for Augment globally${reset}\n    npx ${pkg.name} --augment --global\n\n    ${dim}# Install for Augment locally${reset}\n    npx ${pkg.name} --augment --local\n\n    ${dim}# Install for Trae globally${reset}\n    npx ${pkg.name} --trae --global\n\n    ${dim}# Install for Trae locally${reset}\n    npx ${pkg.name} --trae --local\n\n    ${dim}# Install for Hermes Agent globally${reset}\n    npx ${pkg.name} --hermes --global\n\n    ${dim}# Install for Hermes Agent locally${reset}\n    npx ${pkg.name} --hermes --local\n\n    ${dim}# Install for Cline globally${reset}\n    npx ${pkg.name} --cline --global\n\n    ${dim}# Install for Cline locally${reset}\n    npx ${pkg.name} --cline --local\n\n    ${dim}# Install for CodeBuddy globally${reset}\n    npx ${pkg.name} --codebuddy --global\n\n    ${dim}# Install for CodeBuddy locally${reset}\n    npx ${pkg.name} --codebuddy --local\n\n    ${dim}# Install for all runtimes globally${reset}\n    npx ${pkg.name} --all --global\n\n    ${dim}# Install to custom config directory${reset}\n    npx ${pkg.name} --kilo --global --config-dir ~/.kilo-work\n\n    ${dim}# Install to current project only${reset}\n    npx ${pkg.name} --claude --local\n\n    ${dim}# Uninstall GSD from Cursor globally${reset}\n    npx ${pkg.name} --cursor --global --uninstall\n\n  ${yellow}Notes:${reset}\n    The --config-dir option is useful when you have multiple configurations.\n    It takes priority over CLAUDE_CONFIG_DIR / OPENCODE_CONFIG_DIR / GEMINI_CONFIG_DIR / KILO_CONFIG_DIR / CODEX_HOME / KIMI_CONFIG_DIR / COPILOT_CONFIG_DIR / COPILOT_HOME / ANTIGRAVITY_CONFIG_DIR / CURSOR_CONFIG_DIR / WINDSURF_CONFIG_DIR / AUGMENT_CONFIG_DIR / TRAE_CONFIG_DIR / QWEN_CONFIG_DIR / HERMES_HOME / CLINE_CONFIG_DIR / CODEBUDDY_CONFIG_DIR environment variables.\n    Kimi CLI defaults to the first existing generic skills root: ${cyan}~/.config/agents/skills${reset}, then ${cyan}~/.agents/skills${reset}; if neither exists, GSD creates ${cyan}~/.config/agents${reset}.\n    Use ${cyan}--config-dir ~/.kimi-code${reset} or ${cyan}KIMI_CONFIG_DIR=~/.kimi-code${reset} for brand-specific Kimi installs.\n`);
+  console.log(`  ${yellow}Usage:${reset} npx ${pkg.name} [options]\n\n  ${yellow}Options:${reset}\n    ${cyan}-g, --global${reset}              Install globally (to config directory)\n    ${cyan}-l, --local${reset}               Install locally (to current directory)\n    ${cyan}--claude${reset}                  Install for Claude Code only\n    ${cyan}--opencode${reset}                Install for OpenCode only\n    ${cyan}--gemini${reset}                  Install for Gemini only\n    ${cyan}--kilo${reset}                    Install for Kilo only\n    ${cyan}--codex${reset}                   Install for Codex only\n    ${cyan}--kimi${reset}                    Install for Kimi CLI only\n    ${cyan}--copilot${reset}                 Install for Copilot only\n    ${cyan}--antigravity${reset}             Install for Antigravity only\n    ${cyan}--cursor${reset}                  Install for Cursor only\n    ${cyan}--windsurf${reset}                Install for Windsurf only\n    ${cyan}--augment${reset}                 Install for Augment only\n    ${cyan}--trae${reset}                    Install for Trae only\n    ${cyan}--qwen${reset}                    Install for Qwen Code only\n    ${cyan}--hermes${reset}                  Install for Hermes Agent only\n    ${cyan}--cline${reset}                   Install for Cline only\n    ${cyan}--codebuddy${reset}              Install for CodeBuddy only\n    ${cyan}--all${reset}                     Install for all runtimes\n    ${cyan}-u, --uninstall${reset}           Uninstall pp-core (remove all pp-core files)\n    ${cyan}-c, --config-dir <path>${reset}   Specify custom config directory\n    ${cyan}-h, --help${reset}                Show this help message\n    ${cyan}--force-statusline${reset}        Replace existing statusline config\n    ${cyan}--portable-hooks${reset}          Emit \$HOME-relative hook paths in settings.json\n                              (for WSL/Docker bind-mount setups; also GSD_PORTABLE_HOOKS=1)\n    ${cyan}--profile=<name>${reset}         Install a named skill profile. Profiles:\n                              core     — ${PROFILES.core.length} main-loop skills incl. phase (~130 desc tokens)\n                              standard — ${PROFILES.standard.length} skills incl. phase, review, config (~700)\n                              full     — all skills (default)\n                              Composable: --profile=core,audit installs union of closures.\n                              Profile is persisted and respected by \`gsd update\`.\n    ${cyan}--minimal${reset}                 Alias for --profile=core (back-compat).\n                              Cuts cold-start overhead from ~12k tokens to ~700.\n                              Alias: --core-only.\n\n  ${yellow}Examples:${reset}\n    ${dim}# Interactive install (prompts for runtime and location)${reset}\n    npx ${pkg.name}\n\n    ${dim}# Install for Claude Code globally${reset}\n    npx ${pkg.name} --claude --global\n\n    ${dim}# Install for Gemini globally${reset}\n    npx ${pkg.name} --gemini --global\n\n    ${dim}# Install for Kilo globally${reset}\n    npx ${pkg.name} --kilo --global\n\n    ${dim}# Install for Codex globally${reset}\n    npx ${pkg.name} --codex --global\n\n    ${dim}# Install for Kimi CLI globally${reset}\n    npx ${pkg.name} --kimi --global\n\n    ${dim}# Install for Kimi CLI under ~/.kimi-code${reset}\n    npx ${pkg.name} --kimi --global --config-dir ~/.kimi-code\n\n    ${dim}# Install for Copilot globally${reset}\n    npx ${pkg.name} --copilot --global\n\n    ${dim}# Install for Copilot locally${reset}\n    npx ${pkg.name} --copilot --local\n\n    ${dim}# Install for Antigravity globally${reset}\n    npx ${pkg.name} --antigravity --global\n\n    ${dim}# Install for Antigravity locally${reset}\n    npx ${pkg.name} --antigravity --local\n\n    ${dim}# Install for Cursor globally${reset}\n    npx ${pkg.name} --cursor --global\n\n    ${dim}# Install for Cursor locally${reset}\n    npx ${pkg.name} --cursor --local\n\n    ${dim}# Install for Windsurf globally${reset}\n    npx ${pkg.name} --windsurf --global\n\n    ${dim}# Install for Windsurf locally${reset}\n    npx ${pkg.name} --windsurf --local\n\n    ${dim}# Install for Augment globally${reset}\n    npx ${pkg.name} --augment --global\n\n    ${dim}# Install for Augment locally${reset}\n    npx ${pkg.name} --augment --local\n\n    ${dim}# Install for Trae globally${reset}\n    npx ${pkg.name} --trae --global\n\n    ${dim}# Install for Trae locally${reset}\n    npx ${pkg.name} --trae --local\n\n    ${dim}# Install for Hermes Agent globally${reset}\n    npx ${pkg.name} --hermes --global\n\n    ${dim}# Install for Hermes Agent locally${reset}\n    npx ${pkg.name} --hermes --local\n\n    ${dim}# Install for Cline globally${reset}\n    npx ${pkg.name} --cline --global\n\n    ${dim}# Install for Cline locally${reset}\n    npx ${pkg.name} --cline --local\n\n    ${dim}# Install for CodeBuddy globally${reset}\n    npx ${pkg.name} --codebuddy --global\n\n    ${dim}# Install for CodeBuddy locally${reset}\n    npx ${pkg.name} --codebuddy --local\n\n    ${dim}# Install for all runtimes globally${reset}\n    npx ${pkg.name} --all --global\n\n    ${dim}# Install to custom config directory${reset}\n    npx ${pkg.name} --kilo --global --config-dir ~/.kilo-work\n\n    ${dim}# Install to current project only${reset}\n    npx ${pkg.name} --claude --local\n\n    ${dim}# Uninstall pp-core from Cursor globally${reset}\n    npx ${pkg.name} --cursor --global --uninstall\n\n  ${yellow}Notes:${reset}\n    The --config-dir option is useful when you have multiple configurations.\n    It takes priority over CLAUDE_CONFIG_DIR / OPENCODE_CONFIG_DIR / GEMINI_CONFIG_DIR / KILO_CONFIG_DIR / CODEX_HOME / KIMI_CONFIG_DIR / COPILOT_CONFIG_DIR / COPILOT_HOME / ANTIGRAVITY_CONFIG_DIR / CURSOR_CONFIG_DIR / WINDSURF_CONFIG_DIR / AUGMENT_CONFIG_DIR / TRAE_CONFIG_DIR / QWEN_CONFIG_DIR / HERMES_HOME / CLINE_CONFIG_DIR / CODEBUDDY_CONFIG_DIR environment variables.\n    Kimi CLI defaults to the first existing generic skills root: ${cyan}~/.config/agents/skills${reset}, then ${cyan}~/.agents/skills${reset}; if neither exists, pp-core creates ${cyan}~/.config/agents${reset}.\n    Use ${cyan}--config-dir ~/.kimi-code${reset} or ${cyan}KIMI_CONFIG_DIR=~/.kimi-code${reset} for brand-specific Kimi installs.\n`);
   process.exit(0);
 }
 
@@ -6554,10 +6554,10 @@ function writeHermesCategoryDescription(categoryDir) {
     '---',
     'name: gsd',
     `version: ${pkg.version}`,
-    'description: GSD Core — Git. Ship. Done. Disciplined planning, execution, and shipping workflows. Use any gsd-* skill in this category to drive a project through new-project → discuss-phase → plan-phase → execute-phase → ship.',
+    'description: pp-core — The Pareto delivery framework. Disciplined planning, execution, and shipping workflows. Use any pp-* skill in this category to drive a project through new-project → discuss-phase → plan-phase → execute-phase → ship.',
     '---',
     '',
-    '# GSD Core',
+    '# pp-core',
     '',
     'GSD is a structured development workflow. Skills in this category cover',
     'project initialization, phase planning, execution, code review, and shipping.',
@@ -7886,7 +7886,7 @@ const GSD_UNINSTALL_HOOKS = [
 ];
 
 /**
- * Uninstall GSD from the specified directory for a specific runtime
+ * Uninstall pp-core from the specified directory for a specific runtime
  * Removes only GSD-specific files/directories, preserves user content
  * @param {boolean} isGlobal - Whether to uninstall from global or local
  * @param {string} runtime - Target runtime ('claude', 'opencode', 'gemini', 'codex', 'copilot')
@@ -9513,7 +9513,7 @@ function install(isGlobal, runtime = 'claude', options = {}) {
   // `@$HOME/...` is treated as a literal path relative to the config dir, producing
   // `command/$HOME/...` (file not found). Use the absolute path for OpenCode so
   // @-references resolve correctly (#2376 Windows, #2831 macOS/Linux).
-  // gsd update marker re-application (ADR-0010 Deviation 2):
+  // pp update marker re-application (ADR-0010 Deviation 2):
   // Resolve which profile to use for this runtime's install:
   //   1. --minimal / --core-only → back-compat alias for the core profile
   //   2. Explicit --profile=<name> → use it (overrides any marker)
@@ -10201,7 +10201,7 @@ function install(isGlobal, runtime = 'claude', options = {}) {
         }
       }
     }
-    console.log(`  ${dim}↳${reset} Skipping agents (minimal install — run \`gsd update\` without \`--minimal\` to add full surface)`);
+    console.log(`  ${dim}↳${reset} Skipping agents (minimal install — run \`pp update\` without \`--minimal\` to add full surface)`);
   } else if (fs.existsSync(agentsSrc)) {
     fs.mkdirSync(agentsDest, { recursive: true });
 

package/commands/pp-autonomous.md

@@ -37,12 +37,12 @@ Optional flags:
 - `--to N` — stop after phase N completes (halt instead of advancing to next phase).
 - `--only N` — execute only phase N (single-phase mode).
 - `--interactive` — run discuss inline with questions (not auto-answered), then dispatch plan→execute as background agents. Keeps the main context lean while preserving user input on decisions.
-- `--converge` — run each phase's planning step through `gsd-plan-review-convergence` instead of plain `gsd-plan-phase`. Requires `workflow.plan_review_convergence=true`.
+- `--converge` — run each phase's planning step through `pp-plan-review-convergence` instead of plain `pp-plan-phase`. Requires `workflow.plan_review_convergence=true`.
 - `--cross-ai` — compatibility alias for `--converge`.
 
-When `--converge` or `--cross-ai` is set, reviewer selector flags supported by `gsd-plan-review-convergence` may be passed through: `--codex`, `--gemini`, `--claude`, `--opencode`, `--ollama`, `--lm-studio`, `--llama-cpp`, `--all`, and `--max-cycles N`.
+When `--converge` or `--cross-ai` is set, reviewer selector flags supported by `pp-plan-review-convergence` may be passed through: `--codex`, `--gemini`, `--claude`, `--opencode`, `--ollama`, `--lm-studio`, `--llama-cpp`, `--all`, and `--max-cycles N`.
 
-Project context, phase list, and state are resolved inside the workflow using init commands (`gsd-tools query init.milestone-op`, `gsd-tools query roadmap.analyze`). No upfront context loading needed.
+Project context, phase list, and state are resolved inside the workflow using init commands (`pp_run query init.milestone-op`, `pp_run query roadmap.analyze`). No upfront context loading needed.
 </context>
 
 <process>

package/commands/pp-capture.md

@@ -13,7 +13,7 @@ allowed-tools:
 ---
 
 <objective>
-Capture ideas, tasks, notes, and seeds to their appropriate destination in the GSD system.
+Capture ideas, tasks, notes, and seeds to their appropriate destination in the pp-core system.
 
 Mode routing:
 - **default** (no flag): Capture as a structured todo for later work → add-todo workflow

package/commands/pp-code-review.md

@@ -41,7 +41,7 @@ Optional flags parsed from $ARGUMENTS:
 - `--depth=VALUE` — Depth override (quick|standard|deep). If provided, overrides workflow.code_review_depth config.
 - `--files=file1,file2,...` — Explicit file list override. Has highest precedence for file scoping per D-08. When provided, workflow skips SUMMARY.md extraction and git diff fallback entirely.
 
-Context files (CLAUDE.md, SUMMARY.md, phase state) are resolved inside the workflow via `gsd-tools query init.phase-op` and delegated to agent via `<files_to_read>` blocks.
+Context files (CLAUDE.md, SUMMARY.md, phase state) are resolved inside the workflow via `pp_run query init.phase-op` and delegated to agent via `<files_to_read>` blocks.
 </context>
 
 <process>

package/commands/pp-config.md

@@ -1,6 +1,6 @@
 ---
 name: pp:config
-description: Configure GSD settings — workflow toggles, advanced knobs, integrations, and model profile
+description: Configure pp-core settings — workflow toggles, advanced knobs, integrations, and model profile
 argument-hint: "[--advanced | --integrations | --profile <name>]"
 allowed-tools:
   - Read
@@ -11,7 +11,7 @@ requires: [code-review, review, settings]
 ---
 
 <objective>
-Configure GSD settings interactively with a single consolidated command.
+Configure pp-core settings interactively with a single consolidated command.
 
 Mode routing:
 - **default** (no flag): Common-case toggles (model, research, plan_check, verifier, branching) → settings workflow
@@ -27,7 +27,7 @@ Mode routing:
 | (none) | Interactive 5-question common-case config prompt | settings |
 | --advanced | Power-user knobs: planning, execution, discussion, cross-AI, git, runtime | settings-advanced |
 | --integrations | API keys (Brave/Firecrawl/Exa), review CLI routing, agent skills | settings-integrations |
-| --profile &lt;name&gt; | Switch model profile without interactive prompt | pp-tools query config-set-model-profile |
+| --profile &lt;name&gt; | Switch model profile without interactive prompt | pp_run query config-set-model-profile |
 
 </routing>
 
@@ -45,7 +45,7 @@ Parse the first token of $ARGUMENTS:
 - If it is `--integrations`: strip the flag, execute settings-integrations workflow
 - If it starts with `--profile`: extract the profile name (remainder after `--profile`), then:
   1. Verify `pp-tools` is on PATH via `command -v pp-tools`; if absent, emit the install hint `Install PP via 'npm i -g @pareto4/pp-core'` and stop.
-  2. Run: `pp-tools query config-set-model-profile <profile-name> --raw` and display the output verbatim.
+  2. Run: `pp_run query config-set-model-profile <profile-name> --raw` and display the output verbatim.
 - Otherwise: execute settings workflow (no argument needed)
 </context>
 

package/commands/pp-debug.md

@@ -22,7 +22,7 @@ Debug issues using scientific method with subagent isolation.
 </objective>
 
 <available_agent_types>
-Valid GSD subagent types (use exact names — do not fall back to 'general-purpose'):
+Valid pp-core subagent types (use exact names — do not fall back to 'general-purpose'):
 - pp-debug-session-manager — manages debug checkpoint/continuation loop in isolated context
 - pp-debugger — investigates bugs using scientific method
 </available_agent_types>

package/commands/pp-docs-update.md

@@ -20,7 +20,7 @@ Flag handling rule:
 - The optional flags documented below are available behaviors, not implied active behaviors
 - A flag is active only when its literal token appears in `$ARGUMENTS`
 - If a documented flag is absent from `$ARGUMENTS`, treat it as inactive
-- `--force`: skip preservation prompts, regenerate all docs regardless of existing content or GSD markers
+- `--force`: skip preservation prompts, regenerate all docs regardless of existing content or pp-core markers
 - `--verify-only`: check existing docs for accuracy against codebase, no generation (full verification requires Phase 4 verifier)
 - If `--force` and `--verify-only` both appear in `$ARGUMENTS`, `--force` takes precedence
 </objective>
@@ -33,7 +33,7 @@ Flag handling rule:
 Arguments: $ARGUMENTS
 
 **Available optional flags (documentation only — not automatically active):**
-- `--force` — Regenerate all docs. Overwrites hand-written and GSD docs alike. No preservation prompts.
+- `--force` — Regenerate all docs. Overwrites hand-written and pp-core docs alike. No preservation prompts.
 - `--verify-only` — Check existing docs for accuracy against the codebase. No files are written. Reports VERIFY marker count. Full codebase fact-checking requires the pp-doc-verifier agent (Phase 4).
 
 **Active flags must be derived from `$ARGUMENTS`:**

package/commands/pp-execute-phase.md

@@ -56,7 +56,7 @@ Phase: $ARGUMENTS
 - If none of these tokens appear, run the standard full-phase execution flow with no flag-specific filtering
 - Do not infer that a flag is active just because it is documented in this prompt
 
-Context files are resolved inside the workflow via `gsd-tools query init.execute-phase` and per-subagent `<files_to_read>` blocks.
+Context files are resolved inside the workflow via `pp_run query init.execute-phase` and per-subagent `<files_to_read>` blocks.
 </context>
 
 <process>

package/commands/pp-explore.md

@@ -12,7 +12,7 @@ allowed-tools:
 ---
 <objective>
 Open-ended Socratic ideation session. Guides the developer through exploring an idea via
-probing questions, optionally spawns research, then routes outputs to the appropriate GSD
+probing questions, optionally spawns research, then routes outputs to the appropriate pp-core
 artifacts (notes, todos, seeds, research questions, requirements, or new phases).
 
 Accepts an optional topic argument: `/pp:explore authentication strategy`

package/commands/pp-forensics.md

@@ -1,7 +1,7 @@
 ---
 type: prompt
 name: pp:forensics
-description: Post-mortem investigation for failed GSD workflows — diagnoses what went wrong.
+description: Post-mortem investigation for failed pp-core workflows — diagnoses what went wrong.
 argument-hint: "[problem description]"
 allowed-tools:
   - Read
@@ -13,7 +13,7 @@ requires: [phase, progress, update]
 ---
 
 <objective>
-Investigate what went wrong during a GSD workflow execution. Analyzes git history, `.planning/` artifacts, and file system state to detect anomalies and generate a structured diagnostic report.
+Investigate what went wrong during a pp-core workflow execution. Analyzes git history, `.planning/` artifacts, and file system state to detect anomalies and generate a structured diagnostic report.
 
 Purpose: Diagnose failed or stuck workflows so the user can understand root cause and take corrective action.
 Output: Forensic report saved to `.planning/forensics/`, presented inline, with optional issue creation.

package/commands/pp-graphify.md

@@ -10,14 +10,14 @@ requires: [config, fast, phase, update]
 
 **STOP -- DO NOT READ THIS FILE. You are already reading it. This prompt was injected into your context by Claude Code's command system. Using the Read tool on this file wastes tokens. Begin executing Step 0 immediately.**
 
-**CJS-only (graphify):** `graphify` subcommands are not registered on `pp-tools query (graphify) …` where `<runtime-home>` is your runtime's config directory (e.g. `~/.claude`, `~/.hermes`, `~/.cursor`). See `docs/CLI-TOOLS.md` for details. Other tooling may still use `pp-tools query` where a handler exists.
+**CJS-only (graphify):** `graphify` subcommands are not registered on `pp_run query (graphify) …` where `<runtime-home>` is your runtime's config directory (e.g. `~/.claude`, `~/.hermes`, `~/.cursor`). See `docs/CLI-TOOLS.md` for details. Other tooling may still use `pp_run query` where a handler exists.
 
 ## Step 0 -- Banner
 
 **Before ANY tool calls**, display this banner:
 
 ```
-GSD > GRAPHIFY
+pp-core > GRAPHIFY
 ```
 
 Then proceed to Step 1.
@@ -26,7 +26,7 @@ Then proceed to Step 1.
 
 Check if graphify is enabled by reading `.planning/config.json` directly using the Read tool.
 
-**DO NOT use the pp-tools query config-get command** -- it hard-exits on missing keys.
+**DO NOT use the pp_run query config-get command** -- it hard-exits on missing keys.
 
 1. Read `.planning/config.json` using the Read tool
 2. If the file does not exist: display the disabled message below and **STOP**
@@ -37,7 +37,7 @@ Check if graphify is enabled by reading `.planning/config.json` directly using t
 **Disabled message:**
 
 ```
-GSD > GRAPHIFY
+pp-core > GRAPHIFY
 
 Knowledge graph is disabled. To activate:
 
@@ -63,7 +63,7 @@ Parse `$ARGUMENTS` to determine the operation mode:
 **Usage message** (shown when no argument or unrecognized argument):
 
 ```
-GSD > GRAPHIFY
+pp-core > GRAPHIFY
 
 Usage: /pp:graphify <mode>
 
@@ -154,7 +154,7 @@ Parse the JSON output:
 Display:
 
 ```text
-GSD > Building knowledge graph...
+pp-core > Building knowledge graph...
 ```
 
 Run the build, copy artifacts, write the diff snapshot, and report the summary in a single foreground Bash call so the whole pipeline survives to completion. Use a `timeout` of `600000` ms (10 minutes), which covers the `graphify.build_timeout` ceiling (default 300 s) with margin:
@@ -184,7 +184,7 @@ If the chain succeeds:
 
 ## MVP-Mode Node Rendering
 
-**MVP-mode rendering.** When a phase has `**Mode:** mvp` in ROADMAP.md (resolved via `pp-tools query roadmap.get-phase --pick mode`), render its graph node with two distinct visual signals:
+**MVP-mode rendering.** When a phase has `**Mode:** mvp` in ROADMAP.md (resolved via `pp_run query roadmap.get-phase --pick mode`), render its graph node with two distinct visual signals:
 
 1. **Distinct fill color.** Use `#22c55e` (green) for MVP-mode phase nodes. Standard phases keep the default fill color. Two-channel signaling (color + label) handles color-blind and grayscale renders.
 2. **`MVP` label suffix.** Append ` (MVP)` to the node's label text. Example: a phase originally labeled `Phase 1: User Auth` renders as `Phase 1: User Auth (MVP)`.
@@ -201,4 +201,4 @@ When the phase mode is null/absent, render with the standard color and label —
 2. DO NOT pass `run_in_background: true` for the build chain -- the operation is fast and must complete in the foreground.
 3. DO NOT modify graph files directly -- always go through `graphify update .` and the snapshot CLI.
 4. DO NOT skip the config gate check.
-5. DO NOT use `pp-tools query config-get` for the config gate -- it exits on missing keys.
+5. DO NOT use `pp_run query config-get` for the config gate -- it exits on missing keys.

package/commands/pp-health.md

@@ -12,7 +12,7 @@ requires: [thread]
 <objective>
 Validate `.planning/` directory integrity and report actionable issues. Checks for missing files, invalid configurations, inconsistent state, and orphaned plans.
 
-`--context` runs an orthogonal check: the running session's context utilization. The workflow asks for the model's tokensUsed + contextWindow, calls `gsd-tools query validate.context`, and renders one of three states:
+`--context` runs an orthogonal check: the running session's context utilization. The workflow asks for the model's tokensUsed + contextWindow, calls `pp_run query validate.context`, and renders one of three states:
 
 | Utilization | State    | Action                                                |
 |-------------|----------|-------------------------------------------------------|

package/commands/pp-help.md

@@ -1,12 +1,12 @@
 ---
 name: pp:help
-description: Show available GSD commands and usage guide
+description: Show available pp-core commands and usage guide
 argument-hint: "[--brief | --full | <topic> | --brief <topic>]"
 allowed-tools:
   - Read
 ---
 <objective>
-Display GSD help at the tier the user asked for: brief (one-line refresher), default (one-page tour), full (complete reference), a single topic section, or a compact scoped lookup of one topic (`--brief <topic>`: signature + one-line summary).
+Display pp-core help at the tier the user asked for: brief (one-line refresher), default (one-page tour), full (complete reference), a single topic section, or a compact scoped lookup of one topic (`--brief <topic>`: signature + one-line summary).
 
 Output ONLY the reference content of the chosen tier. Do NOT add:
 - Project-specific analysis

package/commands/pp-import.md

@@ -14,10 +14,10 @@ allowed-tools:
 ---
 
 <objective>
-Import external plan files into the GSD planning system with conflict detection against PROJECT.md decisions.
+Import external plan files into the pp-core planning system with conflict detection against PROJECT.md decisions.
 
-- **--from**: Import an external plan file, detect conflicts, write as GSD PLAN.md, validate via pp-plan-checker.
-- **--from-gsd2**: Reverse-migrate a GSD-2 project (`.gsd/` directory) back to GSD v1 (`.planning/`) format. Runs `gsd-tools.cjs from-gsd2`. Pass `--path <dir>` to migrate a project at a different path.
+- **--from**: Import an external plan file, detect conflicts, write as pp-core PLAN.md, validate via pp-plan-checker.
+- **--from-gsd2**: Reverse-migrate a GSD-2 project (`.gsd/` directory) back to GSD v1 (`.planning/`) format. Runs `pp-tools.cjs from-gsd2`. Pass `--path <dir>` to migrate a project at a different path.
 </objective>
 
 <execution_context>
@@ -36,7 +36,7 @@ If `--from-gsd2` is in $ARGUMENTS:
 Run the reverse-migration (append `--path <dir>` if provided):
 ```bash
 _PP_SHIM_NAME="pp-tools.cjs"; _PP_RUNTIME_ROOT="${RUNTIME_DIR:-$(git rev-parse --show-toplevel 2>/dev/null || pwd)}"; PP_TOOLS="${_PP_RUNTIME_ROOT}/pp-core/bin/${_PP_SHIM_NAME}"; if [ -f "$PP_TOOLS" ]; then pp_run() { node "$PP_TOOLS" "$@"; }; elif [ -f "${_PP_RUNTIME_ROOT}/.claude/pp-core/bin/${_PP_SHIM_NAME}" ]; then PP_TOOLS="${_PP_RUNTIME_ROOT}/.claude/pp-core/bin/${_PP_SHIM_NAME}"; pp_run() { node "$PP_TOOLS" "$@"; }; elif command -v pp-tools >/dev/null 2>&1; then PP_TOOLS="$(command -v pp-tools)"; pp_run() { "$PP_TOOLS" "$@"; }; elif [ -f "$HOME/.claude/pp-core/bin/${_PP_SHIM_NAME}" ]; then PP_TOOLS="$HOME/.claude/pp-core/bin/${_PP_SHIM_NAME}"; pp_run() { node "$PP_TOOLS" "$@"; }; elif [ -f "${HERMES_HOME:-$HOME/.hermes}/pp-core/bin/${_PP_SHIM_NAME}" ]; then PP_TOOLS="${HERMES_HOME:-$HOME/.hermes}/pp-core/bin/${_PP_SHIM_NAME}"; pp_run() { node "$PP_TOOLS" "$@"; }; elif [ -f "${CURSOR_CONFIG_DIR:-$HOME/.cursor}/pp-core/bin/${_PP_SHIM_NAME}" ]; then PP_TOOLS="${CURSOR_CONFIG_DIR:-$HOME/.cursor}/pp-core/bin/${_PP_SHIM_NAME}"; pp_run() { node "$PP_TOOLS" "$@"; }; elif [ -f "${CODEX_HOME:-$HOME/.codex}/pp-core/bin/${_PP_SHIM_NAME}" ]; then PP_TOOLS="${CODEX_HOME:-$HOME/.codex}/pp-core/bin/${_PP_SHIM_NAME}"; pp_run() { node "$PP_TOOLS" "$@"; }; elif [ -f "${GEMINI_CONFIG_DIR:-$HOME/.gemini}/pp-core/bin/${_PP_SHIM_NAME}" ]; then PP_TOOLS="${GEMINI_CONFIG_DIR:-$HOME/.gemini}/pp-core/bin/${_PP_SHIM_NAME}"; pp_run() { node "$PP_TOOLS" "$@"; }; elif [ -f "${COPILOT_CONFIG_DIR:-$HOME/.copilot}/pp-core/bin/${_PP_SHIM_NAME}" ]; then PP_TOOLS="${COPILOT_CONFIG_DIR:-$HOME/.copilot}/pp-core/bin/${_PP_SHIM_NAME}"; pp_run() { node "$PP_TOOLS" "$@"; }; elif [ -f "${WINDSURF_CONFIG_DIR:-$HOME/.codeium/windsurf}/pp-core/bin/${_PP_SHIM_NAME}" ]; then PP_TOOLS="${WINDSURF_CONFIG_DIR:-$HOME/.codeium/windsurf}/pp-core/bin/${_PP_SHIM_NAME}"; pp_run() { node "$PP_TOOLS" "$@"; }; elif [ -f "${AUGMENT_CONFIG_DIR:-$HOME/.augment}/pp-core/bin/${_PP_SHIM_NAME}" ]; then PP_TOOLS="${AUGMENT_CONFIG_DIR:-$HOME/.augment}/pp-core/bin/${_PP_SHIM_NAME}"; pp_run() { node "$PP_TOOLS" "$@"; }; elif [ -f "${TRAE_CONFIG_DIR:-$HOME/.trae}/pp-core/bin/${_PP_SHIM_NAME}" ]; then PP_TOOLS="${TRAE_CONFIG_DIR:-$HOME/.trae}/pp-core/bin/${_PP_SHIM_NAME}"; pp_run() { node "$PP_TOOLS" "$@"; }; elif [ -f "${QWEN_CONFIG_DIR:-$HOME/.qwen}/pp-core/bin/${_PP_SHIM_NAME}" ]; then PP_TOOLS="${QWEN_CONFIG_DIR:-$HOME/.qwen}/pp-core/bin/${_PP_SHIM_NAME}"; pp_run() { node "$PP_TOOLS" "$@"; }; elif [ -f "${CODEBUDDY_CONFIG_DIR:-$HOME/.codebuddy}/pp-core/bin/${_PP_SHIM_NAME}" ]; then PP_TOOLS="${CODEBUDDY_CONFIG_DIR:-$HOME/.codebuddy}/pp-core/bin/${_PP_SHIM_NAME}"; pp_run() { node "$PP_TOOLS" "$@"; }; elif [ -f "${CLINE_CONFIG_DIR:-$HOME/.cline}/pp-core/bin/${_PP_SHIM_NAME}" ]; then PP_TOOLS="${CLINE_CONFIG_DIR:-$HOME/.cline}/pp-core/bin/${_PP_SHIM_NAME}"; pp_run() { node "$PP_TOOLS" "$@"; }; elif [ -f "${GROK_AGENTS_HOME:-$HOME/.agents}/pp-core/bin/${_PP_SHIM_NAME}" ]; then PP_TOOLS="${GROK_AGENTS_HOME:-$HOME/.agents}/pp-core/bin/${_PP_SHIM_NAME}"; pp_run() { node "$PP_TOOLS" "$@"; }; elif [ -f "${ANTIGRAVITY_CONFIG_DIR:-$HOME/.gemini/antigravity}/pp-core/bin/${_PP_SHIM_NAME}" ]; then PP_TOOLS="${ANTIGRAVITY_CONFIG_DIR:-$HOME/.gemini/antigravity}/pp-core/bin/${_PP_SHIM_NAME}"; pp_run() { node "$PP_TOOLS" "$@"; }; elif [ -f "${OPENCODE_CONFIG_DIR:-${XDG_CONFIG_HOME:-$HOME/.config}/opencode}/pp-core/bin/${_PP_SHIM_NAME}" ]; then PP_TOOLS="${OPENCODE_CONFIG_DIR:-${XDG_CONFIG_HOME:-$HOME/.config}/opencode}/pp-core/bin/${_PP_SHIM_NAME}"; pp_run() { node "$PP_TOOLS" "$@"; }; elif [ -f "${KILO_CONFIG_DIR:-${XDG_CONFIG_HOME:-$HOME/.config}/kilo}/pp-core/bin/${_PP_SHIM_NAME}" ]; then PP_TOOLS="${KILO_CONFIG_DIR:-${XDG_CONFIG_HOME:-$HOME/.config}/kilo}/pp-core/bin/${_PP_SHIM_NAME}"; pp_run() { node "$PP_TOOLS" "$@"; }; else echo "ERROR: pp-tools.cjs not found at $PP_TOOLS and pp-tools is not on PATH. Run: npx -y @pareto4/pp-core@latest --claude --local" >&2; exit 1; fi
-gsd_run from-gsd2
+pp_run from-gsd2
 ```
 Present the migration result to the user.
 Stop here (do not run the standard import workflow).

package/commands/pp-manager.md

@@ -19,7 +19,7 @@ Single-terminal command center for managing a milestone. Shows a dashboard of al
 Designed for power users who want to parallelize work across phases from one terminal: discuss a phase while another plans or executes in the background.
 
 **Creates/Updates:**
-- No files created directly — dispatches to existing GSD commands via Skill() and background Task agents.
+- No files created directly — dispatches to existing pp-core commands via Skill() and background Task agents.
 - Reads `.planning/STATE.md`, `.planning/ROADMAP.md`, phase directories for status.
 
 **After:** User exits when done managing, or all phases complete and milestone lifecycle is suggested.
@@ -33,7 +33,7 @@ Designed for power users who want to parallelize work across phases from one ter
 <context>
 No arguments required. Requires an active milestone with ROADMAP.md and STATE.md.
 
-Project context, phase list, dependencies, and recommendations are resolved inside the workflow using `gsd-tools query init.manager`. No upfront context loading needed.
+Project context, phase list, dependencies, and recommendations are resolved inside the workflow using `pp_run query init.manager`. No upfront context loading needed.
 </context>
 
 <process>

package/commands/pp-mempalace-capture.md

@@ -15,7 +15,7 @@ requires: [config]
 **Before ANY tool calls**, display this banner:
 
 ```
-GSD > MEMPALACE CAPTURE
+pp-core > MEMPALACE CAPTURE
 ```
 
 Then proceed to Step 1.
@@ -31,7 +31,7 @@ Check whether the MemPalace capability is enabled by reading `.planning/config.j
 **Disabled message:**
 
 ```
-GSD > MEMPALACE CAPTURE
+pp-core > MEMPALACE CAPTURE
 
 MemPalace capture is disabled (mempalace.enabled / mempalace.capture_artifacts).
 Nothing was filed; the loop proceeds normally.

package/commands/pp-mempalace-recall.md

@@ -16,7 +16,7 @@ requires: [config]
 **Before ANY tool calls**, display this banner:
 
 ```
-GSD > MEMPALACE RECALL
+pp-core > MEMPALACE RECALL
 ```
 
 Then proceed to Step 1.
@@ -25,7 +25,7 @@ Then proceed to Step 1.
 
 Check whether the MemPalace capability is enabled by reading `.planning/config.json` directly with the Read tool.
 
-**DO NOT use `gsd-tools config get-value`** -- it hard-exits on missing keys.
+**DO NOT use `pp-tools config get-value`** -- it hard-exits on missing keys.
 
 1. Read `.planning/config.json` with the Read tool.
 2. If the file does not exist: write the "unavailable" stub (Step 4) and **STOP**.
@@ -34,7 +34,7 @@ Check whether the MemPalace capability is enabled by reading `.planning/config.j
 **Disabled message:**
 
 ```
-GSD > MEMPALACE RECALL
+pp-core > MEMPALACE RECALL
 
 MemPalace memory is disabled. To activate:
 
@@ -62,7 +62,7 @@ All calls in this step are side-effect-free. On any error or timeout, stop retri
 2. **Targeted search:**
    - Interactive: `mempalace_search(query=<topic>, wing=<wing>)`.
    - Headless: `mempalace search "<topic>" --wing <wing>`.
-3. **Knowledge-graph facts** (when `config.mempalace.mirror_kg` is true): `mempalace_kg_query` / `mempalace_kg_timeline` for decisions relevant to the topic and their validity windows. Only `augment` is currently wired, so the palace KG *supplements* GSD's native `.planning/graphs/` — do not treat it as the sole source. (`kg_backend`/`replace` are forward-declared and behave as `augment` today.)
+3. **Knowledge-graph facts** (when `config.mempalace.mirror_kg` is true): `mempalace_kg_query` / `mempalace_kg_timeline` for decisions relevant to the topic and their validity windows. Only `augment` is currently wired, so the palace KG *supplements* pp-core's native `.planning/graphs/` — do not treat it as the sole source. (`kg_backend`/`replace` are forward-declared and behave as `augment` today.)
 4. **Dedup** the returned drawers/facts; keep the top results.
 
 ## Step 4 -- Write MEMORY-RECALL.md

package/commands/pp-mvp-phase.md

@@ -18,7 +18,7 @@ Guide the user through MVP-mode planning for a phase. The command:
 1. Prompts for an "As a / I want to / So that" user story (three structured questions)
 2. Runs SPIDR splitting check — if the story is too large, walks through Spike/Paths/Interfaces/Data/Rules and offers to split into multiple phases
 3. Writes `**Mode:** mvp` and the reformatted `**Goal:**` to the phase's ROADMAP.md section
-4. Delegates to `/gsd plan-phase <N>` which auto-detects MVP mode via the roadmap field
+4. Delegates to `/pp:plan-phase <N>` which auto-detects MVP mode via the roadmap field
 
 Phase 1 of the vertical-mvp-slice PRD shipped the planner-side machinery; this command is the user entry point for it.
 </objective>
@@ -36,7 +36,7 @@ Phase 1 of the vertical-mvp-slice PRD shipped the planner-side machinery; this c
 <context>
 Phase number: $ARGUMENTS (required — integer or decimal like `2.1`)
 
-The phase must already exist in ROADMAP.md (created via `/gsd new-project`, `/gsd add-phase`, or `/gsd insert-phase`). This command does not create new phases — it converts an existing phase to MVP mode.
+The phase must already exist in ROADMAP.md (created via `/pp:new-project`, `/pp:phase`, or `/pp:phase`). This command does not create new phases — it converts an existing phase to MVP mode.
 </context>
 
 <process>

package/commands/pp-ns-manage.md

@@ -14,23 +14,23 @@ Route to the appropriate management skill based on the user's intent.
 
 | User wants | Invoke |
 |---|---|
-| Configure GSD settings (basic / advanced / integrations / profile) | pp-config |
+| Configure pp-core settings (basic / advanced / integrations / profile) | pp-config |
 | Manage workspaces (create / list / remove) | pp-workspace |
 | Manage parallel workstreams | pp-workstreams |
 | Continue work in a fresh context thread | pp-thread |
 | Pause current work | pp-pause-work |
 | Resume paused work | pp-resume-work |
-| Update the GSD installation | pp-update |
+| Update the pp-core installation | pp-update |
 | Ship completed work | pp-ship |
 | Process inbox items | pp-inbox |
 | Create a clean PR branch | pp-pr-branch |
-| Undo the last GSD action | pp-undo |
+| Undo the last pp-core action | pp-undo |
 | Archive accumulated phase directories | pp-cleanup |
 | Diagnose planning directory health | pp-health |
 | Open the interactive command center | pp-manager |
 | Configure workflow toggles and model profile | pp-settings |
 | Show project statistics | pp-stats |
 | Toggle which skills are surfaced | pp-surface |
-| Show the GSD command guide | pp-help |
+| Show the pp-core command guide | pp-help |
 
 Invoke the matched skill directly using the Skill tool.

package/commands/pp-ns-workflow.md

@@ -30,6 +30,6 @@ absorbs the former next/do commands.
 | Run all remaining phases autonomously | pp-autonomous |
 | Execute a trivial task inline | pp-fast |
 | Plan a phase as a vertical MVP slice | pp-mvp-phase |
-| Execute a quick task with GSD guarantees | pp-quick |
+| Execute a quick task with pp-core guarantees | pp-quick |
 
 Invoke the matched skill directly using the Skill tool.

package/commands/pp-plan-review-convergence.md

@@ -15,14 +15,14 @@ requires: [phase, review]
 ---
 
 <objective>
-Cross-AI plan convergence loop — an outer revision gate around gsd-review and pp-planner.
+Cross-AI plan convergence loop — an outer revision gate around pp-review and pp-planner.
 Repeatedly: review plans with external AI CLIs → if HIGH or actionable non-HIGH concerns remain → replan with --reviews feedback → re-review. Stops when no unresolved HIGH concerns or actionable MEDIUM/LOW findings remain outside PLAN.md, or when max cycles is reached.
 
-**Flow:** Skill("gsd-plan-phase") → Agent→Skill("gsd-review") → check unresolved HIGH + actionable non-HIGH → Skill("gsd-plan-phase --reviews") → Agent→Skill("gsd-review") → ... → Converge or escalate
+**Flow:** Skill("pp-plan-phase") → Agent→Skill("pp-review") → check unresolved HIGH + actionable non-HIGH → Skill("pp-plan-phase --reviews") → Agent→Skill("pp-review") → ... → Converge or escalate
 
-Replaces gsd-plan-phase's internal pp-plan-checker with external AI reviewers (codex, gemini, etc.). Plan-phase runs **inline** (bare Skill at depth 0) so it can spawn pp-planner/pp-plan-checker at depth 1. Review runs inside an isolated Agent (gsd-review is a Bash leaf — no sub-agents needed). Orchestrator only does loop control.
+Replaces pp-plan-phase's internal pp-plan-checker with external AI reviewers (codex, gemini, etc.). Plan-phase runs **inline** (bare Skill at depth 0) so it can spawn pp-planner/pp-plan-checker at depth 1. Review runs inside an isolated Agent (pp-review is a Bash leaf — no sub-agents needed). Orchestrator only does loop control.
 
-**Orchestrator role:** Parse arguments, validate phase, run plan-phase inline (Skill at depth 0), spawn an Agent for gsd-review, check unresolved HIGH and actionable non-HIGH counts, stall detection, escalation gate.
+**Orchestrator role:** Parse arguments, validate phase, run plan-phase inline (Skill at depth 0), spawn an Agent for pp-review, check unresolved HIGH and actionable non-HIGH counts, stall detection, escalation gate.
 </objective>
 
 <execution_context>
@@ -51,7 +51,7 @@ Phase number: extracted from $ARGUMENTS (required)
 - `--max-cycles N` — Maximum replan→review cycles (default: 3)
 
 **Feature gate:** This command requires `workflow.plan_review_convergence=true`. Enable with:
-`gsd config-set workflow.plan_review_convergence true`
+`pp config-set workflow.plan_review_convergence true`
 </context>
 
 <process>

package/commands/pp-pr-branch.md

@@ -11,7 +11,7 @@ requires: [review]
 
 <objective>
 Create a clean branch suitable for pull requests by filtering out .planning/ commits
-from the current branch. Reviewers see only code changes, not GSD planning artifacts.
+from the current branch. Reviewers see only code changes, not pp-core planning artifacts.
 
 This solves the problem of PR diffs being cluttered with PLAN.md, SUMMARY.md, STATE.md
 changes that are irrelevant to code review.

package/commands/pp-profile-user.md

@@ -13,7 +13,7 @@ allowed-tools:
 ---
 
 <objective>
-Generate a developer behavioral profile from session analysis (or questionnaire) and produce artifacts (USER-PROFILE.md, `gsd-dev-preferences` skill config, CLAUDE.md section) that personalize Claude's responses.
+Generate a developer behavioral profile from session analysis (or questionnaire) and produce artifacts (USER-PROFILE.md, `pp-dev-preferences` skill config, CLAUDE.md section) that personalize Claude's responses.
 
 Routes to the profile-user workflow which orchestrates the full flow: consent gate, session analysis or questionnaire fallback, profile generation, result display, and artifact selection.
 </objective>