@glexcorp/gskp 0.1.1 → 0.1.2

package/{global → base}/claude/skills/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog
 
+## v0.8 - 2026-06-13
+
+- Renamed the scanned skill set from "global" to "base": now scans `base/<tool>/*/SKILL.md`, and ungrouped skills are labeled `base` instead of `global`.
+
 ## v0.7 - 2026-06-12
 
 - Standardized active pack and skill install guidance on `npx skillpacks install <pack-or-skill>` instead of agent-native `/pack install` or `$pack install` recommendations.

package/base/claude/skills/SKILL.md

@@ -0,0 +1,141 @@
+---
+name: skills
+description: Browse and search all available skills, grouped by workflow stage or activity type
+type: ops
+version: v0.8
+argument-hint: "[list | types | search <keyword>]"
+---
+
+# Skills
+
+Discover and search installed base skills plus enabled project-local pack skills, grouped by workflow stage or activity type.
+
+## Process
+
+1. **Parse arguments:**
+   - If `$ARGUMENTS` is empty or `list` → **list mode** (show all skills grouped by workflow stage).
+   - If `$ARGUMENTS` is `types` → **type mode** (show all skills grouped by activity type).
+   - If `$ARGUMENTS` starts with `search ` → **search mode** (filter by keyword after `search`).
+
+2. **Discover skills:**
+   - Always scan base Claude skills in `base/claude/*/SKILL.md`.
+   - If `.agents/project.json` exists, read `enabled_packs` and scan `packs/<pack>/claude/*/SKILL.md` for each enabled pack. Also scan sub-directories like `packs/<pack>/claude/<skill>/frameworks/*/SKILL.md` for sub-skills.
+   - Also scan all packs in `packs/*/claude/*/SKILL.md` (and `frameworks/*/SKILL.md` children) to discover available-but-not-installed skills.
+   - If `.claude/skills/*/SKILL.md` exists in the current project, include those local skills too.
+   - Read the first 10 lines of each file to extract YAML frontmatter fields: `name`, `description`, `type`, `invocation`, `parent`.
+   - Track which pack each skill belongs to (if any).
+   - Default `invocation` to `primary` when the field is absent.
+
+3. **Group skills by workflow stage** using this static mapping:
+
+   The mapping includes base skills and pack-provided skills. Only skills
+   discovered in step 2 should be printed, so domain and kanban entries appear
+   only when the corresponding project-local pack is enabled or linked.
+   PoketoWork kanban skills are intentionally absent while the kanban packs are hibernated.
+
+   | Stage | Skills (pack in parentheses; no label = base) |
+   |-------|--------|
+   | Pack Management | `pack`, `pack list`, `pack status`, `pack recommend`, `npx skillpacks install <pack-or-skill>` (or project shell: `npx skillpacks install <pack-or-skill>`), `pack remove <pack-or-skill>`, `pack which <skill>` |
+   | Discovery & Market Fit | `customer-discovery` (business-discovery), `enterprise-icp` (business-discovery) |
+   | Game Development | `game-workflow` (game), `game-audience` (game), `game-fantasy` (game), `game-genre-map` (game), `game-comparables` (game), `game-core-loop` (game), `game-prototype-test` (game), `game-store-page-test` (game), `game-playtest-metrics` (game), `game-roadmap` (game), `game-launch` (game) |
+   | Devtool Development | `devtool-workflow` (devtool), `devtool-user-map` (devtool), `devtool-integration-map` (devtool), `devtool-dx-journey` (devtool), `devtool-adoption` (devtool), `devtool-positioning` (devtool), `devtool-monetization` (devtool), `devtool-docs-audit` (devtool) |
+   | Planning | `idea-scope-brief`, `brainstorm` (product-design), `feature-interview` (product-design), `user-flow-map` (product-design), `spec-interview` (product-design), `spec-interview --ideas` (product-design), `ui-interview` (product-design), `ux-variations` (product-design), `consolidate-variations` (product-design), `experiment` (business-growth) |
+   | Mapping | `journey-map` (customer-lifecycle), `metrics` (business-ops) |
+   | Strategize | `roadmap` (agent-work-admin), `competitive-analysis` (business-discovery), `platform-strategy` (business-growth), `gtm` (business-growth), `landing-copy` (business-growth), `monetization` (business-growth), `positioning` (business-discovery), `runway-model` (business-ops) |
+   | Evaluate | `dogfood` (product-testing), `mvp-gap` (business-discovery), `scale-audit` (business-ops), `customer-feedback` (customer-lifecycle), `assumption-tracker` (business-discovery), `cohort-review` (customer-lifecycle), `retro` (business-ops) |
+   | Research Health | `research-roadmap` (research-admin), `reconcile-research` (business-discovery), `reconcile-dev-docs` (docs-health) |
+   | Detail | `plan-phase` (agent-work-admin) |
+   | Execution | `exec` (exec-loop), `guide` (guided-walkthrough) |
+   | Shipping | `ship` (exec-loop), `ship-end` (exec-loop) |
+   | Code Quality | `expert-review` (code-review), `regression-check` (code-review), `dead-code` (code-review), `slim-audit` (code-review) |
+   | Debugging | `investigate` (code-debug), `debug` (code-debug), `trace` (code-debug), `session-triage` (session-analytics) |
+   | Refactoring & Migration | `migrate` (code-maintenance), `decommission` (teardown), `scaffold` (monorepo) |
+   | Monorepo | `affected` (monorepo), `mono-plan` (monorepo), `mono-guard` (monorepo) |
+   | Release & Deploy | `release` (release-ops), `deploy` (release-ops), `branch-lifecycle` (release-ops) |
+   | Context & Session | `afps-status`, `codebase-status`, `analyze-sessions` (session-analytics), `handoff` (context-transfer), `sync` (gitops), `investor-update` (business-ops) |
+   | Skill Development | `targeted-skill-builder` (skill-dev), `skill-interview` (skill-dev), `create-agentic-skill` (skill-dev), `create-local-skill` (skill-dev) |
+   | Testing | `uat` (product-testing), `uat-guide` (guided-walkthrough), `quiz-me` (knowledge-check) |
+   | Utility | `commit-and-push-by-feature` (gitops), `init-agentic-skills`, `provision-agentic-config`, `skills`, `bootstrap-repo` (repo-maintenance), `desk-flip` (teardown), `compile-central-alignment` (alignment-page-admin), `patch-exec-profile` (exec-profile), `delegate` (agent-bridge), `report-website` (report-gen), `icon-handler` (website-polish), `design-system` (product-design), `prototype` (product-design), `spec-drift` (agent-work-admin), `hygiene` (docs-health), `update-packages` (code-maintenance) |
+
+   Skills not found in the mapping go into an **Other** group at the end.
+
+4. **Group skills by activity type** (type mode only) using the `type` field from frontmatter:
+
+   | Type | Description |
+   |------|-------------|
+   | `research` | Web search + analysis → produces documents |
+   | `analysis` | Reads codebase/docs → produces assessments |
+   | `planning` | Interactive → produces specs/plans |
+   | `execution` | Writes/modifies code |
+   | `review` | Reads code → reports issues (no changes) |
+   | `debugging` | Investigates + fixes problems |
+   | `shipping` | Commits, deploys, session management |
+   | `ops` | Manages boards, branches, meta-tooling |
+
+   Display order: research → analysis → planning → execution → review → debugging → shipping → ops.
+   Skills with no `type` field go into an **Other** group at the end.
+
+5. **Apply filter (search mode only):**
+   - Match the keyword case-insensitively against each skill's `name`, `description`, and `type`.
+   - Keep only matching skills. Remove empty groups.
+
+6. **Output results:**
+   - Print each non-empty group as a `## Group Name` heading.
+   - Under each heading, list installed/base primary and chained skills as `/<name> — <description>  [type]`.
+   - Show orchestrator skills with an `⚙` prefix: `⚙ /<name> — <description>  [type]`.
+   - Show sub-skills indented under their parent skill (identified by the `parent:` frontmatter field or by living under a `frameworks/` directory). Format: `  ↳ /<name> — <description>  [sub-skill]`. If the parent is not in the same group, place sub-skills in a "Sub-skills" subsection at the end of the parent's group.
+   - For available-but-not-installed pack skills, list as `/<name> — <description>  [type]  ⚠ requires \`npx skillpacks install <skill>\` or \`npx skillpacks install <pack>\` inside Claude Code, or \`npx skillpacks install <pack-or-skill>\` from the project shell`.
+   - Omit groups that have no skills (after filtering in search mode).
+   - At the bottom, print a total count: `**N skills** installed (M sub-skills), **P skills** available via packs` (or `**N skills** matching "<keyword>"`).
+
+## Output
+
+### List mode (default — grouped by workflow stage)
+```
+## Discovery & Market Fit
+/customer-discovery — Customer discovery interview...  [research]
+/enterprise-icp — Enterprise multi-stakeholder discovery...  [research]
+
+## Strategize
+⚙ /positioning — Parent router — detect market vs product mode...  [research]
+  ↳ /category-design — Play Bigger category design framework  [sub-skill]
+  ↳ /jtbd-positioning — Jobs to Be Done positioning framework  [sub-skill]
+  ↳ /moore-positioning — Geoffrey Moore positioning framework  [sub-skill]
+  ↳ /obviously-awesome — Obviously Awesome positioning framework  [sub-skill]
+  ↳ /strategic-canvas — Strategic Canvas positioning framework  [sub-skill]
+/competitive-analysis — Research competitors...  [research]
+...
+
+## Execution
+⚙ /exec — Execute next plan step...  [execution]
+...
+
+**N skills** installed (M sub-skills), **P skills** available via packs
+```
+
+### Type mode (`/skills types`)
+```
+## Research
+/customer-discovery — Customer discovery interview...
+/competitive-analysis — Research competitors...
+...
+
+## Analysis
+/mvp-gap — Evaluate codebase against customer-discovery evidence...
+...
+
+**N skills** found
+```
+
+## Constraints
+
+- This is a read-only scan — never modify any files.
+- Always read the live frontmatter from SKILL.md files; do not hardcode descriptions.
+- Use the static stage mapping for stage grouping; use the `type` frontmatter field for type grouping.
+- Keep output compact — one line per skill, no extra detail beyond name, description, and type tag.
+- In search mode, if no skills match the keyword, print: `No skills matching "<keyword>"`.
+
+
+## Default Shipping Contract
+
+Follow the shared shipping contract convention in CLAUDE.md.

