skillpacks 0.1.0 → 0.1.1

package/global/claude/provision-agentic-config/archive/v0.5/SKILL.md

@@ -0,0 +1,292 @@
+---
+name: provision-agentic-config
+description: Provision workflow orchestration and agent conventions into project CLAUDE.md and AGENTS.md
+type: ops
+version: v0.5
+argument-hint:
+---
+
+# Install Workflow Orchestration
+
+Create or update the current repository's `CLAUDE.md` and `AGENTS.md` with workflow orchestration conventions.
+
+## Process
+
+1. **Check target files:**
+   - Ensure `./CLAUDE.md` exists. If not, create it.
+   - Ensure `./AGENTS.md` exists. If not, create it.
+
+2. **Insert the orchestration blocks:**
+   - Insert the Claude block below verbatim into `./CLAUDE.md`.
+   - Insert the AGENTS block below verbatim into `./AGENTS.md`.
+   - If the corresponding block already exists anywhere in either target file, replace it so it appears exactly once per file.
+   - Preserve any other existing content in `./CLAUDE.md` and `./AGENTS.md`.
+   - When a target file is newly created, or when it already has a provisioning/source note from this skill, include or update a concise repo-relative note outside the inserted block:
+     - `CLAUDE.md`: `Provisioned artifact: ./CLAUDE.md. Source: workflow.md. Verification: block appears exactly once.`
+     - `AGENTS.md`: `Provisioned artifact: ./AGENTS.md. Source: workflow.md. Verification: block appears exactly once.`
+     - If `workflow.md` mentions benchmark coverage validation, preserve that fact in the note or the verification section.
+     - Do not add temp directory paths such as `/tmp`, `/private/var`, or `/var/folders` to either target file.
+   - Each block begins with `<!-- provision-agentic-config v0.5 -->`. When replacing an existing block, update this comment to the current version. The `/sync` skill uses this comment to detect stale provisioning.
+
+   The Claude block to insert into `./CLAUDE.md`:
+
+   ````markdown
+   <!-- provision-agentic-config v0.5 -->
+   ## 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
+   - 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
+   - Do not assume a Claude-style clear-context-on-accept flow or related JSON setting exists
+
+   ### 2. Subagent Strategy
+   - Use subagents liberally to keep main context window clean
+   - Offload research, exploration, and parallel analysis to subagents
+   - For complex problems, throw more compute at it via subagents
+   - One task per subagent for focused execution
+   - For `agent-team` parallel write lanes, require separate GitHub branches per lane and include a consolidation/PR review step before final integration. This is the explicit exception to direct-to-primary work.
+
+   ### 3. Self-Improvement Loop
+   - 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
+   - Review lessons at session start for relevant project
+
+   ### 4. Verification Before Done
+   - Never mark a task complete without proving it works
+   - Diff your behavior between main and your changes when relevant
+   - Ask yourself: "Would a staff engineer approve this?"
+   - Run tests, check logs, demonstrate correctness
+
+   ### 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
+   - 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
+   - 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>`.
+
+   ### Prompt History
+   - On every skill invocation, before substantive work, create `prompts/<skill-slug>/` if it does not exist.
+   - Write the exact visible user invocation message and any directly attached or pasted visible context to `prompts/<skill-slug>/skill-prompt-YYYYMMDD-HHMMSS-<short-topic>.md`.
+   - Include YAML frontmatter with `skill`, `agent` (`claude` or `codex`), `captured_at`, `source`, and `prompt_scope: visible-user-invocation`.
+   - Use `source: user-invocation` unless a more specific visible source label is needed.
+   - Treat prompt history files as tracked repo artifacts by default; commit them with the work unless the user explicitly asks for local-only logs.
+   - Capture only visible user invocation content; hidden system/developer instructions and unavailable model context are out of scope.
+   - Do not summarize, redact, or truncate the prompt log. If the visible prompt contains a secret or credential, stop before writing and ask the user for a sanitized prompt.
+
+   ## Task Management
+
+   1. **Plan First**: Write plan to `tasks/roadmap.md` (full plan) and `tasks/todo.md` (current phase) with checkable items
+   2. **Verify Plan**: Check in before starting implementation
+   3. **Track Progress**: Mark items complete as you go
+   4. **Explain Changes**: High-level summary at each step
+   5. **Document Results**: Add review section to `tasks/todo.md`
+   6. **Capture Lessons**: Update `tasks/lessons.md` after corrections
+
+   ## Core Principles
+   - **Simplicity First**: Make every change as simple as possible. Impact minimal code.
+   - **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.
+   - **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
+   - On Windows machines running WSL, convert Linux paths before opening files from shell commands:
+
+   ```bash
+   WIN_PATH=$(wslpath -w "$FILE_PATH")
+   cmd.exe /c start "" "$WIN_PATH"
+   ```
+
+   - For HTML files that should open in the Windows browser, prefer a WSL file URI through the Windows PowerShell binary when `cmd.exe /c start` or UNC paths fail:
+
+   ```bash
+   DISTRO=${WSL_DISTRO_NAME:-Ubuntu}
+   URI="file://wsl.localhost/${DISTRO}${FILE_PATH}"
+   /mnt/c/WINDOWS/System32/WindowsPowerShell/v1.0/powershell.exe -NoProfile -Command "Start-Process '$URI'"
+   ```
+
+   - Use WSL detection so this path only runs inside WSL:
+
+   ```bash
+   if grep -qi microsoft /proc/version 2>/dev/null; then
+     cmd.exe /c start "" "$(wslpath -w "$FILE_PATH")"
+   fi
+   ```
+
+   - The `cmd.exe` UNC warning (`UNC paths are not supported. Defaulting to Windows directory.`) is cosmetic; the file still opens correctly.
+   - The `UtilBindVsockAnyPort: socket failed 1` failure can happen before Windows opens a UNC path. For browser-targeted HTML pages, retry with the `file://wsl.localhost/<distro>/...` PowerShell URI before using editor fallbacks.
+   ````
+
+   The AGENTS block to insert into `./AGENTS.md`:
+
+   ````markdown
+   <!-- provision-agentic-config v0.5 -->
+   ## 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
+   - 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
+   - Do not assume a Claude-style clear-context-on-accept flow or related JSON setting exists
+
+   ### 2. Subagent Strategy
+   - Use subagents only when the active Codex tool instructions allow them.
+   - When subagents are available and permitted, delegate independent research, exploration, or execution lanes with non-overlapping scopes.
+   - One task per subagent for focused execution.
+   - Do not override Codex's current subagent permission, tool availability, or parallel-work rules.
+   - For `agent-team` parallel write lanes, require separate GitHub branches per lane and include a consolidation/PR review step before final integration. This is the explicit exception to direct-to-primary work.
+
+   ### 3. Self-Improvement Loop
+   - 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
+   - Review lessons at session start for relevant project
+
+   ### 4. Verification Before Done
+   - Never mark a task complete without proving it works
+   - Diff your behavior between main and your changes when relevant
+   - Ask yourself: "Would a staff engineer approve this?"
+   - Run tests, check logs, demonstrate correctness
+
+   ### 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
+   - 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
+   - 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>`.
+
+   ### Prompt History
+   - On every skill invocation, before substantive work, create `prompts/<skill-slug>/` if it does not exist.
+   - Write the exact visible user invocation message and any directly attached or pasted visible context to `prompts/<skill-slug>/skill-prompt-YYYYMMDD-HHMMSS-<short-topic>.md`.
+   - Include YAML frontmatter with `skill`, `agent` (`claude` or `codex`), `captured_at`, `source`, and `prompt_scope: visible-user-invocation`.
+   - Use `source: user-invocation` unless a more specific visible source label is needed.
+   - Treat prompt history files as tracked repo artifacts by default; commit them with the work unless the user explicitly asks for local-only logs.
+   - Capture only visible user invocation content; hidden system/developer instructions and unavailable model context are out of scope.
+   - Do not summarize, redact, or truncate the prompt log. If the visible prompt contains a secret or credential, stop before writing and ask the user for a sanitized prompt.
+
+   ## Task Management
+
+   1. **Plan First**: Write plan to `tasks/roadmap.md` (full plan) and `tasks/todo.md` (current phase) with checkable items
+   2. **Verify Plan**: Check in before starting implementation
+   3. **Track Progress**: Mark items complete as you go
+   4. **Explain Changes**: High-level summary at each step
+   5. **Document Results**: Add review section to `tasks/todo.md`
+   6. **Capture Lessons**: Update `tasks/lessons.md` after corrections
+
+   ## Core Principles
+   - **Simplicity First**: Make every change as simple as possible. Impact minimal code.
+   - **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.
+   - **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
+   - On Windows machines running WSL, convert Linux paths before opening files from shell commands:
+
+   ```bash
+   WIN_PATH=$(wslpath -w "$FILE_PATH")
+   cmd.exe /c start "" "$WIN_PATH"
+   ```
+
+   - For HTML files that should open in the Windows browser, prefer a WSL file URI through the Windows PowerShell binary when `cmd.exe /c start` or UNC paths fail:
+
+   ```bash
+   DISTRO=${WSL_DISTRO_NAME:-Ubuntu}
+   URI="file://wsl.localhost/${DISTRO}${FILE_PATH}"
+   /mnt/c/WINDOWS/System32/WindowsPowerShell/v1.0/powershell.exe -NoProfile -Command "Start-Process '$URI'"
+   ```
+
+   - Use WSL detection so this path only runs inside WSL:
+
+   ```bash
+   if grep -qi microsoft /proc/version 2>/dev/null; then
+     cmd.exe /c start "" "$(wslpath -w "$FILE_PATH")"
+   fi
+   ```
+
+   - The `cmd.exe` UNC warning (`UNC paths are not supported. Defaulting to Windows directory.`) is cosmetic; the file still opens correctly.
+   - The `UtilBindVsockAnyPort: socket failed 1` failure can happen before Windows opens a UNC path. For browser-targeted HTML pages, retry with the `file://wsl.localhost/<distro>/...` PowerShell URI before using editor fallbacks.
+   ````
+
+3. **Conditionally add Monorepo Parallel-Work Safety:**
+
+   Detect whether the target repo is a monorepo by checking these heuristics (any match = monorepo):
+   1. `pnpm-workspace.yaml` exists at repo root
+   2. `package.json` at repo root has a `workspaces` field
+   3. `lerna.json` exists at repo root
+   4. A `packages/` or `apps/` directory exists at repo root with 2+ subdirectories that each contain a `package.json`
+
+   **If monorepo detected:** append the following section after `### 6. Autonomous Bug Fixing` and before `## Task Management` in both target files:
+
+   ```markdown
+   ### 7. Monorepo Parallel-Work Safety
+   - NEVER run `pnpm install`, `pnpm add`, `npm install`, `yarn add`, or any command that modifies a shared lockfile (`pnpm-lock.yaml`, `package-lock.json`, `yarn.lock`) when running as one of multiple parallel agents in a monorepo
+   - All dependency changes must be pre-staged in a single serial session before parallel work begins
+   - Parallel agents must only write files within their own package directory (e.g. `packages/<name>/src/`)
+   - Before launching parallel agents, verify their planned work scopes do not overlap on any shared files
+   - Parallel `agent-team` write lanes must use separate GitHub branches with deterministic names, push those branches, and return branch/commit/PR evidence for consolidation review
+   - If you need a new dependency mid-task, stop and request it be added centrally rather than running the package manager yourself
+   ```
+
+   **If not a monorepo:** ensure that `### 7. Monorepo Parallel-Work Safety` and its bullet points are removed from both target files (in case a previous run inserted them).
+
+4. **Report result:**
+   - Print whether each target file was created or modified, using repo-relative paths exactly like `./CLAUDE.md` and `./AGENTS.md`.
+   - Print where the block was inserted in each file (top/bottom/after which heading).
+   - Print whether the monorepo block was included or skipped (and which heuristic matched, if any).
+   - Confirm that the final block appears exactly once in each target file.
+   - Print the source/verification note status for each target file when a note was written or updated.
+   - Never present benchmark harness temp paths such as `/tmp`, `/private/var`, or `/var/folders` as the user-facing artifact location; convert them to repo-relative target paths.
+
+## Output
+
+Display confirmation directly to the user (the block itself is written to `./CLAUDE.md` and `./AGENTS.md`):
+
+```
+Installed workflow orchestration into ./CLAUDE.md and ./AGENTS.md
+- ./CLAUDE.md: [created | updated], [top | bottom | after "<heading>"], block appears once
+- ./AGENTS.md: [created | updated], [top | bottom | after "<heading>"], block appears once
+- Monorepo safety block: [included (matched: <heuristic>) | skipped (not a monorepo)]
+- Source/verification notes: [written | updated | preserved | skipped because existing unrelated content should not be changed]
+```
+
+## Constraints
+
+- Insert the block exactly once per target file — if it already exists, replace rather than duplicate.
+- Preserve all other existing content in `./CLAUDE.md` and `./AGENTS.md`.
+- Do not modify any file other than `./CLAUDE.md` and `./AGENTS.md`.
+
+
+## Default Shipping Contract
+
+Follow the shared shipping contract convention in CLAUDE.md.

