skillpacks 0.1.1 → 0.1.2

package/AGENTS.md

@@ -1,9 +1,9 @@
-<!-- provision-agentic-config v0.5 -->
+<!-- provision-agentic-config v0.11 -->
 ## Workflow Orchestration
 
 ### 1. Plan Mode Default
 - Enter plan mode for ANY non-trivial task (3+ steps or architectural decisions)
-- If something goes sideways, STOP and re-plan immediately — don't keep pushing
+- If something goes sideways, STOP and re-plan immediately - don't keep pushing
 - Verification is mandatory, but routine no-op verification runs inside the active execution/shipping step. Enter plan mode for non-trivial remediation or new work discovered by verification, not for validation that already has clear commands and no expected source changes.
 - Write detailed specs upfront to reduce ambiguity
 - In Codex: use `update_plan` in Default mode and `request_user_input` only when already in Plan mode
@@ -30,25 +30,19 @@
 ### 5. Demand Elegance (Balanced)
 - For non-trivial changes: pause and ask "is there a more elegant way?"
 - If a fix feels hacky: "Knowing everything I know now, implement the elegant solution"
-- Skip this for simple, obvious fixes — don't over-engineer
+- Skip this for simple, obvious fixes - don't over-engineer
 - Challenge your own work before presenting it
 
 ### 6. Autonomous Bug Fixing
 - When given a bug report: just fix it. Don't ask for hand-holding
-- Point at logs, errors, failing tests — then resolve them
+- Point at logs, errors, failing tests - then resolve them
 - Zero context switching required from the user
 - Go fix failing tests without being told how
 
 ### Missing Skill Fallback
-- When a skill invocation fails because the skill is not found, run `scripts/pack.sh which <skill-name>` to check if the skill exists in an available pack.
-- If found in an uninstalled pack, recommend `$pack install <skill>` for just that skill or `$pack install <pack>` for the full pack, and note the post-install reload path: Claude Code `/reload-skills` first, `/clear` 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 should start a fresh Codex CLI session if the `$` skill list remains stale.
-- If found in an installed pack, suggest the same reload path to pick up the local skill roots.
-- If not found in any pack, suggest `$skills` or `$skills search <keyword>`.
-
-### Project Pack Command Resolution
 - If a user invokes a command-like skill such as `$benchmark-test-skill design-system` and the leading command is not in the injected session skill list, search project-local packs before falling back to the trailing argument as the active skill.
-- Check `packs/*/codex/<command>/SKILL.md` and pack metadata such as `packs/*/PACK.md`; project-local pack skills may exist in this repository even when they are not visible in the active session list.
-- In this repository, `$benchmark-test-skill` lives under `packs/agentic-skills-bench/codex/benchmark-test-skill/SKILL.md`, and `design-system` is its target skill argument.
+- Check `packs/*/codex/*/SKILL.md` and pack metadata such as `packs/*/PACK.md`; project-local pack skills may exist in this repository even when they are not visible in the active session list.
+- For any missing skill, run `scripts/pack.sh which <skill-name>` to locate the providing pack. If found in an uninstalled pack, 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` 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 should start a fresh Codex CLI session if the `$` skill list remains stale. If found in an installed pack, suggest the same reload path. If not found in any pack, suggest `$skills` or `$skills search <keyword>`.
 
 ### Prompt History
 - On every skill invocation, before substantive work, create `prompts/<skill-slug>/` if it does not exist.
@@ -88,7 +82,7 @@
 - **No Laziness**: Find root causes. No temporary fixes. Senior developer standards.
 - **Minimal Impact**: Changes should only touch what's necessary. Avoid introducing bugs.
 - **Direct-To-Primary Git Flow**: Default to committing and pushing sequential work on the repository primary branch (`main` when present, otherwise `master`). Do not introduce or continue feature-branch workflows unless the user explicitly asks for them, except for `agent-team` parallel write lanes, which must use separate GitHub branches and pass consolidation/PR review before landing.
-- **Always Ship Mutations**: If a task creates or modifies tracked files, finish by committing and pushing all intended changes before stopping unless the user explicitly says not to. Codex `$exec` ships by default (validates, commits, pushes, plans next) — use `$ship` only to package existing work or unpushed commits.
+- **Always Ship Mutations**: If a task creates or modifies tracked files, finish by committing and pushing all intended changes before stopping unless the user explicitly says not to. Do not leave a dirty tracked tree or unpushed commits behind.
 - **No GitHub Actions**: Do not create, modify, or suggest GitHub Actions workflows unless the user explicitly asks for GitHub Actions. This project does not use GitHub Actions for CI/CD by default.
 
 ## Windows/WSL File Opening

package/CLAUDE.md

@@ -1,9 +1,9 @@
-<!-- provision-agentic-config v0.5 -->
+<!-- provision-agentic-config v0.11 -->
 ## Workflow Orchestration
 
 ### 1. Plan Mode Default
 - Enter plan mode for ANY non-trivial task (3+ steps or architectural decisions)
-- If something goes sideways, STOP and re-plan immediately — don't keep pushing
+- If something goes sideways, STOP and re-plan immediately - don't keep pushing
 - Verification is mandatory, but routine no-op verification runs inside the active execution/shipping step. Enter plan mode for non-trivial remediation or new work discovered by verification, not for validation that already has clear commands and no expected source changes.
 - Write detailed specs upfront to reduce ambiguity
 - In Codex: use `update_plan` in Default mode and `request_user_input` only when already in Plan mode
@@ -19,7 +19,6 @@
 - After ANY correction from the user: update `tasks/lessons.md` with the pattern
 - Write rules for yourself that prevent the same mistake
 - Ruthlessly iterate on these lessons until mistake rate drops
-- For misunderstood-intent corrections, capture: what the user wanted, what the agent interpreted, and which signal was missed
 - Review lessons at session start for relevant project
 
 ### 4. Verification Before Done
@@ -31,18 +30,18 @@
 ### 5. Demand Elegance (Balanced)
 - For non-trivial changes: pause and ask "is there a more elegant way?"
 - If a fix feels hacky: "Knowing everything I know now, implement the elegant solution"
-- Skip this for simple, obvious fixes — don't over-engineer
+- Skip this for simple, obvious fixes - don't over-engineer
 - Challenge your own work before presenting it
 
 ### 6. Autonomous Bug Fixing
 - When given a bug report: just fix it. Don't ask for hand-holding
-- Point at logs, errors, failing tests — then resolve them
+- Point at logs, errors, failing tests - then resolve them
 - Zero context switching required from the user
 - Go fix failing tests without being told how
 
 ### Missing Skill Fallback
 - When a skill invocation fails because the skill is not found, run `scripts/pack.sh which <skill-name>` to check if the skill exists in an available pack.
-- If found in an uninstalled pack, recommend `/pack install <skill>` for just that skill or `/pack install <pack>` for the full pack, and note the post-install reload path: Claude Code `/reload-skills` first, `/clear` 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 should start a fresh Codex CLI session if the `$` skill list remains stale.
+- If found in an uninstalled pack, 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` 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 should start a fresh Codex CLI session if the `$` skill list remains stale.
 - If found in an installed pack, suggest the same reload path to pick up the local skill roots.
 - If not found in any pack, suggest `/skills` or `/skills search <keyword>`.
 