package/{global → base}/codex/init-agentic-skills/CHANGELOG.md

@@ -1,5 +1,17 @@
 # Changelog
 
+## v0.11 - 2026-06-13
+
+- Sunset the user-home (global) install path. Base skills now install **project-local** via `npx skillpacks init` only; there is no `init.sh`, `--global`, or `~/.codex/skills` base install. Rewrote the process around `npx skillpacks` (`init`/`refresh`/`status`/`doctor`) and added an `uninstall-global` mode that runs `npx skillpacks uninstall-global` to clean up legacy repo-managed installs left in `~/.claude/skills` and `~/.codex/skills`. Dropped the `update`/`latest` checkout-refresh flow and the first-run drift-preference prompts that depended on the retired launcher.
+
+## v0.10 - 2026-06-13
+
+- Renamed the source skill set from "global" to "base": canonical sources moved to `base/<tool>/<skill>`, and drift/refresh prose now says "base skills". The `--global`/`init-global` install-location flags are unchanged.
+
+## v0.9 - 2026-06-13
+
+- Switched the default project-shell pack install recommendation from `npx gskp install <pack-or-skill>` to `npx skillpacks install <pack-or-skill>`, matching the canonical install-routing contract and the Claude mirror.
+
 ## v0.8 - 2026-06-12
 
 - Standardized active pack and skill install guidance on `npx gskp install <pack-or-skill>` instead of agent-native `/pack install` or `$pack install` recommendations.