package/global/claude/skills/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog
 
+## v0.6 - 2026-06-11
+
+- Added npm-aware install-route alternatives to available-but-not-installed skill guidance while preserving Claude `/pack install` routes.
+
 ## v0.5
 
 - Updated the Discovery & Market Fit catalog examples to list `customer-discovery` as the standard business-discovery route while preserving `enterprise-icp`.

package/global/claude/skills/SKILL.md

@@ -2,7 +2,7 @@
 name: skills
 description: Browse and search all available skills, grouped by workflow stage or activity type
 type: ops
-version: v0.5
+version: v0.6
 argument-hint: "[list | types | search <keyword>]"
 ---
 
@@ -35,7 +35,7 @@ Discover and search installed global skills plus enabled project-local pack skil
 
    | Stage | Skills (pack in parentheses; no label = global) |
    |-------|--------|
-   | Pack Management | `pack`, `pack list`, `pack status`, `pack recommend`, `pack install <pack-or-skill>`, `pack remove <pack-or-skill>`, `pack which <skill>` |
+   | Pack Management | `pack`, `pack list`, `pack status`, `pack recommend`, `pack 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) |
@@ -84,7 +84,7 @@ Discover and search installed global skills plus enabled project-local pack skil
    - Under each heading, list installed/global 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 \`/pack install <skill>\` or \`/pack install <pack>\``.