@@ -50,7 +49,6 @@
 - If a user invokes a command-like skill such as `/benchmark-test-skill design-system` and the leading command is not in the injected session skill list, search project-local packs before falling back to the trailing argument as the active skill.
 - Check `packs/*/claude/<command>/SKILL.md` and pack metadata such as `packs/*/PACK.md`; project-local pack skills may exist in this repository even when they are not visible in the active session list.
 - In this repository, `/benchmark-test-skill` lives under `packs/agentic-skills-bench/claude/benchmark-test-skill/SKILL.md`, and `design-system` is its target skill argument.
-- For any other missing skill, run `scripts/pack.sh which <skill-name>` to locate the providing pack. If found in an uninstalled pack, use the same `/pack install <skill>` or `/pack install <pack>` recommendation and reload guidance above. If found in an installed pack, suggest the same reload path. If not found in any pack, suggest `/skills` or `/skills search <keyword>`.
 
 ### Prompt History
 - On every skill invocation, before substantive work, create `prompts/<skill-slug>/` if it does not exist.
@@ -84,7 +82,7 @@
 - **No Laziness**: Find root causes. No temporary fixes. Senior developer standards.
 - **Minimal Impact**: Changes should only touch what's necessary. Avoid introducing bugs.
 - **Direct-To-Primary Git Flow**: Default to committing and pushing sequential work on the repository primary branch (`main` when present, otherwise `master`). Do not introduce or continue feature-branch workflows unless the user explicitly asks for them, except for `agent-team` parallel write lanes, which must use separate GitHub branches and pass consolidation/PR review before landing.
-- **Always Ship Mutations**: If a task creates or modifies tracked files, finish by committing and pushing all intended changes before stopping unless the user explicitly says not to. Exception (Claude only): `/exec` hands a dirty tracked tree to `/ship`. After shipping, if `tasks/todo.md` has remaining steps, run `/ship` to handle planning and the approval cycle.
+- **Always Ship Mutations**: If a task creates or modifies tracked files, finish by committing and pushing all intended changes before stopping unless the user explicitly says not to. Do not leave a dirty tracked tree or unpushed commits behind.
 - **No GitHub Actions**: Do not create, modify, or suggest GitHub Actions workflows unless the user explicitly asks for GitHub Actions. This project does not use GitHub Actions for CI/CD by default.
 
 ## Windows/WSL File Opening
@@ -165,4 +163,4 @@ Research-producing skills maintain a shared project glossary at `research/glossa
 
 ### Cross-Pack Routing
 
-When a skill recommends another skill from a different pack, verify the target pack is installed via `.agents/project.json` `enabled_packs`. If not installed, include `/pack install <pack-name>` as a prerequisite in the recommendation.
+When a skill recommends another skill from a different pack, verify the target pack is installed via `.agents/project.json` `enabled_packs`. If not installed, include `npx skillpacks install <pack-name>` as the prerequisite in the recommendation.

package/README.md

@@ -1,19 +1,19 @@
-# Agentic Skills
+# gSkillPacks
 
 A shared skill library for Claude Code and OpenAI Codex.
 
 The library now uses a two-layer model:
 
-- **Global core skills** are domain-neutral and safe to expose in every project.
+- **Base skills** are domain-neutral and safe to expose in every project.
 - **Project-local packs** hold domain-specific workflows such as business apps, video games, and developer tools.
 
 This keeps game research out of B2B SaaS sessions, and keeps business-product assumptions out of game and devtool projects.
 
 ## Prerequisites
 
-- **Node.js 18+** for the `skillpacks` npm CLI and package build.
-- **bash** shell (macOS, Linux, or WSL on Windows) for `./init.sh`, `scripts/pack.sh`, and the remaining shell-backed `skillpacks` commands.
-- **jq** for git-checkout `scripts/pack.sh` write commands and `skillpacks install-deck` materialization: `brew install jq` (macOS) or `apt install jq` (Debian/Ubuntu). Node-owned `skillpacks` project commands do not require `jq`.
+- **Node.js 18+** for the `gskp` npm CLI and package build.
+- **bash** shell (macOS, Linux, or WSL on Windows) for `scripts/pack.sh` and the remaining shell-backed `gskp` commands.
+- **jq** for git-checkout `scripts/pack.sh` write commands and `gskp install-deck` materialization: `brew install jq` (macOS) or `apt install jq` (Debian/Ubuntu). Node-owned `gskp` project commands do not require `jq`.
 - **Claude Code** or **OpenAI Codex** installed on your machine
 - **pnpm** (optional, for running tests): `npm install -g pnpm`
 
@@ -27,11 +27,11 @@ The source-checkout path is available today and remains supported:
 
 ```bash
 git clone <this-repo-url> ~/agentic-skills