package/base/codex/init-agentic-skills/SKILL.md

@@ -0,0 +1,43 @@
+---
+name: init-agentic-skills
+description: Make the base agentic-skills available in a project by installing them project-local with npx skillpacks init, report and fix skill-install drift, clean up legacy user-home installs, and route domain packs to the pack skill. Use when Codex needs to enable base skills for a project, repair stale installs, confirm initialization status, remove old global installs, or explain how to enable packs.
+type: ops
+version: v0.11
+argument-hint: "[init|status|doctor|refresh|uninstall-global]"
+---
+
+# Init Agentic Skills
+
+Invoke as `$init-agentic-skills`.
+
+Make the base agentic-skills available by installing them **project-local** into the current project's `.claude/skills` and `.codex/skills`. Installation is distributed through the npm `skillpacks` package — there is no user-home (global) install path. Active installs are repo-managed directories that expose the canonical `SKILL.md` and exclude `archive/`; pinned installs intentionally point at `archive/<version>`. Keep domain packs project-local too; use `$pack` from the target project or `npx skillpacks install <pack-or-skill>` when packs are needed.
+
+## Process
+
+1. Parse `$ARGUMENTS`:
+   - No args, `init`, or `refresh`: run `npx skillpacks init` from the project root to install the base skills project-local (`.claude/skills` + `.codex/skills`) and enable `base_skills` in `.agents/project.json`. Use `npx skillpacks refresh` instead when the project is already initialized and you only need to recreate roots from `.agents/project.json`.
+   - `status`: run `npx skillpacks status` to report the project designation, enabled packs, and installed skills.
+   - `doctor`: run `npx skillpacks doctor` to report project skill-install drift (read-only). It compares installed `.claude/skills` and `.codex/skills` copies against their canonical sources via the `.agentic-skills-managed` marker's `source_sha`. Report `STALE` skills with the printed fix command, `unknown` skills as needing a refresh to enable tracking, `missing` skills whose source is gone, and `pinned` skills as frozen. Run `npx skillpacks doctor --fix` to clean generated skill-root drift.
+   - `uninstall-global`: run `npx skillpacks uninstall-global` only after confirming the user wants legacy repo-managed base installs removed from `~/.claude/skills` and `~/.codex/skills`. This cleans up installs created by the retired user-home init path; it removes only skillpacks-owned installs and leaves unmanaged directories untouched.
+   - `help`, `--help`, or `-h`: run `npx skillpacks --help`.
+2. Report the command run, the project skill directories, installed counts, and any warnings about non-repo-managed collisions.
+3. Explain pack access separately:
+   - Do not install `packs/*` as base skills.
+   - In the project that needs domain workflows, run `$pack` for guided setup, or `npx skillpacks install <pack-or-skill>` from the project shell for an explicit pack or individual pack skill.
+   - If a project already has `.agents/project.json`, use `$pack refresh` (or `npx skillpacks refresh`) after this base initialization to recreate local pack skill roots.
+4. If the active session still cannot see a newly installed or refreshed skill, report the skill-visibility reload path:
+   - Claude Code: run `/reload-skills` first; `/clear` starts a new empty-context conversation and can pick up the refreshed registry; restart if the top-level `.claude/skills` directory did not exist at session start or the skill is still invisible.
+   - Codex: start a fresh Codex CLI session if the `$` skill list remains stale.
+
+## Constraints
+
+- Drive installation through `npx skillpacks` (the npm `skillpacks` CLI); do not recreate install logic by hand or reintroduce a user-home/global install path.
+- Base skills are project-local: they install into the current project's `.claude/skills` and `.codex/skills`, not into `~/.claude/skills` or `~/.codex/skills`.
+- Do not overwrite real directories or files under `.claude/skills` or `.codex/skills` that are not repo-managed.
+- Treat packs as project-local capabilities managed through `$pack` (`npx skillpacks` under the hood).
+- Stop and report exact errors if `npx skillpacks` fails.
+- Do not install `packs/*` as base skills in any mode.
+
+## Default Shipping Contract
+
+Follow the shared shipping contract convention in CLAUDE.md.