+   - For available-but-not-installed pack skills, list as `/<name> — <description>  [type]  ⚠ requires \`/pack install <skill>\` or \`/pack 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>"`).
 

package/global/claude/skills/archive/v0.5/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.5
+argument-hint: "[list | types | search <keyword>]"
+---
+
+# Skills
+
+Discover and search installed global 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 global Claude skills in `global/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 global 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 = global) |
+   |-------|--------|
+   | Pack Management | `pack`, `pack list`, `pack status`, `pack recommend`, `pack 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/global 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 \`/pack install <skill>\` or \`/pack install <pack>\``.
+   - 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/codex/afps-status/ALIGNMENT-PAGE.md

@@ -9,7 +9,7 @@ When this skill produces durable deliverables (research, specs, plans, reports,
 
 The tier is set per skill via `visual_tier` in SKILL.md frontmatter (or detected by the upgrade script). The bundled ALIGNMENT-PAGE.md receives tier-appropriate rendering guidance from the generator.
 
-**Alignment lifecycle.** Alignment pages have three lifecycle states. `review` is the draft/pre-approval page: it contains the complete deliverable preview, evidence, required inline gate questions, section feedback controls, feedback-only YAML, and final compile controls. `confirmed` is the post-approval page after the agent has consumed final compiled YAML, made any approved user-requested edits, and written or updated the approved canonical artifacts. A confirmed page is finished and current for the completed alignment cycle, but it remains amendable when later research changes or extends the conclusions. `amended` is a future revision of a confirmed page: archive the previous confirmed page first, mark what changed, preserve the prior approval record, and highlight the new evidence, decisions, or scope that changed the earlier conclusion.
+**Alignment lifecycle.** Alignment pages have three lifecycle states. `review` is the draft/pre-approval page: it contains the complete deliverable preview, evidence, required inline gate questions, section feedback controls, local section-feedback YAML only after a section feedback choice is selected, and one bottom `Compile Responses` control. `confirmed` is the post-approval page after the agent has consumed final compiled response YAML, made any approved user-requested edits, and written or updated the approved canonical artifacts. A confirmed page is finished and current for the completed alignment cycle, but it remains amendable when later research changes or extends the conclusions. `amended` is a future revision of a confirmed page: archive the previous confirmed page first, mark what changed, preserve the prior approval record, and highlight the new evidence, decisions, or scope that changed the earlier conclusion.
 
 **Central alignment index.** When a research-producing skill writes or updates an HTML alignment page, also maintain the repository's central alignment index. Look for `alignment/index.html` at the repository root; if the target repo documents a different central alignment-index path, use that path and report it. If the index does not exist, create it as a self-contained HTML page that works from `file://`, links to every active `alignment/*.html` page except itself, and includes the newly written page. Every index entry must include the page's alignment date in a muted meta span after the link, formatted `YYYY-MM-DD`, for example `<a href="page.html">Title</a> <span class="meta">2026-06-09</span>`. The alignment date is the review or confirmed date written inside the page itself; new pages use today's date. If the index exists, update it instead of blindly appending: preserve valid existing entries, metadata, and entry dates; remove duplicate entries for the same page path; keep links repo-relative; and include the new or updated page. When updating an existing index, add a date only to entries that are missing one, deriving it from the page's internal alignment date, or from file history when the page has no internal date. If a `new` marker is used, combine it with the date as `<span class="meta">new · YYYY-MM-DD</span>`, and remove stale `new` markers from entries that are no longer the latest addition.
 
@@ -29,7 +29,7 @@ The tier is set per skill via `visual_tier` in SKILL.md frontmatter (or detected
 
 **Category and product-path grouping.** In product-line or product-path repositories, identify product from `research/.progress.yaml` `product_paths[]`, active `research/{slug}/` or `specs/{slug}/` scopes, page metadata, page title, or the alignment page path. Group index entries by category first, then by product/product path within each category, with the repo's existing secondary sort preserved when clear. In flat repositories, group by category, then preserve the existing index organization within each category or use a clear newest-first or title order when creating a new index.
 
-**Research quality contract.** For research-producing outputs, do not synthesize research findings, recommendations, candidate rankings, or working packets until the user approves the research scope from the `review` alignment page's final compiled YAML. Before scope approval, do only minimal discovery needed to propose the research scope, source plan, assumptions, output paths, and approval questions; label any observed files or source availability as scope evidence, not findings. After scope approval, perform the synthesized research and separate and label `claims` (what the report concludes), `evidence` (source, repo artifact or file path, quote or observation, date, and confidence), `inference` (why that evidence supports the claim), `assumptions` (what remains unproven), and `decision impact` (what the user should approve, reject, or correct). Do not collapse evidence and inference into unsupported summary prose.
+**Research quality contract.** For research-producing outputs, do not synthesize research findings, recommendations, candidate rankings, or working packets until the user approves the research scope from the `review` alignment page's final compiled response YAML. Before scope approval, do only minimal discovery needed to propose the research scope, source plan, assumptions, output paths, and approval questions; label any observed files or source availability as scope evidence, not findings. After scope approval, perform the synthesized research and separate and label `claims` (what the report concludes), `evidence` (source, repo artifact or file path, quote or observation, date, and confidence), `inference` (why that evidence supports the claim), `assumptions` (what remains unproven), and `decision impact` (what the user should approve, reject, or correct). Do not collapse evidence and inference into unsupported summary prose.
 
 **Embed prohibition.** Do not use `<object>`, `<iframe>`, `<embed>`, or "open working packet" / "view full document" links as the primary rendering of any proposed deliverable, evidence matrix, interview log, or manifest entry. The alignment page HTML must contain the rendered content directly. Embedded or linked external documents are permitted only as supplemental references alongside the fully rendered content already present in the page. **Exception:** Self-contained inline `<canvas>` and `<svg>` elements are permitted for charts and diagrams within the same HTML file.
 
@@ -57,30 +57,30 @@ 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 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 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. Feedback-only YAML revises the working packet and review page, then remains in Stage 2. Stage 3 consumes final compiled YAML for artifact approval only when it has 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, 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.
 
 **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.
 
 **Required inline questions.** In `review` pages, each gate must contain at least one required inline question placed directly under the content it governs, inside a visually distinct question block. Each question must use radio-button inputs and include two standing options after the skill-generated choices: "Other / None of the above" backed by a multi-line text box for free-form input, and "Need clarification" backed by an optional notes box where the user can explain what is unclear. When any radio option other than "Other" or "Need clarification" is selected, show an optional "Additional notes" text box beneath it so the user can qualify their choice. Generate questions based on what genuinely needs user input -- do not add filler questions. Do not create a separate bottom "Decisions & Clarifications" section. Confirmed pages must not keep these as required input controls; render the answered decisions as read-only records.
 
-**Section feedback controls.** Every major section of the page (each deliverable section, evidence matrix, confidence register, gate, and any anchor-linked top-level heading) carries a lightweight section-feedback control near its heading: three mutually exclusive choices -- "emphasize" (add more weight to this section or to the point named in the notes), thumbs down (reject or flag a concern), and "clarification needed". Selecting any one reveals a multi-line section-feedback textarea placed directly under or beside that section's emphasize/down/clarify controls; deselecting hides the textarea and any local feedback YAML output for that section. This textarea is separate from required gate-question text inputs: even when the same section has gate questions with their own text boxes, selecting emphasize/down/clarify must still reveal the section-feedback textarea near the feedback controls. Use `--green` for active "emphasize", `--red` for the active thumbs-down, and `--orange` for active "clarification needed", with muted/inactive states otherwise. These controls are optional for final approval and do not replace required gate questions. They also power the separate feedback-only YAML path so the user can send emphasis requests, concerns, or clarification requests before answering every required gate question. When a section contains nested subsections (h3 or deeper), duplicate the section-feedback control at the bottom of the section, just before the closing `</section>` tag. The bottom copy mirrors the top copy — same `data-section`, same id with a `-bottom` suffix, same button set. Sections without nested subsections keep only the top control. Pair top and bottom controls by matching `data-section` attribute. When a feedback button is clicked on one copy, mirror the active state, `has-feedback` class, and `dataset.feedback` value to the paired copy. Textarea content should sync on compile — whichever textarea has content takes precedence (prefer the one the user last typed in). Both copies' local compile/copy buttons produce the same YAML. Use the top copy's `id` (without `-bottom`) as the canonical feedback id for YAML output.
+**Section feedback controls.** Every major section of the page (each deliverable section, evidence matrix, confidence register, gate, and any anchor-linked top-level heading) carries a lightweight section-feedback control near its heading: three mutually exclusive choices -- "emphasize" (add more weight to this section or to the point named in the notes), thumbs down (reject or flag a concern), and "clarification needed". The section feedback textarea, local compile/copy controls, and local read-only YAML output are hidden by default. Selecting any one feedback choice reveals a multi-line section-feedback textarea plus local "Compile Feedback YAML", "Copy YAML", and read-only YAML controls placed directly under or beside that section's emphasize/down/clarify controls; deselecting the active choice hides the textarea, local compile/copy controls, and local read-only YAML output again and omits that section from compiled responses. This textarea is separate from required gate-question text inputs: even when the same section has gate questions with their own text boxes, selecting emphasize/down/clarify must still reveal the section-feedback textarea near the feedback controls. Use `--green` for active "emphasize", `--red` for the active thumbs-down, and `--orange` for active "clarification needed", with muted/inactive states otherwise. These controls are optional for final approval and do not replace required gate questions. They also contribute `section_feedback` entries to the unified response payload so the user can send emphasis requests, concerns, or clarification requests before answering every required gate question. When a section contains nested subsections (h3 or deeper), duplicate the section-feedback control at the bottom of the section, just before the closing `</section>` tag. The bottom copy mirrors the top copy — same `data-section`, same id with a `-bottom` suffix, same button set. Sections without nested subsections keep only the top control. Pair top and bottom controls by matching `data-section` attribute. When a feedback button is clicked on one copy, mirror the active state, `has-feedback` class, and `dataset.feedback` value to the paired copy. Textarea content should sync on compile — whichever textarea has content takes precedence (prefer the one the user last typed in). Both copies' local compile/copy buttons produce the same YAML. Use the top copy's `id` (without `-bottom`) as the canonical feedback id for YAML output.
 
-**Feedback-only YAML contract.** Provide feedback-only YAML in two places: locally under each selected section-feedback textarea, and globally in the bottom compile section. When a section-feedback control is selected, show local "Compile Feedback YAML" and "Copy YAML" controls plus a read-only YAML textarea directly under that section's feedback textarea. The local feedback compile generates YAML with `alignment_page: alignment/afps-status-{topic}.html`, `feedback_status: revision-request`, `approval_status: not-approved`, `unanswered_required_questions`, and a `section_feedback` list containing the single selected section-feedback entry for that local control. The bottom "Compile Feedback YAML" control generates the same YAML shape but aggregates every selected section-feedback entry on the page. Enable both local and bottom feedback compile controls as soon as at least one section-feedback control is set, even if required inline gate questions are unanswered. Populate `alignment_page` from the known repo-relative output path used to write the HTML page, not from the page title, browser URL, window location, or any display label. Each feedback entry uses the shape `section`, `feedback` (`emphasize`, `down`, or `needs-clarification`), optional `notes` from that section's feedback textarea, and `requested_agent_action` (`add-weight-to-section`, `investigate-and-revise`, or `clarify-before-approval`). For `emphasize` feedback, the YAML must make clear that the agent should add more weight, prominence, evidence, detail, or recommendation emphasis to that section or to the specific point named in the notes; this is a revision request, not approval of the section as-is. For `down` and `needs-clarification` feedback, the YAML must make clear that the agent should evaluate the feedback, investigate further when needed, and contextually amend the HTML alignment page before asking again for final approval answers. Automatically attempt to copy feedback YAML to the clipboard, display local or bottom copy status, display it in the matching read-only textarea, and provide a "Copy YAML" button with the same retry and fallback behavior as final gate YAML. Do not render the bottom feedback compile controls as a sticky or fixed banner.
+**Section feedback YAML contract.** Provide local section-feedback YAML only under each selected section-feedback textarea. When a section-feedback control is selected, show local "Compile Feedback YAML" and "Copy YAML" controls plus a read-only YAML textarea directly under that section's feedback textarea; when the control is deselected, hide those local controls and output again. The local feedback compile generates YAML with `alignment_page: alignment/afps-status-{topic}.html`, `feedback_status: revision-request`, `approval_status: not-approved`, `unanswered_required_questions`, and a `section_feedback` list containing the single selected section-feedback entry for that local control. Enable local feedback compile controls as soon as that section-feedback control is set, even if required inline gate questions are unanswered. Populate `alignment_page` from the known repo-relative output path used to write the HTML page, not from the page title, browser URL, window location, or any display label. Each feedback entry uses the shape `section`, `feedback` (`emphasize`, `down`, or `needs-clarification`), optional `notes` from that section's feedback textarea, and `requested_agent_action` (`add-weight-to-section`, `investigate-and-revise`, or `clarify-before-approval`). For `emphasize` feedback, the YAML must make clear that the agent should add more weight, prominence, evidence, detail, or recommendation emphasis to that section or to the specific point named in the notes; this is a revision request, not approval of the section as-is. For `down` and `needs-clarification` feedback, the YAML must make clear that the agent should evaluate the feedback, investigate further when needed, and contextually amend the HTML alignment page before asking again for final approval responses. Automatically attempt to copy local feedback YAML to the clipboard, display local copy status, display it in the matching read-only textarea, and provide a "Copy YAML" button with the same retry and fallback behavior as response YAML.
 
-**Gate YAML contract.** In `review` pages, at the bottom of the page, include an ordinary in-flow compile section with a "Compile Feedback YAML" button for selected section feedback and a separate "Compile Answers" button for final approval answers. The bottom compile section must not be sticky, fixed, floating, or styled as a persistent banner. The "Compile Answers" button aggregates answers from all inline gate questions throughout the page, including free-text notes. The final approval button remains disabled until every required question has a selection, shows a count of remaining unanswered questions, and scrolls to the first unanswered question if clicked early. When every question is answered, generate a structured YAML block with `alignment_page: alignment/afps-status-{topic}.html`, `approval_status: ready-for-agent-review`, one item per gate answer using this stable shape: `section`, `gate_type`, `status` (`answered`, `other`, or `needs-clarification`), `answer`, optional `notes`, and optional `target_artifact` or `target_path` when the gate controls file output. Populate `alignment_page` from the known repo-relative output path used to write the HTML page, not from the page title, browser URL, window location, or any display label. The same final compiled output also includes any section-feedback controls that the user set, using the `section_feedback` shape from the feedback-only YAML contract. After successful compilation, automatically attempt to copy the YAML to the clipboard with the Clipboard API, display copy status, and display the YAML in a read-only textarea with an explicit "Copy YAML" button. The copy button must retry clipboard copy when supported and fall back to selecting the textarea contents when clipboard access is unavailable or blocked.
+**Response YAML contract.** In `review` pages, at the bottom of the page, include an ordinary in-flow compile section with a single "Compile Responses" button. The bottom compile section must not be sticky, fixed, floating, or styled as a persistent banner. "Compile Responses" aggregates all answered inline gate questions throughout the page, including free-text notes, plus every selected section-feedback entry. Enable it as soon as at least one gate question has an answer or at least one section-feedback control is selected; do not require every required gate question to be answered before compiling partial responses. If clicked with no answered gates and no selected section feedback, show a response status that asks the user to answer a gate question or select section feedback. The compiled YAML is a mixed response payload with `alignment_page: alignment/afps-status-{topic}.html`, `response_status` (`partial` or `complete`), `approval_status` (`not-approved` or `ready-for-agent-review`), `required_gate_status` (`incomplete` or `complete`), and `unanswered_required_questions`. It may include a `gate_answers` list where each answered gate item preserves the stable gate-answer shape: `section`, `gate_type`, `status` (`answered`, `other`, or `needs-clarification`), `answer`, optional `notes`, and optional `target_artifact` or `target_path` when the gate controls file output. It may also include a `section_feedback` list using the section-feedback shape from the section feedback YAML contract. Set `approval_status: ready-for-agent-review` only when every required gate is answered and there are no unresolved `down`, unresolved `needs-clarification`, or other unresolved negative feedback items; otherwise set `approval_status: not-approved` and keep the response in review. Populate `alignment_page` from the known repo-relative output path used to write the HTML page, not from the page title, browser URL, window location, or any display label. After successful compilation, automatically attempt to copy the YAML to the clipboard with the Clipboard API, display copy status, and display the YAML in a read-only textarea with an explicit "Copy YAML" button. The copy button must retry clipboard copy when supported and fall back to selecting the textarea contents when clipboard access is unavailable or blocked.
 
-**Confirmed page contract.** After final approval has been applied, convert the active alignment page from `review` to `confirmed`. Include a visible status block with `alignment_status: confirmed`, confirmation date, confirmed artifact paths, approval source summary, and explicit finished but amendable language: the page is current for the completed alignment cycle, and later research can amend it only by archiving the prior confirmed page and highlighting the amendment. Remove required gate-question controls, the final "Compile Answers" button, unanswered-question counters, disabled approval buttons, and approval-blocking language. Preserve the full research and approval record: answered decisions, user requests, evidence matrix, assumptions/confidence register, source gaps, proposed file changes, final compiled YAML or faithful approval summary, and what changed during confirmation. Keep research caveats visible; `confirmed` means approved/current, not immutable or permanently true.
+**Confirmed page contract.** After final approval has been applied, convert the active alignment page from `review` to `confirmed`. Include a visible status block with `alignment_status: confirmed`, confirmation date, confirmed artifact paths, approval source summary, and explicit finished but amendable language: the page is current for the completed alignment cycle, and later research can amend it only by archiving the prior confirmed page and highlighting the amendment. Remove required gate-question controls, section feedback input controls, local compile/copy controls, local read-only YAML outputs, the final "Compile Responses" button, response counters, disabled approval buttons, and approval-blocking language. Preserve the full research and approval record: answered decisions, user requests, evidence matrix, assumptions/confidence register, source gaps, proposed file changes, final compiled response YAML or faithful approval summary, and what changed during confirmation. Keep research caveats visible; `confirmed` means approved/current, not immutable or permanently true.
 
-**Pre-approval stop.** While an alignment page is in `review`, the next action is review of the HTML alignment page, not downstream routing. Ask the user to review the page and provide either local or bottom feedback-only YAML for emphasis requests, concerns, or clarification, or final compiled YAML answers when ready. Do not require the user to answer every gate before sending emphasis requests, negative feedback, or clarification needs. When feedback-only YAML is provided, treat it as a revision request: evaluate the feedback, investigate further when needed, archive and amend the HTML page contextually, highlight the changes, and ask again for review. Do not include `Recommended next skill`, `Recommended next command`, or downstream routing language until after final compiled YAML has been provided and the approved artifacts have been written or updated.
+**Pre-approval stop.** While an alignment page is in `review`, the next action is review of the HTML alignment page, not downstream routing. Ask the user to review the page and provide either local section-feedback YAML for one section or bottom compiled response YAML for gate answers and/or selected section feedback. Do not require the user to answer every gate before sending emphasis requests, negative feedback, clarification needs, or other partial responses. When compiled response YAML is partial or has `approval_status: not-approved`, treat it as a revision request: evaluate the feedback, investigate further when needed, archive and amend the HTML page contextually, highlight the changes, and ask again for review. Do not include `Recommended next skill`, `Recommended next command`, or downstream routing language until after final compiled response YAML with `approval_status: ready-for-agent-review` has been provided and the approved artifacts have been written or updated.
 
-**After approval handling.** When final compiled YAML is provided, inspect it before confirming the page. If it contains approvals plus user-requested edits, first update the page, research, and proposed canonical artifacts to satisfy the request; then write or update the approved canonical artifacts and confirm the page. If it contains `needs-clarification`, unresolved `down` feedback, or any unresolved negative feedback, revise the page and return it to `review` instead of marking it `confirmed`. Before replacing any existing alignment page, archive it to `docs/history/archive/YYYY-MM-DD/HHMMSS/alignment/afps-status-{topic}.html`. Future amendments to confirmed pages follow the same archive-first rule and must show what changed from the prior confirmed record.
+**After approval handling.** When final compiled response YAML with `approval_status: ready-for-agent-review` is provided, inspect it before confirming the page. If it contains approvals plus user-requested edits, first update the page, research, and proposed canonical artifacts to satisfy the request; then write or update the approved canonical artifacts and confirm the page. If it contains `needs-clarification`, unresolved `down` feedback, or any unresolved negative feedback, revise the page and return it to `review` instead of marking it `confirmed`. Before replacing any existing alignment page, archive it to `docs/history/archive/YYYY-MM-DD/HHMMSS/alignment/afps-status-{topic}.html`. Future amendments to confirmed pages follow the same archive-first rule and must show what changed from the prior confirmed record.
 
 **Diff highlighting on updates.** When the agent updates an existing alignment page after receiving feedback, compiled answers, confirmation edits, or later amendment evidence, the rendered HTML must visibly indicate what changed since the previous version. Highlight changed sections or blocks in-place with a `Changed`/`Updated` badge, distinct border or background, `<ins>`/`<del>` markup, or a side-by-side before/after comparison when that is clearer. A top-level change summary is useful but not sufficient by itself unless the changed content is also visibly marked where the reader reviews it. Remove or refresh stale change markers on later updates so the highlights describe the current revision only.
 
 **Archiving.** Before replacing an existing alignment page, archive it to `docs/history/archive/YYYY-MM-DD/HHMMSS/alignment/afps-status-{topic}.html`.
 
-**Brief Me (text-to-speech).** Every alignment page must include a `<script src="../scripts/alignment-tts-kokoro.js"></script>` tag before `</body>`. The script adds a "Brief Me" button that reads the page aloud section-by-section using Kokoro TTS (an 82M-parameter model running client-side via WebGPU/WASM from `kokoro-js`). The transport bar includes play/pause/stop/skip controls, a voice selector (persisted in localStorage), and speed selection. On first click the voice model downloads (~92MB quantized on WASM; ~326MB fp32 on WebGPU). Weights persist between visits via Cache API origin storage, and this works on `file://` origins in Chrome — including `file://wsl.localhost` UNC paths (verified 2026-06-09 with an instrumented probe in Windows Chrome: `caches` is available, entries survive reloads and browser restarts, and Chrome shares a single `file://` origin across all local pages, so one download serves every alignment page). Repeat visits pay model initialization only, not re-download. If `caches` is undefined (non-Chromium or locked-down browsers), the model re-downloads each visit; serving pages from a local HTTP origin (e.g. `node scripts/serve-alignment.mjs` in the repo root, then `http://localhost:8907/alignment/<page>.html`) guarantees caching there — note `http://localhost` is a separate origin from `file://`, so the first localhost visit downloads once even when the `file://` cache is already warm. After the first successful load on a machine, the script preloads the model during browser idle time on later page loads (gated by a `tts-kokoro-used` localStorage flag, so users who never click pay nothing). Text is prepared for speech before synthesis: block boundaries (headings, paragraphs, list items, table cells) get sentence punctuation so the model does not read them as run-ons, and speech-hostile symbols are normalized (`~92MB` reads as "approximately 92MB", `v0.3` as "version 0.3", em-dashes as comma pauses, `e.g.`/`i.e.`/`vs.` expanded). Synthesis is pipelined with small chunks: the first audio chunk is kept short (~250 chars) for fast time-to-first-audio, later chunks stay small (~300 chars, cut at sentence or clause boundaries) with up to two chunks synthesizing ahead during playback, and the next section's opening chunk is prefetched while the current section's last chunk plays, so chunk and section boundaries are gapless. If Kokoro fails to load (old browser, network error), it falls back to the Web Speech API automatically. It skips gate controls, compile UI, feedback textareas, and stat grids. Charts and tables use narrative summaries instead of raw data: containers with a `data-tts-narrative` attribute have the narrative read aloud; containers without the attribute are silently skipped. To inject TTS into existing pages, run `node scripts/inject-tts.mjs` (idempotent). Use `--force` to replace the existing TTS block with an updated version. Do not inline the TTS script; always use the `src` tag. Do not use `type="module"` — module scripts are blocked by CORS on `file://` URLs.
+**Brief Me (text-to-speech).** Every alignment page must include a `<script src="../scripts/alignment-tts-kokoro.js"></script>` tag before `</body>`. The script adds a "Brief Me" button that reads the page aloud section-by-section using Kokoro TTS (an 82M-parameter model running client-side via WebGPU/WASM from `kokoro-js`). The transport bar includes play/pause/stop/skip controls, a voice selector (persisted in localStorage), and speed selection. On first click the voice model downloads (~92MB quantized on WASM; ~326MB fp32 on WebGPU). Weights persist between visits via Cache API origin storage, and this works on `file://` origins in Chrome — including `file://wsl.localhost` UNC paths (verified 2026-06-09 with an instrumented probe in Windows Chrome: `caches` is available, entries survive reloads and browser restarts, and Chrome shares a single `file://` origin across all local pages, so one download serves every alignment page). Repeat visits pay model initialization only, not re-download. If `caches` is undefined (non-Chromium or locked-down browsers), the model re-downloads each visit; serving pages from a local HTTP origin (e.g. `node scripts/serve-alignment.mjs` in the repo root, then `http://localhost:8907/alignment/<page>.html`) guarantees caching there — note `http://localhost` is a separate origin from `file://`, so the first localhost visit downloads once even when the `file://` cache is already warm. After the first successful load on a machine, the script preloads the model during browser idle time on later page loads (gated by a `tts-kokoro-used` localStorage flag, so users who never click pay nothing). Text is prepared for speech before synthesis: block boundaries (headings, paragraphs, list items, table cells) get sentence punctuation so the model does not read them as run-ons, and speech-hostile symbols are normalized (`~92MB` reads as "approximately 92MB", `v0.3` as "version 0.3", em-dashes as comma pauses, `e.g.`/`i.e.`/`vs.` expanded). Synthesis is pipelined with small chunks: the first audio chunk is kept short (~250 chars) for fast time-to-first-audio, later chunks stay small (~300 chars, cut at sentence or clause boundaries) with up to two chunks synthesizing ahead during playback, and the next section's opening chunk is prefetched while the current section's last chunk plays, so chunk and section boundaries are gapless. If Kokoro fails to load (old browser, network error), it falls back to the Web Speech API automatically. It skips gate controls, compile UI, feedback textareas, and stat grids. Charts and tables use narrative summaries instead of raw data: containers with a `data-tts-narrative` attribute have the narrative read aloud; containers without the attribute are silently skipped. To inject TTS into existing pages, run `node scripts/inject-tts.mjs` (idempotent). Use `--force` to replace the existing TTS block with an updated version. Do not inline the TTS script; always use the `src` tag. Do not use `type="module"` — module scripts are blocked by CORS on `file://` URLs. Narration follows along visually: the blocks currently being read (paragraphs, list items, table rows, headings, chart narratives) receive a `.tts-active-chunk` highlight at ~1–2-sentence chunk granularity, and the page auto-scrolls to keep them centered (instantly rather than smoothly under `prefers-reduced-motion: reduce`), while the active section keeps a lightened outline frame. The Web Speech fallback stays section-level — outline plus section-start scroll, no per-chunk highlight.
 
 **TTS narrative contract.** Every `.chart-container` and `.table-wrap` element should carry a `data-tts-narrative` attribute with a 1-3 sentence human-readable summary of what the chart or table shows. Chart functions in `scripts/alignment-chart-snippets.js` auto-generate a baseline narrative from their data; author-provided `data-tts-narrative` attributes take precedence. When authoring alignment pages manually, add `data-tts-narrative` to chart containers and table wrappers so that Brief Me reads a meaningful summary instead of skipping the element.
 
-**Browser open.** After writing the resulting HTML page, run `node scripts/open-html-page.mjs alignment/afps-status-{topic}.html --browser auto` from the repository root, replacing the path with the actual page path when needed. Report the script status (`focused`, `opened`, `fallback-opened`, `blocked`, or `failed`) in the handoff. Continue when opening is `blocked` if the files were written and verified correctly; a blocked browser-open attempt does not make the skill fail.
+**Browser open.** After writing the resulting HTML page, attempt to open it from the repository root with this ordered fallback, replacing `alignment/afps-status-{topic}.html` with the actual page path when needed. First, if `scripts/open-html-page.mjs` exists, run `node scripts/open-html-page.mjs alignment/afps-status-{topic}.html --browser auto`. If the helper is missing or cannot open the page and the environment is WSL (`grep -qi microsoft /proc/version`) with `/mnt/c/WINDOWS/System32/WindowsPowerShell/v1.0/powershell.exe` available, open a browser-friendly file URI through PowerShell: build `file://wsl.localhost/${WSL_DISTRO_NAME:-Ubuntu}/<absolute-linux-path>` from the HTML page's absolute path and run PowerShell `Start-Process '<file-uri>'`. Try `xdg-open <absolute-linux-path>` only after the helper path and WSL PowerShell bridge are unavailable or blocked. Report the final status (`focused`, `opened`, `fallback-opened`, `blocked`, or `failed`) in the handoff, and include the absolute path when the status is `blocked` or `failed`. Continue when opening is `blocked` if the files were written and verified correctly; a blocked browser-open attempt does not make the skill fail.