-cd ~/agentic-skills
-./init.sh
+cd ~/my-project
+npx skillpacks init
 ```
 
-Project-local packs are installed from the checkout:
+Base skills install **project-local** into the current repository (`.claude/skills/`, `.codex/skills/`). Project-local packs are installed from the checkout:
 
 ```bash
 cd ~/my-project
@@ -54,27 +54,28 @@ npx skillpacks refresh
 npx skillpacks status
 ```
 
-`npx skillpacks init` installs the base skills for the current repository as project-local roots. `npx skillpacks install <pack-or-skill>` adds domain packs or individual pack skills. Both write project-local files: `.agents/project.json`, `.claude/skills/*`, and `.codex/skills/*`. Package semver such as `skillpacks@0.1.0` selects the bundled skill snapshot; `npx skillpacks refresh` recreates enabled base skills and packs from that snapshot. Individual skill pins still use each skill's `version:` value through `skillpacks pin <skill> <version>`.
+`npx skillpacks init` installs the base skills for the current repository as project-local roots. `npx skillpacks install <pack-or-skill>` adds domain packs or individual pack skills. Both write project-local files: `.agents/project.json`, `.claude/skills/*`, and `.codex/skills/*`. Package semver such as `skillpacks@0.1.0` selects the bundled skill snapshot; `npx skillpacks refresh` recreates enabled base skills and packs from that snapshot. Individual skill pins still use each skill's `version:` value through `skillpacks pin <skill> <version>` or `gskp pin <skill> <version>`.
+
+The same release is also published as the scoped alias package `@glexcorp/gskp`, so `npx @glexcorp/gskp init` is equivalent to `npx skillpacks init` at the same version. Both packages install both `gskp` and `skillpacks` binaries for global or local `npm exec --package skillpacks ...` or `npm exec --package @glexcorp/gskp ...` usage. Do not use `npx skillpack ...` singular; that is an unrelated npm package with a different project format.
 
 ## Initialization
 
 ```bash
-./init.sh
+cd ~/my-project
+npx skillpacks init
 ```
 
-`init.sh` initializes only user-home global core skills:
-
-- `global/claude/*` -> `~/.claude/skills/*`
-- `global/codex/*` -> `~/.codex/skills/*`
+`npx skillpacks init` initializes base skills **project-local** for the current repository:
 
-It does **not** install `packs/*` globally.
+- `base/claude/*` -> `<project>/.claude/skills/*`
+- `base/codex/*` -> `<project>/.codex/skills/*`
 
-For npm consumers, prefer `npx skillpacks init` in each target repository. That installs the same base skill sources project-locally and records `base_skills: true` in `.agents/project.json`, so later `npx skillpacks refresh` updates them from the package version being run. Use `npx skillpacks init-global` only when you explicitly want user-home global installs.
+It records `base_skills: true` in `.agents/project.json`, so later `npx skillpacks refresh` updates them from the package version being run. It does **not** install `packs/*` — domain packs are never installed as base skills.
 
-To remove repo-managed global skill installs:
+There is no user-home (global) base install. To clean up legacy repo-managed base installs left in `~/.claude/skills` and `~/.codex/skills` by the retired init path:
 
 ```bash
-./init.sh --uninstall
+npx skillpacks uninstall-global
 ```
 
 ## Project Packs
@@ -82,37 +83,48 @@ To remove repo-managed global skill installs:
 Project packs are enabled per repository.
 
 ```bash
-scripts/pack.sh list
-scripts/pack.sh recommend
-scripts/pack.sh install business-discovery
-scripts/pack.sh install business-growth
-scripts/pack.sh install business-ops
-scripts/pack.sh install game
-scripts/pack.sh install devtool
-scripts/pack.sh install creator-foundation
-scripts/pack.sh install youtube-ops
-scripts/pack.sh install code-quality
-scripts/pack.sh install agentic-skills-bench
-scripts/pack.sh install monorepo
-scripts/pack.sh install remotion
-scripts/pack.sh install project-fleet
-scripts/pack.sh install alignment-loop
-scripts/pack.sh install design-system
-scripts/pack.sh which design-system
-scripts/pack.sh status
-scripts/pack.sh remove game
-scripts/pack.sh remove design-system
+npx skillpacks list
+npx skillpacks recommend
+npx skillpacks install business-discovery
+npx skillpacks install business-growth
+npx skillpacks install business-ops
+npx skillpacks install game
+npx skillpacks install devtool
+npx skillpacks install creator-foundation
+npx skillpacks install youtube-ops
+npx skillpacks install code-quality
+npx skillpacks install agentic-skills-bench
+npx skillpacks install monorepo
+npx skillpacks install remotion
+npx skillpacks install project-fleet
+npx skillpacks install alignment-loop
+npx skillpacks install design-system
+npx skillpacks which design-system
+npx skillpacks status
+npx skillpacks remove game
+npx skillpacks remove design-system
 ```
 
-`scripts/pack.sh install <name>` accepts either a pack name or a skill name from any pack. Pack names install every skill in the pack. Skill names install only that one project-local skill and record it under `.agents/project.json` `enabled_skills`.
+`npx skillpacks install <name>` accepts either a pack name or a skill name from any pack. Pack names install every skill in the pack. Skill names install only that one project-local skill and record it under `.agents/project.json` `enabled_skills`.
+
+For source-checkout development, `scripts/pack.sh install <pack-or-skill>` remains supported from a local clone. The npm CLI also supports `npx skillpacks refresh`, `npx skillpacks doctor`, `npx skillpacks doctor --fix`, `npx skillpacks doctor --fix --agent-docs --dry-run`, and deck installation from manifest metadata including `npx skillpacks install-deck vard`, `npx skillpacks install-deck ord`, `npx skillpacks install-deck business-afps`, `npx skillpacks install-deck devtool-afps`, and `npx skillpacks install-deck game-afps`.
+
+Alignment convention maintenance also has npm wrappers:
+
+```bash
+npx skillpacks alignment bundles --check
+npx skillpacks alignment pages audit
+npx skillpacks alignment pages inject-tts --force alignment/example.html
+npx skillpacks alignment verify
+```
 
-The npm CLI also supports equivalent project-local installs: `npx skillpacks install <pack-or-skill>`, `npx skillpacks remove <pack-or-skill>`, `npx skillpacks refresh`, `npx skillpacks doctor`, and deck installation from manifest metadata including `npx skillpacks install-deck vard`, `npx skillpacks install-deck ord`, `npx skillpacks install-deck business-afps`, `npx skillpacks install-deck devtool-afps`, and `npx skillpacks install-deck game-afps`.
+Use direct `node scripts/upgrade-alignment-page.mjs`, `node scripts/audit-alignment-pages.mjs`, and `node scripts/inject-tts.mjs` commands from a source checkout. Use `npx skillpacks alignment ...` from npm-installed target repos.
 
-`scripts/pack.sh list-packs` is an internal subcommand used by Codex `$exec` routing (see `global/codex/exec/SKILL.md`). It prints enabled packs from `.agents/project.json` one per line with no decoration, distinct from the human-facing `list` above; prefer `list` or `status` for interactive use.
+`scripts/pack.sh list-packs` is an internal subcommand used by Codex `$exec` routing (see `base/codex/exec/SKILL.md`). It prints enabled packs from `.agents/project.json` one per line with no decoration, distinct from the human-facing `list` above; prefer `list` or `status` for interactive use.
 
 Claude users can run `/pack` with no arguments, and Codex users can run `$pack` with no arguments. If `.agents/project.json` exists, the skill refreshes local skill roots from that committed project designation. If it is missing, the assistant inspects the repository, recommends a pack, and asks before installing.
 
-`scripts/pack.sh which <skill>` shows which pack provides a skill and whether it is installed. `scripts/pack.sh refresh` recreates local skill roots; it does not by itself force an active CLI skill registry to reload. Claude Code watches existing `.claude/skills` roots and supports `/reload-skills`; `/clear` starts a new empty-context conversation and can also pick up refreshed skills. Restart Claude Code if `.claude/skills` did not exist when the session started or the skill is still invisible. In Codex, start a fresh Codex CLI session if the `$` skill list stays stale.
+`npx skillpacks which <skill>` shows which pack provides a skill and whether it is installed. `npx skillpacks refresh` recreates local skill roots; it does not by itself force an active CLI skill registry to reload. Claude Code watches existing `.claude/skills` roots and supports `/reload-skills`; `/clear` starts a new empty-context conversation and can also pick up refreshed skills. Restart Claude Code if `.claude/skills` did not exist when the session started or the skill is still invisible. In Codex, start a fresh Codex CLI session if the `$` skill list stays stale.
 
 Pack installation creates local repo-managed skill roots in the current project. Active installs expose the canonical `SKILL.md` and exclude `archive/`:
 
@@ -157,13 +169,13 @@ For mixed monorepos, keep `project_type` as the default designation, set `enable
 }
 ```
 
-Git-checkout `scripts/pack.sh` commands preserve existing `project_scopes` and `notes` fields when `jq` is available. The npm `skillpacks` Node-owned commands preserve `project_scopes`, `notes`, `pinned_versions`, `enabled_skills`, `skill_updates`, and `agent_mode` without requiring `jq`.
+Git-checkout `scripts/pack.sh` commands preserve existing `project_scopes` and `notes` fields when `jq` is available. The npm `gskp` Node-owned commands preserve `project_scopes`, `notes`, `pinned_versions`, `enabled_skills`, `skill_updates`, and `agent_mode` without requiring `jq`.
 
 Pack commands also write `.agents/.pack.lock` owner metadata and automatically remove stale locks whose recorded process is no longer running.
 
 `.agents/project.json` also accepts an optional `agent_mode` field (`"claude-only" | "codex-only" | "hybrid"`) that names the Phase 11 operating mode for the project. Set or clear it with `scripts/pack.sh set-mode <claude-only|codex-only|hybrid|unset>`; the value is preserved across `install`, `remove`, and `refresh`. `SKILLS_AGENT_MODE` overrides the file for the current shell, and `scripts/agent-mode.sh` resolves the effective mode (env > project.json > empty). See `docs/operating-modes.md`.
 
-If an assistant does not discover project-local skills, use the global `pack` or `research-roadmap` skill as the launcher. The pack files still stay project-local.
+If an assistant does not discover project-local skills, use the base `pack` or `research-roadmap` skill as the launcher. The pack files still stay project-local.
 
 For workflow ordering, lead-in recommendations, and overlay dependencies, see [`docs/pack-workflow-matrix.md`](docs/pack-workflow-matrix.md).
 
@@ -171,7 +183,7 @@ For workflow ordering, lead-in recommendations, and overlay dependencies, see [`
 
 ```text
 agentic-skills/
-├── global/
+├── base/
 │   ├── claude/<name>/SKILL.md
 │   └── codex/<name>/SKILL.md
 ├── packs/
@@ -197,34 +209,34 @@ agentic-skills/
 │   └── skills-showcase/
 ├── packages/
 │   └── skillpacks/
-├── init.sh
 └── docs/
 ```
 
-The repository root is private workspace metadata. The publishable `skillpacks` package lives in `packages/skillpacks/`, while the public Skills Showcase app and its data generators live in `apps/skills-showcase/`.
+The repository root is private workspace metadata. The publishable `skillpacks` package source lives in `packages/skillpacks/`; `@glexcorp/gskp` is generated as a staged package variant during release. The public Skills Showcase app and its data generators live in `apps/skills-showcase/`.
 
-## Global Core
+## Base Core
 
-The global surface is intentionally small and domain-neutral. `./init.sh` installs six skills under `global/claude/` (mirrored under `global/codex/`):
+The base surface is intentionally small and domain-neutral. `npx skillpacks init` installs 11 skills under `base/claude/`, 8 of which are mirrored under `base/codex/`:
 
 ```text
-codebase-status, idea-scope-brief, init-agentic-skills, pack,
-provision-agentic-config, skills
+afps-status, animation-design-planner, autoresearch, autoresearch-prep,
+codebase-status, fork-idea-branch, idea-scope-brief, init-agentic-skills,
+pack, provision-agentic-config, skills
 ```
 
-### Codex-only global skill
+### Claude-only base skills
 
-One global skill ships only under `global/codex/` (no `global/claude/` mirror):
+Three base skills ship only under `base/claude/` (no `base/codex/` mirror):
 
 ```text
-afps-status
+autoresearch, autoresearch-prep, fork-idea-branch
 ```
 
 `$afps-status` summarizes AFPS product-workflow progress from existing artifacts and recommends the next concrete skill command. It is read-mostly reconciliation, not a competing workflow state system.
 
 ### `delegate` moved to the `agent-bridge` pack
 
-`delegate` is **no longer global** — it lives in `packs/agent-bridge/claude/delegate`. Install it with `scripts/pack.sh install agent-bridge`. It remains **Claude-only** with no Codex mirror.
+`delegate` is **no longer a base skill** — it lives in `packs/agent-bridge/claude/delegate`. Install it with `npx skillpacks install agent-bridge`. It remains **Claude-only** with no Codex mirror.
 
 `/delegate` is the synchronous, in-session sibling of `/handoff --target=codex`: it drafts and approves a packet via `scripts/approved-plan.sh`, then invokes `codex exec "<target-skill> --execute-approved"` live from Claude. It is `hybrid`-only by design. Codex users should not expect a `$delegate` — drive hybrid delegation from the Claude side, or use `/handoff --target=codex` for the async variant. See `packs/agent-bridge/claude/delegate/SKILL.md` and `docs/operating-modes.md`.
 
@@ -251,7 +263,7 @@ burn-rate, runway-model, investor-update, reconcile-research,
 mvp-gap, scale-audit, platform-strategy
 ```
 
-`scripts/pack.sh install business-app` remains a compatibility alias that installs all four, but narrow installs are preferred for context size.
+`npx skillpacks install business-app` remains a compatibility alias that installs all four, but narrow installs are preferred for context size.
 
 
 ### Game
@@ -295,7 +307,7 @@ youtube-portfolio, youtube-peer-benchmark, youtube-search-positioning,
 youtube-cadence-diagnosis
 ```
 
-`scripts/pack.sh install creator-media` remains a compatibility alias that installs `creator-foundation` and `youtube-ops`. Use `remotion` for `youtube-format-research`, `video-script`, and `video-build`.
+`npx skillpacks install creator-media` remains a compatibility alias that installs `creator-foundation` and `youtube-ops`. Use `remotion` for `youtube-format-research`, `video-script`, and `video-build`.
 
 LinkedIn-first evidence work uses the `creator-foundation` matrix/schema/dossier path:
 
@@ -352,7 +364,7 @@ extract-shared-types, quality-sweep
 For pnpm workspace monorepos that may use Turborepo and need package-aware execution, guardrails, and shipping.
 
 ```bash
-scripts/pack.sh install monorepo
+npx skillpacks install monorepo
 ```
 
 ```text
@@ -385,16 +397,16 @@ PoketoWork kanban packs are hibernated while Poketo.work is being rebuilt. Their
 
 ## Moved Skills
 
-Former global business/product skills now live in narrower project packs. `business-app` remains a compatibility alias for all four business packs.
+Former base business/product skills now live in narrower project packs. `business-app` remains a compatibility alias for all four business packs.
 
 ```bash
-scripts/pack.sh install business-discovery
-scripts/pack.sh install customer-lifecycle
-scripts/pack.sh install business-growth
-scripts/pack.sh install business-ops
+npx skillpacks install business-discovery
+npx skillpacks install customer-lifecycle
+npx skillpacks install business-growth
+npx skillpacks install business-ops
 ```
 
-Creator-media and YouTube work is similarly split between `creator-foundation`, `youtube-ops`, and `remotion`. Fleet/portfolio work moved from global core into `project-fleet`.
+Creator-media and YouTube work is similarly split between `creator-foundation`, `youtube-ops`, and `remotion`. Fleet/portfolio work moved from base core into `project-fleet`.
 
 ## Version Pinning
 
@@ -402,14 +414,14 @@ Skills can be pinned to an archived version. When a skill's version is bumped, t
 
 ```bash
 # Archive current version before bumping
-bash scripts/skill-archive.sh global/claude/ship
+bash scripts/skill-archive.sh base/claude/codebase-status
 
 # Pin a pack skill to an archived version
 scripts/pack.sh pin devtool-adoption v0.0
 scripts/pack.sh unpin devtool-adoption
 
-# Pin a global skill during initialization
-./init.sh --pin ship=v0.0
+# Pin a base skill to an archived version
+npx skillpacks pin ship v0.0
 
 # Audit archive integrity
 bash scripts/skill-archive-audit.sh
@@ -429,7 +441,7 @@ See [`docs/skill-versioning.md`](docs/skill-versioning.md) for the full versioni
 pnpm --dir tests test
 ```
 
-`skill-deps.sh`, `skill-pack-routing-audit.sh`, and `skill-versions.sh` scan `global/` and `packs/`; `skill-mirror-parity-audit.sh` checks mirrored pack skill pairs under `packs/`.
+`skill-deps.sh`, `skill-pack-routing-audit.sh`, and `skill-versions.sh` scan `base/` and `packs/`; `skill-mirror-parity-audit.sh` checks mirrored pack skill pairs under `packs/`.
 
 Live agent behavior tests are opt-in because they invoke authenticated CLIs and may spend model budget:
 

package/{global → base}/claude/afps-status/ALIGNMENT-PAGE.md

@@ -1,6 +1,6 @@
 # Alignment Page — afps-status
 
-When this skill produces durable deliverables (research, specs, plans, reports, prototypes, or any document output), build a full-depth HTML alignment page at `alignment/afps-status-{topic}.html`. Use a normalized topic slug derived from the app, feature, research subject, report subject, or output filename.
+Alignment pages are optional for this operational skill. By default, report the outcome inline and write only the skill's normal durable artifacts (`tasks/*.md`, reports, queues, benchmark notes, status docs, or other skill-specific files). Build `alignment/afps-status-{topic}.html` only when the user explicitly requests an alignment page or when the agent explicitly identifies a concrete clarification/review need that cannot be resolved cleanly in conversation or the normal artifacts. When an alignment page is created, use the full contract below and a normalized topic slug derived from the app, feature, research subject, report subject, or output filename.
 
 **Visual rendering tier.** Each alignment page declares a rendering tier:
 - `document` (default) — text, tables, approval gates. No charts or interactive elements.
@@ -57,7 +57,9 @@ The tier is set per skill via `visual_tier` in SKILL.md frontmatter (or detected
 
 **Report-only research gates.** For report-only or pre-approval research skills, the first `review` alignment page must explicitly contain proposed research scope, source plan, assumptions/confidence, recommended output path, proposed file changes, and approval gates before synthesized research begins and before any working packet, canonical research, spec, or task file is created or updated.
 
-**Staged research workflow.** Heavy report-first research uses a scope-first three-stage approval workflow. Stage 1 is minimal scope discovery only: inspect enough repository, user, and source context to propose research scope, source plan, assumptions, output paths, and approval questions. Build the `review` alignment page before synthesized research. The page must render the proposed scope, available source categories, known context, assumptions/confidence, proposed working-packet and canonical output paths, and research-scope approval gates. Stop for final compiled response YAML approval of the research scope. Do not synthesize findings, rank candidates, recommend a path, or create working packets, canonical research, spec, or task files in Stage 1. Stage 2 starts only after final compiled response YAML approves the research scope with no unresolved `needs-clarification`, unresolved `down` feedback, or other unresolved negative feedback. Perform the synthesized research, run required source/code checks, and write only a non-canonical working packet. Flat mode uses `research/_working/preliminary-afps-status-research.md`; product-path mode uses `research/{slug}/_working/preliminary-afps-status-research.md`. Existing raw evidence or search-log outputs may remain as supporting evidence when the skill contract already requires them, but synthesized deliverables stay in the working packet. Update the same `review` alignment page so it renders the full preliminary packet, evidence matrix, assumptions/confidence register, source coverage gaps, proposed canonical file changes, and artifact approval gates. Partial compiled responses revise the working packet and review page, then remain in Stage 2. Stage 3 consumes final compiled response YAML for artifact approval only when it has `approval_status: ready-for-agent-review` and no unresolved `needs-clarification`, unresolved `down` feedback, or other unresolved negative feedback. Apply approved edits first, archive the working packet to `docs/history/archive/YYYY-MM-DD/HHMMSS/<original-working-path>`, remove the active working packet, write the approved canonical artifacts to the unchanged output paths, and convert the page to `confirmed` with the approval record preserved.
+**Staged research workflow.** Heavy report-first research uses a scope-first three-stage approval workflow. Stage 1 is minimal scope discovery only: inspect enough repository, user, and source context to propose research scope, source plan, assumptions, output paths, and approval questions. Build the `review` alignment page before synthesized research. The page must render the proposed scope, available source categories, known context, assumptions/confidence, proposed working-packet and canonical output paths, research-scope approval gates, and a `Stage 2 Preview / Expected Review Format` section that shows the future Stage 2 review shape before research starts. Stop for final compiled response YAML approval of the research scope. Do not synthesize findings, rank candidates, recommend a path, or create working packets, canonical research, spec, or task files in Stage 1. Stage 2 starts only after final compiled response YAML approves the research scope with no unresolved `needs-clarification`, unresolved `down` feedback, or other unresolved negative feedback. Perform the synthesized research, run required source/code checks, and write only a non-canonical working packet. Flat mode uses `research/_working/preliminary-afps-status-research.md`; product-path mode uses `research/{slug}/_working/preliminary-afps-status-research.md`. Existing raw evidence or search-log outputs may remain as supporting evidence when the skill contract already requires them, but synthesized deliverables stay in the working packet. Update the same `review` alignment page so it renders the complete working-packet substance as structured HTML review UI: purpose-built sections, tables, matrices, gates, cards, and tier-appropriate charts or diagrams that preserve every packet section, finding, caveat, and decision detail without summary loss. Raw Markdown packet text may appear only as a supplemental source view after the rendered review UI; do not make a `Full Preliminary Packet` or `Full Working Packet` raw Markdown dump, giant `<pre><code>` block, link-only view, or source-only view the primary review surface. Include the evidence matrix, assumptions/confidence register, source coverage gaps, proposed canonical file changes, and artifact approval gates. Partial compiled responses revise the working packet and review page, then remain in Stage 2. Stage 3 consumes final compiled response YAML for artifact approval only when it has `approval_status: ready-for-agent-review` and no unresolved `needs-clarification`, unresolved `down` feedback, or other unresolved negative feedback. Apply approved edits first, archive the working packet to `docs/history/archive/YYYY-MM-DD/HHMMSS/<original-working-path>`, remove the active working packet, write the approved canonical artifacts to the unchanged output paths, and convert the page to `confirmed` with the approval record preserved.
+
+**Stage 2 review-page template.** Stage 1 scope-review pages must include a `Stage 2 Preview / Expected Review Format` section that previews the exact section sequence, table shapes, evidence treatment, visual density, and approval gates the user will see after research; make it specific enough for the user to flag preferred content formats, grouping, labels, visuals, and evidence density before the agent does heavy research. After scope approval and research, the Stage 2 review page must include these sections as structured HTML, not as raw Markdown dumps: `Research Scope Approved` status block with approved scope, source plan, output paths, and unresolved caveats; `Executive Findings` or a skill-specific top-findings section with confidence labels; `Evidence Matrix` mapping claim, evidence/source/path, inference, confidence, assumptions, and decision impact; `Working Packet Review` with the complete working-packet substance rendered as purpose-built HTML sections, lists, tables, matrices, cards, and tier-appropriate charts or diagrams; `Alternatives / Rejected or Lower-Confidence Findings`; `Source Coverage & Gaps`; `Assumptions / Confidence Register`; `Proposed Canonical Artifacts & File Changes`; a required `User Format Preferences` gate asking whether the layout, tables, grouping, visuals, labels, and evidence density match expectations; and a required `Final Artifact Approval` gate for Stage 3 readiness. Raw Markdown packet text, search logs, or source notes may appear only as supplemental source views after the rendered review UI and never replace the Stage 2 review sections.
 
 **Glossary Additions gate.** When this research introduces domain-specific terms, acronyms, or concept definitions that a reader outside the project would not know, include a `## Glossary Additions` section in the alignment page. Render a table of proposed terms with columns: Term, Definition, Source (`afps-status`), Category (business/tooling/workflow/technical/domain), and per-term Approve/Edit/Reject/Flag radio controls. Only user-approved terms are appended to the target glossary (`research/glossary.md` or `research/{slug}/glossary.md` for scoped paths) during the confirmed-page write step. When the skill operates in a product-path scope, ask whether each term belongs in the parent or scoped glossary; default to the scoped glossary.
 

package/{global → base}/claude/afps-status/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## v0.4 - 2026-06-12
+
+- Made alignment pages optional by default: report inline and write the skill's normal durable artifacts unless the user requests an alignment page or the agent identifies a concrete clarification/review need.
+
+## v0.3 - 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.
+
 ## v0.2 - 2026-06-11
 
 - Added npm-aware install-route alternatives to AFPS pack fallback recommendations while preserving Claude `/pack install` routes.

package/base/claude/afps-status/SKILL.md

@@ -0,0 +1,110 @@
+---
+name: afps-status
+description: Summarize AFPS product-workflow progress from existing artifacts and recommend the next concrete skill command
+type: analysis
+version: v0.4
+argument-hint: "[optional project path, product path, or focus]"
+---
+
+# AFPS Status
+
+Invoke as `/afps-status`.
+
+Use this skill when the user asks where a product project is in the AFPS workflow, what research/planning/implementation artifact is missing next, whether task docs match product evidence, or which AFPS command should run next.
+
+AFPS here means the product workflow from raw idea through concept scoping, customer discovery/research, lifecycle/growth planning, specs, roadmap/phase work, implementation, validation, and shipping. This is read-mostly reconciliation. It summarizes existing artifacts and recommends a route; it does not create a competing workflow state system.
+
+## Process
+
+1. Resolve target project:
+   - Default to the current working directory.
+   - If `$ARGUMENTS` names a path, inspect that project.
+   - If `$ARGUMENTS` names a product path, app, customer, audience, or focus, prioritize matching artifacts under `research/`, `specs/`, `tasks/`, and `alignment/`.
+   - Confirm whether the target is a git worktree when possible. Continue with filesystem evidence if git is unavailable.
+2. Read project orientation:
+   - `.agents/project.json`
+   - `README.md`, `AGENTS.md`, `CLAUDE.md`
+   - package/workspace manifests and obvious app entrypoints when needed to understand whether implementation exists.
+   - Use `scripts/pack.sh list-packs` when available to determine enabled packs; do not grep `.agents/project.json` directly when choosing installed-pack routes.
+3. Inspect AFPS evidence from existing artifacts:
+   - Product-path state: `research/.progress.yaml`, including legacy `active_path` normalized mentally to `active_paths`.
+   - Concept artifacts: `research/idea-brief*.md`, app-scoped `research/*/idea-brief*.md`, and concept/interview notes.
+   - Discovery artifacts: customer-discovery docs such as `research/icp.md`, competitive analysis, customer feedback, journey/lifecycle maps, value-prop canvas, positioning, lean canvas, market evidence, and assumption/risk trackers.
+   - Lifecycle/growth artifacts: onboarding, activation, retention, conversion, monetization, GTM, growth model, metrics, PMF, and experiment docs.
+   - Product/spec artifacts: `specs/`, `spec.md`, app/feature specs, UX/UI/prototype/UAT/consolidation notes, and alignment pages under `alignment/`.
+   - Execution artifacts: `tasks/roadmap.md`, `tasks/todo.md`, `tasks/manual-todo.md`, `tasks/record-todo.md`, `tasks/recurring-todo.md`, `tasks/history.md`, `tasks/phases/`, and recent validation notes.
+   - Rapid pipeline artifacts: `research/vard-ship-log.md` (VARD experiments), `research/ord-ship-log.md` (ORD packages), and `alignment/vard-*.md` or `alignment/ord-*.md` alignment docs.
+   - Git evidence: `git status --short`, current branch/upstream, last relevant commits, unpushed commits, and changed files.
+4. Reconcile evidence instead of trusting one file:
+   - Distinguish missing artifacts, stale artifacts, contradictory artifacts, completed work, active implementation tasks, manual blockers, unvalidated implementation, and unshipped local changes.
+   - Treat `research/.progress.yaml` as a manifest of product/app/customer focus, not as the source of truth over concrete artifacts.
+   - If product-path manifest entries are missing or stale, report the exact proposed update in prose. Do not write `research/.progress.yaml` unless the user explicitly asks for mutation.
+   - If task docs contradict research/spec/code/git evidence, call out the contradiction and route to reconciliation rather than choosing whichever artifact is newest.
+5. Detect rapid pipeline activity:
+   - If `research/vard-ship-log.md` exists, report VARD pipeline status: number of experiments shipped, most recent entry, and whether any show traction signals warranting graduation to Business AFPS.
+   - If `research/ord-ship-log.md` exists, report ORD pipeline status: number of packages published, most recent entry, and whether any show traction signals warranting graduation to Devtool AFPS.
+   - If `vard` or `ord` packs are enabled, note the active rapid pipeline alongside deliberate pipeline status.
+6. Classify AFPS stage:
+   - `unscoped`: no concept brief or the concept is too unclear for customer discovery.
+   - `concept-ready`: concept exists but discovery pack/skills are not enabled.
+   - `discovery-needed`: concept exists and discovery skills are enabled, but customer discovery is absent or not specific enough.
+   - `research-incomplete`: customer discovery exists but market, competitive, value, positioning, journey, or lifecycle evidence is missing.
+   - `lifecycle-gap`: discovery exists but onboarding, conversion, activation, retention, monetization, GTM, or metrics questions block spec quality.
+   - `spec-needed`: research is sufficient but durable product/spec artifacts are absent or stale.
+   - `roadmap-needed`: research/spec artifacts exist but `tasks/roadmap.md` or `tasks/todo.md` is missing, stale, contradictory, or not actionable.
+   - `execution-ready`: a clear unchecked implementation task exists with no blocking manual task.
+   - `ship-needed`: implementation changes are present, completed, or unpushed but validation, task review, commit, push, or deploy packaging is pending.
+   - `reconcile-needed`: artifacts conflict enough that the next step should be reconciliation before new research or implementation.
+6. Choose the next route with these rules:
+   - No concept brief or unclear concept: `/idea-scope-brief`
+   - Concept exists but business discovery is missing: `npx skillpacks install business-discovery` from the project shell.
+   - Concept exists and discovery is enabled, but no customer-discovery evidence: `/customer-discovery`
+   - Customer discovery exists but market/value evidence is missing: the most specific discovery command, usually `/competitive-analysis`, `/value-prop-canvas`, or `/positioning`
+   - Journey/lifecycle/growth questions are missing after discovery: recommend the relevant installed command, or install the required pack first, such as `npx skillpacks install customer-lifecycle` from the project shell, or `npx skillpacks install business-growth` from the project shell.
+   - Research/specs exist but task queue is stale or absent: `/roadmap`
+   - Clear executable task exists: `/exec`
+   - Implementation is done but unvalidated, dirty, uncommitted, unpushed, or otherwise unshipped: `/ship`
+   - Contradictory research/spec/task evidence: `/reconcile-research` when business-ops is enabled, `/spec-drift` when agent-work-admin is enabled, otherwise `/codebase-status` with a focused prompt naming the contradiction.
+7. Validate command availability before recommending pack-local routes:
+   - Use `scripts/pack.sh list-packs` when present to detect enabled packs.
+   - If the best command lives in an uninstalled pack, recommend the package install command instead of the unavailable command: `npx skillpacks install <pack>` from the project shell.
+   - If `scripts/pack.sh` is missing or pack lookup fails, silently fall back to the global/default route and mention the degraded lookup only if it changes confidence.
+
+## Output
+
+Produce a concise structured report with:
+
+- **Overview:** repo path, product/app focus, git status, enabled packs, active rapid pipelines (VARD/ORD), and whether AFPS evidence is single-path or multi-path.
+- **Rapid Pipeline Status** (if applicable): VARD and/or ORD experiment counts, latest shipment, traction signals, and graduation readiness.
+- **Artifact Map:** concept, customer discovery/research, lifecycle/growth, specs/prototypes/UAT, tasks, alignment pages, and shipping evidence with present/missing/stale status.
+- **AFPS Stage:** one stage label from the workflow above, with confidence and evidence.
+- **Contradictions And Gaps:** conflicting artifacts, missing product-path manifest updates, stale task queues, manual blockers, validation/shipping gaps, and uncertainty.
+- **Recommended Route:** the next concrete work item and why it is the narrowest route.
+
+End with exactly:
+
+```md
+**Next work:** <specific AFPS step or blocker>
+**Recommended next command:** <one command or route>
+```
+
+## Constraints
+
+- Read-only by default. Do not modify workflow state, task docs, research docs, specs, or git state unless the user explicitly asks for mutation.
+- Do not create a new AFPS state file or schema. Use existing artifacts, especially `research/.progress.yaml`, `research/`, `specs/`, `tasks/`, `alignment/`, and git.
+- Propose missing `research/.progress.yaml` updates in the report instead of writing them by default.
+- Do not run expensive tests, installs, web research, deploys, or external-account actions during status synthesis.
+- Do not treat `tasks/record-todo.md` or `tasks/recurring-todo.md` as execution queues unless an item has clearly been promoted into `tasks/todo.md`.
+- Do not route agent-executable repo work to `/guide`; reserve guided/manual routes for human-only blockers.
+- Do not create or modify GitHub Actions workflows.
+
+## Alignment Page
+
+By default, this skill reports results inline and writes only its normal durable artifacts (for example `tasks/*.md`, reports, queues, benchmark notes, status docs, or other skill-specific files). Do not build an alignment page automatically. Create `alignment/afps-status-{topic}.html` only when the user explicitly requests an alignment page or when you explicitly identify a concrete clarification/review need that cannot be handled cleanly inline; when you create one, follow `ALIGNMENT-PAGE.md` in this skill's directory.
+
+## Default Shipping Contract
+
+- **Default next-step routing:** when reporting completion, include the two-line pair `**Next work:** <specific task or "none">` and `**Recommended next command:** <one command or route>` so the next caller has a concrete handoff.
+- Normally read-only and should not create or modify tracked repository files.
+- If the user explicitly asks this skill to create or modify tracked files, finish by committing and pushing all intended changes to the repository primary branch (`main` when present, otherwise `master`) before stopping.
+- This contract does not override stricter safety rules about secrets, destructive history changes, release publication/tag confirmation, production deploy confirmation, paid actions, or public visibility changes.