package/base/codex/init-agentic-skills/agents/openai.yaml

@@ -0,0 +1,7 @@
+interface:
+  display_name: "Init Agentic Skills"
+  short_description: "Initialize base Claude and Codex skills from this checkout"
+  default_prompt: "Use $init-agentic-skills to run the agentic-skills initializer, refresh base managed skill installs, and explain how to enable project-local packs."
+
+policy:
+  allow_implicit_invocation: true

package/base/codex/init-agentic-skills/archive/v0.10/SKILL.md

@@ -0,0 +1,58 @@
+---
+name: init-agentic-skills
+description: Initialize this agentic-skills checkout on a developer machine by running the repository init script, verify base managed skill installs, uninstall repo-managed installs when requested, and route project-local pack setup to the pack skill. Use when Codex needs to make all base agentic-skills skills available on the current machine, repair stale installs, confirm initialization status, or explain how to enable packs for a project.
+type: ops
+version: v0.10
+argument-hint: "[init|status|doctor|update|latest|--uninstall]"
+---
+
+# Init Agentic Skills
+
+Invoke as `$init-agentic-skills`.
+
+Initialize this `agentic-skills` checkout on the current machine by installing base skills for both Claude and Codex. Active installs are repo-managed directories that expose the canonical `SKILL.md` and exclude `archive/`; copied managed launchers resolve this checkout through `.agentic-skills-managed` provenance. Pinned installs intentionally point at `archive/<version>`. Keep domain packs project-local; use `$pack` from the target project or `npx skillpacks install <pack-or-skill>` from the project shell when packs are needed.
+
+## Process
+
+1. Parse `$ARGUMENTS`:
+   - No args, `init`, `refresh`, or `sync`: run `scripts/init-agentic-skills.sh`, then run the first-run setup prompts in step 6 when the drift preferences are still unset.
+   - `status`: run `scripts/init-agentic-skills.sh status`, then report the local checkout commit, remote URL, and whether GitHub freshness is enabled by `~/.agentic-skills/preferences.json` at `sync.github_freshness_check`.
+   - `doctor`: run `scripts/init-agentic-skills.sh doctor` to report base skill-install drift (read-only). It compares installed `~/.claude/skills` and `~/.codex/skills` copies against canonical `base/<tool>/<skill>` via the `.agentic-skills-managed` marker's `source_sha`. Report `stale` skills with the fix `$init-agentic-skills update`, `unknown` skills as needing a re-init to enable tracking, and `pinned` skills as frozen.
+   - `update` or `latest`: run `scripts/init-agentic-skills.sh update` only after confirming the user wants to check GitHub, fast-forward the local checkout, and rerun `init.sh`. This re-copy is the base "refresh" — it rewrites markers with current `source_version`/`source_sha`, clearing drift.
+   - `--uninstall`, `uninstall`, or `remove`: run `scripts/init-agentic-skills.sh --uninstall` only after confirming the user wants repo-managed base installs removed.
+   - `help`, `--help`, or `-h`: run `scripts/init-agentic-skills.sh --help`.
+2. Report the initializer command, the Claude and Codex skill directories, installed/skipped counts, and warnings about non-repo-managed collisions.
+3. Explain pack access separately:
+   - Do not install `packs/*` as base skills.
+   - In the project that needs domain workflows, run `$pack` for guided setup, or `npx skillpacks install <pack-or-skill>` from the project shell for an explicit pack or individual pack skill.
+   - If a project already has `.agents/project.json`, use `$pack refresh` after this base initialization to recreate local pack skill roots.
+4. If the active session still cannot see a newly installed or refreshed skill, report the skill-visibility reload path:
+   - Claude Code: run `/reload-skills` first; `/clear` starts a new empty-context conversation and can pick up the refreshed registry; restart if the top-level `.claude/skills` directory did not exist at session start or the skill is still invisible.
+   - Codex: start a fresh Codex CLI session if the `$` skill list remains stale.
+5. For `update` / `latest` mode:
+   - Confirm before running commands that fetch, pull, or reinstall.
+   - Fetch GitHub freshness, compare the local checkout to `origin/HEAD`, and update only with a fast-forward-only operation such as `git pull --ff-only` or an equivalent `git fetch` + `git merge --ff-only`.
+   - If the update cannot fast-forward cleanly, stop and report the exact reason without rebasing, merging, stashing, or force-resetting.
+   - After a successful fast-forward, rerun `init.sh`.
+   - Warn that Claude Code should use `/reload-skills` first, then `/clear` or restart if needed, and that Codex should start a fresh Codex CLI session if the `$` skill list remains stale.
+6. First-run drift preferences (init / clone setup):
+   - Default policy is **track-latest** (installed skills follow canonical; drift is observable). The two prompts below are **opt-in and off by default**, so the explicit-control default stays out of the box.
+   - Only prompt when the preference keys are still unset. Check with `scripts/init-agentic-skills.sh show-prefs`; skip silently when both are already set.
+   - Ask (a): "Enable a session-start hook that warns when tracked skills are behind canonical?" Default **no**.
+     - If yes: run `scripts/init-agentic-skills.sh hook enable` (registers a `SessionStart` hook in `~/.claude/settings.json` invoking `scripts/skill-drift-hook.sh` and sets `skills.session_start_hook=true`).
+     - If no: run `scripts/init-agentic-skills.sh set-pref session_start_hook false`.
+   - Ask (b): "Auto-refresh latest skills on session start (instead of just warning)?" Default **no**.
+     - Run `scripts/init-agentic-skills.sh set-pref auto_refresh <true|false>` with the answer. Auto-refresh only takes effect when the hook is enabled.
+   - To disable later: decline the prompt, run `scripts/init-agentic-skills.sh set-pref session_start_hook false`, or run `scripts/init-agentic-skills.sh hook disable` to remove the settings entry.
+
+## Constraints
+
+- Delegate base initialization to `scripts/init-agentic-skills.sh`; do not recreate install logic by hand.
+- Do not overwrite real directories or files under `~/.claude/skills`, `~/.codex/skills`, `.claude/skills`, or `.codex/skills`.
+- Treat packs as project-local capabilities managed by `scripts/pack.sh` through `$pack`.
+- Stop and report exact errors if the launcher cannot resolve the repository root or if root `init.sh` fails.
+- Do not install `packs/*` as base skills in any mode.
+
+## Default Shipping Contract
+
+Follow the shared shipping contract convention in CLAUDE.md.

package/base/codex/init-agentic-skills/archive/v0.9/SKILL.md

@@ -0,0 +1,58 @@
+---
+name: init-agentic-skills
+description: Initialize this agentic-skills checkout on a developer machine by running the repository init script, verify global managed skill installs, uninstall repo-managed installs when requested, and route project-local pack setup to the pack skill. Use when Codex needs to make all global agentic-skills skills available on the current machine, repair stale installs, confirm initialization status, or explain how to enable packs for a project.
+type: ops
+version: v0.9
+argument-hint: "[init|status|doctor|update|latest|--uninstall]"
+---
+
+# Init Agentic Skills
+
+Invoke as `$init-agentic-skills`.
+
+Initialize this `agentic-skills` checkout on the current machine by installing global core skills for both Claude and Codex. Active installs are repo-managed directories that expose the canonical `SKILL.md` and exclude `archive/`; copied managed launchers resolve this checkout through `.agentic-skills-managed` provenance. Pinned installs intentionally point at `archive/<version>`. Keep domain packs project-local; use `$pack` from the target project or `npx skillpacks install <pack-or-skill>` from the project shell when packs are needed.
+
+## Process
+
+1. Parse `$ARGUMENTS`:
+   - No args, `init`, `refresh`, or `sync`: run `scripts/init-agentic-skills.sh`, then run the first-run setup prompts in step 6 when the drift preferences are still unset.
+   - `status`: run `scripts/init-agentic-skills.sh status`, then report the local checkout commit, remote URL, and whether GitHub freshness is enabled by `~/.agentic-skills/preferences.json` at `sync.github_freshness_check`.
+   - `doctor`: run `scripts/init-agentic-skills.sh doctor` to report global skill-install drift (read-only). It compares installed `~/.claude/skills` and `~/.codex/skills` copies against canonical `global/<tool>/<skill>` via the `.agentic-skills-managed` marker's `source_sha`. Report `stale` skills with the fix `$init-agentic-skills update`, `unknown` skills as needing a re-init to enable tracking, and `pinned` skills as frozen.
+   - `update` or `latest`: run `scripts/init-agentic-skills.sh update` only after confirming the user wants to check GitHub, fast-forward the local checkout, and rerun `init.sh`. This re-copy is the global "refresh" — it rewrites markers with current `source_version`/`source_sha`, clearing drift.
+   - `--uninstall`, `uninstall`, or `remove`: run `scripts/init-agentic-skills.sh --uninstall` only after confirming the user wants repo-managed global installs removed.
+   - `help`, `--help`, or `-h`: run `scripts/init-agentic-skills.sh --help`.
+2. Report the initializer command, the Claude and Codex skill directories, installed/skipped counts, and warnings about non-repo-managed collisions.
+3. Explain pack access separately:
+   - Do not install `packs/*` globally.
+   - In the project that needs domain workflows, run `$pack` for guided setup, or `npx skillpacks install <pack-or-skill>` from the project shell for an explicit pack or individual pack skill.
+   - If a project already has `.agents/project.json`, use `$pack refresh` after this global initialization to recreate local pack skill roots.
+4. If the active session still cannot see a newly installed or refreshed skill, report the skill-visibility reload path:
+   - Claude Code: run `/reload-skills` first; `/clear` starts a new empty-context conversation and can pick up the refreshed registry; restart if the top-level `.claude/skills` directory did not exist at session start or the skill is still invisible.
+   - Codex: start a fresh Codex CLI session if the `$` skill list remains stale.
+5. For `update` / `latest` mode:
+   - Confirm before running commands that fetch, pull, or reinstall.
+   - Fetch GitHub freshness, compare the local checkout to `origin/HEAD`, and update only with a fast-forward-only operation such as `git pull --ff-only` or an equivalent `git fetch` + `git merge --ff-only`.
+   - If the update cannot fast-forward cleanly, stop and report the exact reason without rebasing, merging, stashing, or force-resetting.
+   - After a successful fast-forward, rerun `init.sh`.
+   - Warn that Claude Code should use `/reload-skills` first, then `/clear` or restart if needed, and that Codex should start a fresh Codex CLI session if the `$` skill list remains stale.
+6. First-run drift preferences (init / clone setup):
+   - Default policy is **track-latest** (installed skills follow canonical; drift is observable). The two prompts below are **opt-in and off by default**, so the explicit-control default stays out of the box.
+   - Only prompt when the preference keys are still unset. Check with `scripts/init-agentic-skills.sh show-prefs`; skip silently when both are already set.
+   - Ask (a): "Enable a session-start hook that warns when tracked skills are behind canonical?" Default **no**.
+     - If yes: run `scripts/init-agentic-skills.sh hook enable` (registers a `SessionStart` hook in `~/.claude/settings.json` invoking `scripts/skill-drift-hook.sh` and sets `skills.session_start_hook=true`).
+     - If no: run `scripts/init-agentic-skills.sh set-pref session_start_hook false`.
+   - Ask (b): "Auto-refresh latest skills on session start (instead of just warning)?" Default **no**.
+     - Run `scripts/init-agentic-skills.sh set-pref auto_refresh <true|false>` with the answer. Auto-refresh only takes effect when the hook is enabled.
+   - To disable later: decline the prompt, run `scripts/init-agentic-skills.sh set-pref session_start_hook false`, or run `scripts/init-agentic-skills.sh hook disable` to remove the settings entry.
+
+## Constraints
+
+- Delegate global initialization to `scripts/init-agentic-skills.sh`; do not recreate install logic by hand.
+- Do not overwrite real directories or files under `~/.claude/skills`, `~/.codex/skills`, `.claude/skills`, or `.codex/skills`.
+- Treat packs as project-local capabilities managed by `scripts/pack.sh` through `$pack`.
+- Stop and report exact errors if the launcher cannot resolve the repository root or if root `init.sh` fails.
+- Do not install `packs/*` globally in any mode.
+
+## Default Shipping Contract
+
+Follow the shared shipping contract convention in CLAUDE.md.

package/{global → base}/codex/pack/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## v0.10 - 2026-06-13
+
+- Base-skill install reference updated from the retired `init.sh` to project-local `npx skillpacks init`.
+
+## v0.9 - 2026-06-13
+
+- Renamed the domain-neutral core skill set from "global" to "base" in the description and notes (these are the `init.sh`-initialized base skills).
+
 ## v0.8 - 2026-06-12
 
 - Standardized active pack and skill install guidance on `npx skillpacks install <pack-or-skill>` instead of agent-native `/pack install` or `$pack install` recommendations.

package/base/codex/pack/SKILL.md

@@ -0,0 +1,172 @@
+---
+name: pack
+description: Manage project-local skill packs, individual pack skill roots, and project designation without installing domain skills as base skills
+type: ops
+version: v0.10
+argument-hint: "[list|status|recommend|install <pack-or-skill>|remove <pack-or-skill>|refresh|which <skill>] or no args for guided setup"
+---
+
+# Pack
+
+Invoke as `$pack`.
+
+Use this skill when the user wants to inspect, recommend, install, remove, or refresh project-local skill packs or individual skills from those packs.
+
+## Process
+
+1. Parse `$ARGUMENTS`.
+   - Treat commas as separators.
+   - Treat `business` as `business-app`.
+   - Ignore filler words such as `pack` or `packs`.
+2. If no arguments were provided, run guided setup:
+   - If `.agents/project.json` exists, run `scripts/pack.sh refresh` to recreate local pack skill roots from committed project state, then report the project type, enabled packs, and installed skills.
+   - If `.agents/project.json` is missing, inspect the repository before asking the user:
+     - Run `scripts/pack.sh recommend`.
+     - Check top-level files and directories, package manifests, app/framework configs, source layout, docs, existing `research/`, `specs/`, and `tasks/` files.
+     - Classify likely packs using the pack selection rules below.
+     - Present a concise recommendation with evidence.
+     - Present a plain-text **Pack Decision Checkpoint**: show 2-4 numbered choices, mark the recommended choice, explain the tradeoff for each, and ask the user to reply with a number, exact pack list, `status`, or `cancel`.
+     - Stop after the checkpoint. Do not install anything until the user explicitly confirms a choice in a later message.
+     - After the user confirms, run the source-checkout helper `scripts/pack.sh install <pack...>`. For package consumers outside this checkout, the equivalent project-shell route is `npx skillpacks install <pack...>`.
+   - If `.agents/project.json` exists but `refresh` fails, report the failure and the exact command the user can retry.
+3. Run the matching helper command from this skill library's bundled launcher for explicit commands:
+   - `scripts/pack.sh list`
+   - `scripts/pack.sh status`
+   - `scripts/pack.sh recommend`
+   - `scripts/pack.sh install <pack-or-skill>` (source checkout) or `npx skillpacks install <pack-or-skill>` (published package from the project shell)
+   - `scripts/pack.sh remove <pack-or-skill>`
+   - `scripts/pack.sh refresh`
+   - `scripts/pack.sh which <skill>`
+   The launcher is intentionally located at `scripts/pack.sh` under this skill directory and forwards to the repository-level pack manager.
+4. For `install`, `remove`, `refresh`, and guided setup installs, report:
+   - `.agents/project.json` project type and enabled packs
+   - any `enabled_skills` entries when present, including the skill name and source pack
+   - any `project_scopes` entries when present, including the path, `project_type`, packs, and purpose
+   - local skill roots created or removed under `.claude/skills` and `.codex/skills`
+   - any skipped roots caused by non-repo-managed targets
+   - shipping guidance: `.agents/project.json` is the committed project designation and should be committed when pack configuration changed; `.claude/skills/**` and `.codex/skills/**` are generated local skill roots recreated by `/pack`, `$pack`, or `scripts/pack.sh refresh`, and generated skill roots must not be staged or committed
+   - skill-visibility reload guidance: Claude Code watches existing `.claude/skills` roots and supports `/reload-skills`; `/clear` starts a new conversation and can pick up the refreshed registry, while a full restart remains the fallback if the top-level skills directory did not exist at session start or the skill remains invisible. Codex users should start a fresh Codex CLI session if the active session does not show the changed skills.
+
+## Pack Model
+
+- Base skills are domain-neutral and installed project-local by `npx skillpacks init`.
+- Domain workflows live in project-local packs.
+- Project designation is stored in `.agents/project.json`.
+- `.agents/project.json` is the committed project designation. `.claude/skills/**` and `.codex/skills/**` are generated local skill roots and must not be staged or committed; recreate them with `/pack`, `$pack`, or `scripts/pack.sh refresh`.
+- Mixed monorepos may keep a coarse default `project_type` and add `project_scopes` entries for subtrees that need different domain routing.
+- `enabled_packs` is the union of packs available to the repository; `project_scopes[].packs` explains which packs are appropriate for a specific path or glob.
+- Pack installs use repo-managed skill roots that point back to this skill-library repository and exclude archived skill snapshots by default.
+- The bundled launcher resolves copied managed installs through `.agentic-skills-managed` provenance before delegating to the repository-level pack manager.
+- `scripts/pack.sh install`, `remove`, `refresh`, and `set-mode` preserve existing `project_scopes` and `notes` fields when `jq` is available.
+- `scripts/pack.sh install <name>` treats `<name>` as a pack first, then as an individual skill provided by a pack. Package consumers use `npx skillpacks install <name>` for the same pack-or-skill resolution from the project shell.
+- Pack writes use `.agents/.pack.lock` with owner metadata (`pid`, `started_at`, `command`); if a recorded owner process is gone, the next pack command removes that stale lock automatically.
+- `scripts/pack.sh refresh` recreates project-local skill roots from `.agents/project.json`; it does not by itself force an active CLI skill registry to reload.
+- Claude Code watches skill files under existing `.claude/skills` roots and supports `/reload-skills` to rescan skills and commands during a session. If a newly installed skill is not visible, run `/reload-skills`; `/clear` starts a new empty-context conversation and can also pick up the refreshed registry. Restart Claude Code if the top-level `.claude/skills` directory did not exist when the session started or the skill is still invisible.
+- Codex may keep the `$` skill list loaded from session start. This pack workflow has no supported in-session Codex CLI skill refresh command, so start a fresh Codex CLI session if changed skills are not visible.
+
+## Individual Skill Installation
+
+When a name passed to `install` or `remove` does not match a pack, the system checks whether it matches a skill inside any pack. If it does, only that single skill root is installed, not the entire pack.
+
+- `npx skillpacks install design-system` from the project shell installs only the `design-system` skill from `product-design`, not the whole pack.
+- `npx skillpacks install code-review customer-discovery` from the project shell installs the `code-review` pack plus the individual `customer-discovery` skill.
+- `$pack remove customer-discovery` removes only the `customer-discovery` skill root and its `enabled_skills` entry.
+- `$pack which design-system` shows the source pack and whether the skill is installed.
+
+Individual skills are tracked in `enabled_skills` in `.agents/project.json`:
+
+```json
+{
+  "enabled_skills": {"customer-discovery": "business-discovery", "positioning": "business-discovery"}
+}
+```
+
+The `{skill: pack}` format tracks provenance so `refresh` knows where to rebuild from. When a name matches both a pack and a skill, the pack takes precedence.
+
+## Pack Selection
+
+- Use `business-discovery`, `customer-lifecycle`, `business-growth`, or `business-ops` for SaaS, marketplaces, productivity apps, internal/admin tools, business workflows, and enterprise applications. `business-app` is a compatibility alias for all four.
+- Use `creator-foundation`, `youtube-ops`, and `remotion` separately for creator-media work; `creator-media` is a compatibility alias for foundation plus YouTube operations.
+- Use `project-fleet` for control repositories that manage downstream repos, spec-store portfolios, or spin-offs.
+- Use `code-quality` as an additive pack for behavior-preserving refactors, type hygiene, import honesty, dependency-boundary cleanup, and module organization.
+- Use `alignment-loop` for lightweight operator-agent calibration before committing to a full spec-interview pipeline.
+- Use `game` for video games, prototypes, playable entertainment, game engines, store pages, playtest loops, and game assets.
+- Use `devtool` for SDKs, CLIs, APIs, libraries, infrastructure products, developer platforms, and documentation-first developer workflows.
+- PoketoWork kanban packs (`business-app-kanban`, `devtool-kanban`, `game-kanban`, and `poketowork-kanban`) are hibernated while Poketo.work is being rebuilt. Do not recommend or install kanban packs until they are reactivated.
+- Treat `monorepo` and `code-quality` as overlays. Pair overlays with a domain pack unless the user explicitly wants only the overlay behavior.
+- For workflow ordering, lead-in recommendations, and overlay dependencies, read `docs/pack-workflow-matrix.md`.
+
+## Mixed Monorepos
+
+Use one repo-level `.agents/project.json` with a primary default plus scoped overrides:
+
+```json
+{
+  "project_type": "devtool",
+  "enabled_packs": ["devtool", "business-discovery", "customer-lifecycle", "business-growth"],
+  "skill_pack_version": 1,
+  "project_scopes": [
+    {
+      "path": "apps/pitwall-local",
+      "project_type": "devtool",
+      "packs": ["devtool"],
+      "purpose": "Pitwall Local / OSS developer utility work."
+    },
+    {
+      "path": "apps/pitwall-calcllm",
+      "project_type": "business-app",
+      "packs": ["business-discovery", "customer-lifecycle", "business-growth"],
+      "purpose": "CalcLLM-powered connected edition research, GTM, monetization, and SaaS product work."
+    },
+    {
+      "path": "packages/calcllm-sync",
+      "project_type": "business-app",
+      "packs": ["business-discovery", "customer-lifecycle", "business-growth"],
+      "purpose": "Connected-edition sync and SaaS integration work."
+    }
+  ]
+}
+```
+
+When a task clearly names a scoped path, route to that scope's `project_type` and packs. When no scope matches, use the top-level `project_type` as the default.
+
+## Pack Decision Checkpoint
+
+Use this format when Codex needs user confirmation and `request_user_input` is unavailable:
+
+```
+## Pack Decision Checkpoint
+
+Detected:
+- [evidence]
+
+Recommendation: `<pack>` because [reason].
+
+Choose one:
+1. `<pack>` (Recommended) — [impact/tradeoff]
+2. `<alternate-pack>` — [impact/tradeoff]
+3. `<pack> <matching-kanban-pack>` — [impact/tradeoff]
+4. `cancel` — leave the project unconfigured
+
+Reply with a number or an exact pack list to install.
+```
+
+## Missing Skill Resolution
+
+When a user invokes a skill that is not found in the current session:
+
+1. Run `scripts/pack.sh which <skill-name>` to check if the skill exists in any pack.
+2. If found in an uninstalled pack: tell the user which pack provides the skill, recommend `npx skillpacks install <pack-or-skill>` from the project shell for either the skill or the full pack, and note the post-install reload path: Claude Code `/reload-skills` first, `/clear` or restart if needed; Codex fresh session if the `$` list stays stale.
+3. If found in an installed pack: the skill should already be available, so suggest the same reload path to pick up the local skill roots.
+4. If not found in any pack: suggest `$skills` to browse available skills or `$skills search <keyword>` to search.
+
+## Constraints
+
+- Never install `packs/*` into `~/.claude/skills` or `~/.codex/skills`.
+- Do not overwrite real directories or files in `.claude/skills` or `.codex/skills`; skip them with a warning.
+- If local skill discovery is not available in the active assistant, treat `pack` as the launcher and read the project-local pack files directly.
+- Do not create `.agents/project.json` without user confirmation during guided setup.
+
+## Default Shipping Contract
+
+Follow the shared shipping contract convention in CLAUDE.md.