skillpacks 0.1.0 → 0.1.1

package/global/codex/idea-scope-brief/archive/v0.13/SKILL.md

@@ -0,0 +1,158 @@
+---
+name: idea-scope-brief
+description: Shape a rough product or project idea into a scoped brief before customer discovery, market research, specifications, UX, UI, or implementation planning
+type: planning
+version: v0.13
+argument-hint: "[optional rough idea, product thought, or product-path scope]"
+interview_depth: full
+---
+
+# Idea Scope Brief
+
+Invoke as `$idea-scope-brief`.
+
+Use this skill when the user has a half-formed idea and needs it cleaned up enough to enter the normal research and planning workflow. This skill is intentionally pre-customer-discovery: it clarifies the concept, problem hypothesis, beneficiary hypothesis, value wedge, constraints, non-goals, and unknowns, but does not select a validated target-customer segment, analyze competitors, define UX/UI, choose architecture, or write implementation specs.
+
+## Process
+
+### 0. Product-Path Scope Resolution
+
+Resolve research scope by product path before using code or app structure as a hint:
+
+1. If `$ARGUMENTS` names a non-archived `research/{slug}/` directory or a product-path ID whose `scope_path` points there, use that path. Treat `{slug}` as the product/app name, not the customer, audience, or segment label.
+2. If `$ARGUMENTS` names only `research/_archive/{slug}/` or a manifest entry with `status: archived` or legacy `status: abandoned`, stop and warn that the path is archived; do not write or update scoped outputs there.
+3. Read `research/.progress.yaml` when present. Normalize legacy `active_path` to `active_paths` on read and write back `active_paths` on manifest updates. Treat legacy `abandoned` as `archived`; exclude `archived`, `abandoned`, `deferred`, `revisit_candidate`, `promoted`, and any `scope_path` under `research/_archive/` from active target selection.
+4. If active product paths exist in the manifest, use those paths. If multiple active paths exist, ask which one to target unless this skill explicitly supports cross-path output.
+5. If no active manifest target exists, list non-archived product directories under `research/`, excluding `research/_archive/` and dot directories. Auto-select only when exactly one exists; ask when multiple exist.
+6. If no product directories exist, use flat `research/` single-product mode.
+7. Detect monorepo/app/package structure only as a secondary hint. Suggest creating a missing `research/{slug}/` product path when code clearly exposes an app, but do not require code or monorepo detection before using `research/{slug}/`.
+
+When product path `{slug}` is active, read and write research under `research/{slug}/`, specs under `specs/{slug}/`, and treat top-level `research/*.md` files as flat-mode documents or cross-path summaries.
+
+1. **Resolve context**
+   - Read `.agents/project.json` if it exists.
+   - Read README, CLAUDE.md, AGENTS.md, existing `research/`, `specs/`, and task docs when present.
+   - Determine whether the current directory is already a bootstrapped project. Treat it as bootstrapped when it has meaningful `README.md` plus `AGENTS.md` or `CLAUDE.md`; treat it as unbootstrapped when those are missing, placeholder-only, or the user is describing an idea outside any project repo.
+   - If `$ARGUMENTS` contains a rough idea, use it as the starting draft.
+   - If `$ARGUMENTS` names a non-archived `research/{slug}/` product path, use that path. If it names only `research/_archive/{slug}/`, stop and warn that the path is archived.
+   - Determine the concept identity and a normalized concept slug as soon as either is known from `$ARGUMENTS`, repo context, or the interview. Normalize by lowercasing, removing URL suffix noise, replacing non-alphanumeric runs with `-`, trimming leading/trailing `-`, and dropping only project-wide brand prefixes when the remaining word is the actual scoped concept (for example, `poketo.work` -> `work`; `Poketo Core` -> `poketo-core`).
+   - If existing research or the prompt suggests multiple related concepts may exist, prefer slugged output paths over generic filenames. Reserve generic `idea-brief.md` only for a single unambiguous project-level concept.
+   - If no rough idea is available from arguments or repo context, ask the user for the idea in plain language.
+   - Read `research/.progress.yaml` when present. Normalize `active_path` (singular legacy) to `active_paths` (plural list) when reading; treat legacy `abandoned` as `archived` and exclude archived/deferred/revisit/promoted paths plus `research/_archive/` scopes from active target selection. Treat `active_paths` as the current product/app/customer focuses and `product_paths[]` as parked, archived, or promoted product-path state, not git branch state.
+   - When the prompt, repo context, interview, or pivot history surfaces multiple related concepts, apps, product lines, or future pivots, update or propose updates to `research/.progress.yaml` with product-path entries instead of merging them into one generic concept. Use fields: `id`, `label`, `scope_path`, `status`, `source_skill`, `reason`, `archive_reason`, `archived_at`, `promoted_at`, `evidence_refs`, `revisit_trigger`, `next_skill`, `pipeline_stage`, and `last_touched`. Set `pipeline_stage: idea-scope-brief` on entries created by this skill.
+   - Keep the central concept in `active_paths` when it is the current focus. Record related or future concepts as `status: deferred` or `status: revisit_candidate` with a concrete revisit trigger and a likely next skill such as `$customer-discovery <path/audience>`; if `business-discovery` is not enabled, recommend `$pack install business-discovery` inside Codex, or `npx skillpacks install business-discovery` from the project shell, before `$customer-discovery`.
+   - When 3+ product paths exist in the manifest, recommend `$product-line review` to the user for portfolio management; if `business-ops` is not enabled, recommend `$pack install business-ops` inside Codex, or `npx skillpacks install business-ops` from the project shell, before `$product-line`.
+
+2. **Keep the boundary clear**
+   - Do not run customer discovery, competitive analysis, journey mapping, UX variation, UI interview, roadmap, or implementation planning inside this skill.
+   - Do not validate the market with broad web research. Use light repo/context inspection only; downstream research skills own evidence gathering.
+   - Treat every user claim as a hypothesis unless supported by existing project files.
+
+3. **Surface an Idea Assumptions Manifest**
+   - Before deep questioning, present what you think the concept is.
+   - Tag assumptions as `[from prompt]`, `[from repo]`, `[from research]`, or `[inferred]`.
+   - Cover:
+     - concept summary
+     - problem hypothesis
+     - target beneficiary or user hypothesis
+     - product/category guess
+     - value wedge
+     - constraints
+     - non-goals
+     - riskiest unknowns
+   - Ask the user to confirm, correct, or flag assumptions before writing.
+
+### Market Structure Handoff
+
+During the Idea Assumptions Manifest, if the concept appears marketplace/platform/B2B2C/multi-sided, add a compact `Market Structure Handoff` note:
+
+- Name the apparent sides and the expected value exchange between them.
+- Mark those sides and exchanges as hypotheses, not validated customer segments; do not decide which side is the customer, buyer, or primary target segment here.
+- Keep the source tag for each side as `[from prompt]`, `[from repo]`, or `[inferred]` unless the user provides a correction.
+- If the concept appears single-sided, omit the handoff or state that no marketplace/platform/B2B2C/multi-sided handoff is apparent.
+
+4. **Interview until concept-ready**
+   - Codex interview cadence is one primary decision question per turn by default. Use short follow-up bullets only when they clarify the same decision, not to batch unrelated questions.
+   - Resolve only concept-level ambiguity:
+     - what problem exists
+     - who might care
+     - what outcome changes for them
+     - what makes the idea different enough to investigate
+     - what must stay out of scope
+     - what constraints are real now
+   - When unsure, recommend a practical default and clearly mark it as an assumption.
+
+5. **Coverage checkpoint**
+   - Present the final concept summary, unknowns, and readiness for customer discovery.
+   - Restate the resolved concept identity, slug, and exact output paths before writing.
+   - If the conversation pivoted from the initial concept to a different central concept, write the pivoted concept to its own slugged brief and preserve the initial concept as a related or future concept in the brief and interview log. Do not merge both concepts into one generic project-level brief.
+   - Ask whether any core premise, constraint, or non-goal is wrong before writing.
+
+6. **Build pre-approval alignment preview**
+   - Before writing any canonical `research/**/idea-brief.md`, `research/**/idea-brief-interview.md`, legacy flat `research/idea-brief-{slug}.md` variant, or `research/.progress.yaml`, build `alignment/idea-scope-brief-{topic}.html` as the review artifact.
+   - The HTML page must render the Idea/Concept Assumptions Manifest, artifact destinations, proposed file changes, coverage checkpoint, and approval gates, including any Market Structure Handoff.
+   - Attempt to open the page in the browser and point the user at the repo-relative path.
+   - Treat coverage-checkpoint confirmation as non-final; it only confirms the draft scope is ready to preview. Only final compiled YAML from the alignment page authorizes canonical writes.
+   - Before compiled YAML approval, the next action is review or revision of the HTML alignment page. Do not include `Recommended next skill`, `Recommended next command`, or downstream routing language until after final compiled YAML approval has been provided and the approved artifacts below have been written or updated.
+   - When feedback-only YAML is provided, revise the alignment page and ask again; do not write canonical artifacts until final compiled YAML approval is provided.
+
+### Review-Only Product Path Approval
+
+When the user approves a product-path fork or split at the alignment page level but explicitly withholds canonical-write approval (e.g., "review only, do not write canonical files"):
+
+1. **Do not write canonical files.** Keep `research/.progress.yaml`, `research/{slug}/idea-brief.md`, and `research/{slug}/idea-brief-interview.md` unchanged.
+2. **Render fully in the alignment page.** The proposed manifest entry, idea brief sections, and interview log for the review-only path must be rendered in full in the alignment page HTML — not summarized, linked, or embedded.
+3. **Mark the page as review-only-approved.** Set `approval_status: review-only-approved` in the alignment page status block. This is distinct from `confirmed` (canonical artifacts written) and `review` (awaiting any approval).
+4. **Downstream treatment.** Downstream skills must treat a review-only-approved path as provisional: it may be referenced as concept context, but it is not a canonical product path until manifest approval is later granted via a subsequent alignment cycle. See the provisional-path evidence rule in customer-discovery and competitive-analysis contracts.
+
+## Output
+
+Before writing anything in this section, verify the alignment page has final compiled YAML approval. Do not write canonical idea briefs, interview logs, or `research/.progress.yaml` until `alignment/idea-scope-brief-{topic}.html` has been reviewed and the user has provided final compiled YAML approval. Coverage-checkpoint confirmation is not final approval and does not authorize these writes.
+
+Write:
+
+- For one unambiguous project-level concept only: `research/idea-brief.md` and `research/idea-brief-interview.md`.
+- When a product identity is known, multiple concepts exist or may exist, or a pivot occurs: prefer `research/{slug}/idea-brief.md` and `research/{slug}/idea-brief-interview.md`; preserve flat `research/idea-brief-{slug}.md` only as legacy compatibility when no product path is being introduced.
+- If `$ARGUMENTS` names a non-archived product path, use unsuffixed scoped files under `research/{slug}/`: `research/{slug}/idea-brief.md` and `research/{slug}/idea-brief-interview.md`.
+- `research/.progress.yaml` — create or update only when multiple concepts, product paths, product lines, product-path scopes, or pivots are present. Use `product_paths` terminology instead of branch terminology.
+
+The idea brief must include:
+
+- `## Summary`
+- `## Problem Hypothesis`
+- `## Beneficiary Hypothesis`
+- `## Product Category Guess`
+- `## Value Wedge`
+- `## Constraints`
+- `## Non-Goals`
+- `## Assumptions And Unknowns`
+- `## Customer Discovery Readiness`
+- `## Next Steps`
+
+The `## Customer Discovery Readiness` section must state whether the concept is ready for `$customer-discovery`, what inputs `$customer-discovery` should use, and which assumptions should be tested first. If a Market Structure Handoff exists, include the apparent sides and value exchange as explicit inputs for `$customer-discovery` to validate or refute.
+
+The `## Next Steps` section must recommend exactly one primary command:
+
+- If the concept appears to be a business app or user-facing product and the business discovery lane is not enabled: `$pack install business-discovery` inside Codex, or `npx skillpacks install business-discovery` from the project shell — this installs the research skills (customer discovery, competitive analysis, value prop, positioning, lean canvas) needed before any repo bootstrapping or development.
+- If `business-discovery` or the compatibility `business-app` alias is enabled: `$customer-discovery`
+- If the concept already has customer-discovery/market evidence but needs journey, onboarding, conversion, or retention planning: `$pack install customer-lifecycle` inside Codex, or `npx skillpacks install customer-lifecycle` from the project shell.
+- If project type is unclear: `$pack recommend`
+
+Include 1-3 other options only when they are materially useful.
+
+### Alignment Page
+
+When this skill produces durable deliverables (research, specs, plans, reports, prototypes, or any document output), build a full-depth HTML alignment page following `ALIGNMENT-PAGE.md` in this skill's directory. Output: `alignment/idea-scope-brief-{topic}.html`.
+
+## Constraints
+
+- Keep the skill short and pre-research.
+- Do not write specs, UX variants, UI specs, roadmap phases, or implementation tasks.
+- Do not recommend `$scaffold` unless the user explicitly asks to create a package/app shell before research; normal product flow scaffolds after research, prototype consolidation, spec, roadmap, and phase planning identify the first implementation target. `$scaffold` requires the monorepo pack (`$pack install monorepo` inside Codex, or `npx skillpacks install monorepo` from the project shell).
+- Do not update `tasks/todo.md`.
+- New files do not need archive snapshots. Before replacing an existing idea brief, including slugged briefs, archive it to `docs/history/archive/YYYY-MM-DD/HHMMSS/<original-relative-path>`.
+- Migration: if a project already has `research/concept-brief.md`, `research/concept-brief-interview.md`, or any `research/{slug}/concept-brief*.md` / `research/concept-brief-{slug}*.md` from a prior run, rename it to the `idea-brief` equivalent before re-running. Write only the `idea-brief` names and no longer recognizes the legacy `concept-brief` filenames.
+
+## Default Shipping Contract
+
+Follow the shared shipping contract convention in CLAUDE.md.

package/global/codex/idea-scope-brief/archive/v0.14/SKILL.md

@@ -0,0 +1,159 @@
+---
+name: idea-scope-brief
+description: Shape a rough product or project idea into a scoped brief before customer discovery, market research, specifications, UX, UI, or implementation planning
+type: planning
+version: v0.14
+argument-hint: "[optional rough idea, product thought, or product-path scope]"
+interview_depth: full
+---
+
+# Idea Scope Brief
+
+Invoke as `$idea-scope-brief`.
+
+Use this skill when the user has a half-formed idea and needs it cleaned up enough to enter the normal research and planning workflow. This skill is intentionally pre-customer-discovery: it clarifies the concept, problem hypothesis, beneficiary hypothesis, value wedge, constraints, non-goals, and unknowns, but does not select a validated target-customer segment, analyze competitors, define UX/UI, choose architecture, or write implementation specs.
+
+## Process
+
+### 0. Product-Path Scope Resolution
+
+Resolve research scope by product path before using code or app structure as a hint:
+
+1. If `$ARGUMENTS` names a non-archived `research/{slug}/` directory or a product-path ID whose `scope_path` points there, use that path. Treat `{slug}` as the product/app name, not the customer, audience, or segment label.
+2. If `$ARGUMENTS` names only `research/_archive/{slug}/` or a manifest entry with `status: archived` or legacy `status: abandoned`, stop and warn that the path is archived; do not write or update scoped outputs there.
+3. Read `research/.progress.yaml` when present. Normalize legacy `active_path` to `active_paths` on read and write back `active_paths` on manifest updates. Treat legacy `abandoned` as `archived`; exclude `archived`, `abandoned`, `deferred`, `revisit_candidate`, `promoted`, and any `scope_path` under `research/_archive/` from active target selection.
+4. If active product paths exist in the manifest, use those paths. If multiple active paths exist, ask which one to target unless this skill explicitly supports cross-path output.
+5. If no active manifest target exists, list non-archived product directories under `research/`, excluding `research/_archive/` and dot directories. Auto-select only when exactly one exists; ask when multiple exist.
+6. If no product directories exist, use flat `research/` single-product mode.
+7. Detect monorepo/app/package structure only as a secondary hint. Suggest creating a missing `research/{slug}/` product path when code clearly exposes an app, but do not require code or monorepo detection before using `research/{slug}/`.
+
+When product path `{slug}` is active, read and write research under `research/{slug}/`, specs under `specs/{slug}/`, and treat top-level `research/*.md` files as flat-mode documents or cross-path summaries.
+
+1. **Resolve context**
+   - Read `.agents/project.json` if it exists.
+   - Read README, CLAUDE.md, AGENTS.md, existing `research/`, `specs/`, and task docs when present.
+   - Determine whether the current directory is already a bootstrapped project. Treat it as bootstrapped when it has meaningful `README.md` plus `AGENTS.md` or `CLAUDE.md`; treat it as unbootstrapped when those are missing, placeholder-only, or the user is describing an idea outside any project repo.
+   - If `$ARGUMENTS` contains a rough idea, use it as the starting draft.
+   - If `$ARGUMENTS` names a non-archived `research/{slug}/` product path, use that path. If it names only `research/_archive/{slug}/`, stop and warn that the path is archived.
+   - Determine the concept identity and a normalized concept slug as soon as either is known from `$ARGUMENTS`, repo context, or the interview. Normalize by lowercasing, removing URL suffix noise, replacing non-alphanumeric runs with `-`, trimming leading/trailing `-`, and dropping only project-wide brand prefixes when the remaining word is the actual scoped concept (for example, `poketo.work` -> `work`; `Poketo Core` -> `poketo-core`).
+   - If existing research or the prompt suggests multiple related concepts may exist, prefer slugged output paths over generic filenames. Reserve generic `idea-brief.md` only for a single unambiguous project-level concept.
+   - If no rough idea is available from arguments or repo context, ask the user for the idea in plain language.
+   - Read `research/.progress.yaml` when present. Normalize `active_path` (singular legacy) to `active_paths` (plural list) when reading; treat legacy `abandoned` as `archived` and exclude archived/deferred/revisit/promoted paths plus `research/_archive/` scopes from active target selection. Treat `active_paths` as the current product/app/customer focuses and `product_paths[]` as parked, archived, or promoted product-path state, not git branch state.
+   - When the prompt, repo context, interview, or pivot history surfaces multiple related concepts, apps, product lines, or future pivots, update or propose updates to `research/.progress.yaml` with product-path entries instead of merging them into one generic concept. Use fields: `id`, `label`, `scope_path`, `status`, `source_skill`, `reason`, `archive_reason`, `archived_at`, `promoted_at`, `evidence_refs`, `revisit_trigger`, `next_skill`, `pipeline_stage`, and `last_touched`. Set `pipeline_stage: idea-scope-brief` on entries created by this skill.
+   - Keep the central concept in `active_paths` when it is the current focus. Record related or future concepts as `status: deferred` or `status: revisit_candidate` with a concrete revisit trigger and a likely next skill such as `$customer-discovery <path/audience>`; if `business-discovery` is not enabled, recommend `$pack install business-discovery` inside Codex, or `npx skillpacks install business-discovery` from the project shell, before `$customer-discovery`.
+   - When 3+ product paths exist in the manifest, recommend `$product-line review` to the user for portfolio management; if `business-ops` is not enabled, recommend `$pack install business-ops` inside Codex, or `npx skillpacks install business-ops` from the project shell, before `$product-line`.
+
+2. **Keep the boundary clear**
+   - Do not run customer discovery, competitive analysis, journey mapping, UX variation, UI interview, roadmap, or implementation planning inside this skill.
+   - Do not validate the market with broad web research. Use light repo/context inspection only; downstream research skills own evidence gathering.
+   - Treat every user claim as a hypothesis unless supported by existing project files.
+
+3. **Surface an Idea Assumptions Manifest**
+   - Before deep questioning, present what you think the concept is.
+   - Tag assumptions as `[from prompt]`, `[from repo]`, `[from research]`, or `[inferred]`.
+   - Cover:
+     - concept summary
+     - problem hypothesis
+     - target beneficiary or user hypothesis
+     - product/category guess
+     - value wedge
+     - constraints
+     - non-goals
+     - riskiest unknowns
+   - Ask the user to confirm, correct, or flag assumptions before writing.
+   - Deliver the manifest inline as the final message text of its own turn; ask the confirmation question in the next turn (consistent with the one-question-per-turn cadence). Never emit it only as mid-turn text in a turn that ends with a tool or command call — harness rendering does not guarantee mid-turn text is shown. A confirmation question must never reference content the user has not been shown.
+
+### Market Structure Handoff
+
+During the Idea Assumptions Manifest, if the concept appears marketplace/platform/B2B2C/multi-sided, add a compact `Market Structure Handoff` note:
+
+- Name the apparent sides and the expected value exchange between them.
+- Mark those sides and exchanges as hypotheses, not validated customer segments; do not decide which side is the customer, buyer, or primary target segment here.
+- Keep the source tag for each side as `[from prompt]`, `[from repo]`, or `[inferred]` unless the user provides a correction.
+- If the concept appears single-sided, omit the handoff or state that no marketplace/platform/B2B2C/multi-sided handoff is apparent.
+
+4. **Interview until concept-ready**
+   - Codex interview cadence is one primary decision question per turn by default. Use short follow-up bullets only when they clarify the same decision, not to batch unrelated questions.
+   - Resolve only concept-level ambiguity:
+     - what problem exists
+     - who might care
+     - what outcome changes for them
+     - what makes the idea different enough to investigate
+     - what must stay out of scope
+     - what constraints are real now
+   - When unsure, recommend a practical default and clearly mark it as an assumption.
+
+5. **Coverage checkpoint**
+   - Present the final concept summary, unknowns, and readiness for customer discovery.
+   - Restate the resolved concept identity, slug, and exact output paths before writing.
+   - If the conversation pivoted from the initial concept to a different central concept, write the pivoted concept to its own slugged brief and preserve the initial concept as a related or future concept in the brief and interview log. Do not merge both concepts into one generic project-level brief.
+   - Ask whether any core premise, constraint, or non-goal is wrong before writing.
+
+6. **Build pre-approval alignment preview**
+   - Before writing any canonical `research/**/idea-brief.md`, `research/**/idea-brief-interview.md`, legacy flat `research/idea-brief-{slug}.md` variant, or `research/.progress.yaml`, build `alignment/idea-scope-brief-{topic}.html` as the review artifact.
+   - The HTML page must render the Idea/Concept Assumptions Manifest, artifact destinations, proposed file changes, coverage checkpoint, and approval gates, including any Market Structure Handoff.
+   - Attempt to open the page in the browser and point the user at the repo-relative path.
+   - Treat coverage-checkpoint confirmation as non-final; it only confirms the draft scope is ready to preview. Only final compiled YAML from the alignment page authorizes canonical writes.
+   - Before compiled YAML approval, the next action is review or revision of the HTML alignment page. Do not include `Recommended next skill`, `Recommended next command`, or downstream routing language until after final compiled YAML approval has been provided and the approved artifacts below have been written or updated.
+   - When feedback-only YAML is provided, revise the alignment page and ask again; do not write canonical artifacts until final compiled YAML approval is provided.
+
+### Review-Only Product Path Approval
+
+When the user approves a product-path fork or split at the alignment page level but explicitly withholds canonical-write approval (e.g., "review only, do not write canonical files"):
+
+1. **Do not write canonical files.** Keep `research/.progress.yaml`, `research/{slug}/idea-brief.md`, and `research/{slug}/idea-brief-interview.md` unchanged.
+2. **Render fully in the alignment page.** The proposed manifest entry, idea brief sections, and interview log for the review-only path must be rendered in full in the alignment page HTML — not summarized, linked, or embedded.
+3. **Mark the page as review-only-approved.** Set `approval_status: review-only-approved` in the alignment page status block. This is distinct from `confirmed` (canonical artifacts written) and `review` (awaiting any approval).
+4. **Downstream treatment.** Downstream skills must treat a review-only-approved path as provisional: it may be referenced as concept context, but it is not a canonical product path until manifest approval is later granted via a subsequent alignment cycle. See the provisional-path evidence rule in customer-discovery and competitive-analysis contracts.
+
+## Output
+
+Before writing anything in this section, verify the alignment page has final compiled YAML approval. Do not write canonical idea briefs, interview logs, or `research/.progress.yaml` until `alignment/idea-scope-brief-{topic}.html` has been reviewed and the user has provided final compiled YAML approval. Coverage-checkpoint confirmation is not final approval and does not authorize these writes.
+
+Write:
+
+- For one unambiguous project-level concept only: `research/idea-brief.md` and `research/idea-brief-interview.md`.
+- When a product identity is known, multiple concepts exist or may exist, or a pivot occurs: prefer `research/{slug}/idea-brief.md` and `research/{slug}/idea-brief-interview.md`; preserve flat `research/idea-brief-{slug}.md` only as legacy compatibility when no product path is being introduced.
+- If `$ARGUMENTS` names a non-archived product path, use unsuffixed scoped files under `research/{slug}/`: `research/{slug}/idea-brief.md` and `research/{slug}/idea-brief-interview.md`.
+- `research/.progress.yaml` — create or update only when multiple concepts, product paths, product lines, product-path scopes, or pivots are present. Use `product_paths` terminology instead of branch terminology.
+
+The idea brief must include:
+
+- `## Summary`
+- `## Problem Hypothesis`
+- `## Beneficiary Hypothesis`
+- `## Product Category Guess`
+- `## Value Wedge`
+- `## Constraints`
+- `## Non-Goals`
+- `## Assumptions And Unknowns`
+- `## Customer Discovery Readiness`
+- `## Next Steps`
+
+The `## Customer Discovery Readiness` section must state whether the concept is ready for `$customer-discovery`, what inputs `$customer-discovery` should use, and which assumptions should be tested first. If a Market Structure Handoff exists, include the apparent sides and value exchange as explicit inputs for `$customer-discovery` to validate or refute.
+
+The `## Next Steps` section must recommend exactly one primary command:
+
+- If the concept appears to be a business app or user-facing product and the business discovery lane is not enabled: `$pack install business-discovery` inside Codex, or `npx skillpacks install business-discovery` from the project shell — this installs the research skills (customer discovery, competitive analysis, value prop, positioning, lean canvas) needed before any repo bootstrapping or development.
+- If `business-discovery` or the compatibility `business-app` alias is enabled: `$customer-discovery`
+- If the concept already has customer-discovery/market evidence but needs journey, onboarding, conversion, or retention planning: `$pack install customer-lifecycle` inside Codex, or `npx skillpacks install customer-lifecycle` from the project shell.
+- If project type is unclear: `$pack recommend`
+
+Include 1-3 other options only when they are materially useful.
+
+### Alignment Page
+
+When this skill produces durable deliverables (research, specs, plans, reports, prototypes, or any document output), build a full-depth HTML alignment page following `ALIGNMENT-PAGE.md` in this skill's directory. Output: `alignment/idea-scope-brief-{topic}.html`.
+
+## Constraints
+
+- Keep the skill short and pre-research.
+- Do not write specs, UX variants, UI specs, roadmap phases, or implementation tasks.
+- Do not recommend `$scaffold` unless the user explicitly asks to create a package/app shell before research; normal product flow scaffolds after research, prototype consolidation, spec, roadmap, and phase planning identify the first implementation target. `$scaffold` requires the monorepo pack (`$pack install monorepo` inside Codex, or `npx skillpacks install monorepo` from the project shell).
+- Do not update `tasks/todo.md`.
+- New files do not need archive snapshots. Before replacing an existing idea brief, including slugged briefs, archive it to `docs/history/archive/YYYY-MM-DD/HHMMSS/<original-relative-path>`.
+- Migration: if a project already has `research/concept-brief.md`, `research/concept-brief-interview.md`, or any `research/{slug}/concept-brief*.md` / `research/concept-brief-{slug}*.md` from a prior run, rename it to the `idea-brief` equivalent before re-running. Write only the `idea-brief` names and no longer recognizes the legacy `concept-brief` filenames.
+
+## Default Shipping Contract
+
+Follow the shared shipping contract convention in CLAUDE.md.

package/global/codex/idea-scope-brief/archive/v0.15/SKILL.md

@@ -0,0 +1,159 @@
+---
+name: idea-scope-brief
+description: Shape a rough product or project idea into a scoped brief before customer discovery, market research, specifications, UX, UI, or implementation planning
+type: planning
+version: v0.15
+argument-hint: "[optional rough idea, product thought, or product-path scope]"
+interview_depth: full
+---
+
+# Idea Scope Brief
+
+Invoke as `$idea-scope-brief`.
+
+Use this skill when the user has a half-formed idea and needs it cleaned up enough to enter the normal research and planning workflow. This skill is intentionally pre-customer-discovery: it clarifies the concept, problem hypothesis, beneficiary hypothesis, value wedge, constraints, non-goals, and unknowns, but does not select a validated target-customer segment, analyze competitors, define UX/UI, choose architecture, or write implementation specs.
+
+## Process
+
+### 0. Product-Path Scope Resolution
+
+Resolve research scope by product path before using code or app structure as a hint:
+
+1. If `$ARGUMENTS` names a non-archived `research/{slug}/` directory or a product-path ID whose `scope_path` points there, use that path. Treat `{slug}` as the product/app name, not the customer, audience, or segment label.
+2. If `$ARGUMENTS` names only `research/_archive/{slug}/` or a manifest entry with `status: archived` or legacy `status: abandoned`, stop and warn that the path is archived; do not write or update scoped outputs there.
+3. Read `research/.progress.yaml` when present. Normalize legacy `active_path` to `active_paths` on read and write back `active_paths` on manifest updates. Treat legacy `abandoned` as `archived`; exclude `archived`, `abandoned`, `deferred`, `revisit_candidate`, `promoted`, and any `scope_path` under `research/_archive/` from active target selection.
+4. If active product paths exist in the manifest, use those paths. If multiple active paths exist, ask which one to target unless this skill explicitly supports cross-path output.
+5. If no active manifest target exists, list non-archived product directories under `research/`, excluding `research/_archive/` and dot directories. Auto-select only when exactly one exists; ask when multiple exist.
+6. If no product directories exist, use flat `research/` single-product mode.
+7. Detect monorepo/app/package structure only as a secondary hint. Suggest creating a missing `research/{slug}/` product path when code clearly exposes an app, but do not require code or monorepo detection before using `research/{slug}/`.
+
+When product path `{slug}` is active, read and write research under `research/{slug}/`, specs under `specs/{slug}/`, and treat top-level `research/*.md` files as flat-mode documents or cross-path summaries.
+
+1. **Resolve context**
+   - Read `.agents/project.json` if it exists.
+   - Read README, CLAUDE.md, AGENTS.md, existing `research/`, `specs/`, and task docs when present.
+   - Determine whether the current directory is already a bootstrapped project. Treat it as bootstrapped when it has meaningful `README.md` plus `AGENTS.md` or `CLAUDE.md`; treat it as unbootstrapped when those are missing, placeholder-only, or the user is describing an idea outside any project repo.
+   - If `$ARGUMENTS` contains a rough idea, use it as the starting draft.
+   - If `$ARGUMENTS` names a non-archived `research/{slug}/` product path, use that path. If it names only `research/_archive/{slug}/`, stop and warn that the path is archived.
+   - Determine the concept identity and a normalized concept slug as soon as either is known from `$ARGUMENTS`, repo context, or the interview. Normalize by lowercasing, removing URL suffix noise, replacing non-alphanumeric runs with `-`, trimming leading/trailing `-`, and dropping only project-wide brand prefixes when the remaining word is the actual scoped concept (for example, `poketo.work` -> `work`; `Poketo Core` -> `poketo-core`).
+   - If existing research or the prompt suggests multiple related concepts may exist, prefer slugged output paths over generic filenames. Reserve generic `idea-brief.md` only for a single unambiguous project-level concept.
+   - If no rough idea is available from arguments or repo context, ask the user for the idea in plain language.
+   - Read `research/.progress.yaml` when present. Normalize `active_path` (singular legacy) to `active_paths` (plural list) when reading; treat legacy `abandoned` as `archived` and exclude archived/deferred/revisit/promoted paths plus `research/_archive/` scopes from active target selection. Treat `active_paths` as the current product/app/customer focuses and `product_paths[]` as parked, archived, or promoted product-path state, not git branch state.
+   - When the prompt, repo context, interview, or pivot history surfaces multiple related concepts, apps, product lines, or future pivots, update or propose updates to `research/.progress.yaml` with product-path entries instead of merging them into one generic concept. Use fields: `id`, `label`, `scope_path`, `status`, `source_skill`, `reason`, `archive_reason`, `archived_at`, `promoted_at`, `evidence_refs`, `revisit_trigger`, `next_skill`, `pipeline_stage`, and `last_touched`. Set `pipeline_stage: idea-scope-brief` on entries created by this skill.
+   - Keep the central concept in `active_paths` when it is the current focus. Record related or future concepts as `status: deferred` or `status: revisit_candidate` with a concrete revisit trigger and a likely next skill such as `$customer-discovery <path/audience>`; if `business-research` is not enabled, recommend `$pack install business-research` inside Codex, or `npx skillpacks install business-research` from the project shell, before `$customer-discovery`.
+   - When 3+ product paths exist in the manifest, recommend `$product-line review` to the user for portfolio management; if `business-ops` is not enabled, recommend `$pack install business-ops` inside Codex, or `npx skillpacks install business-ops` from the project shell, before `$product-line`.
+
+2. **Keep the boundary clear**
+   - Do not run customer discovery, competitive analysis, journey mapping, UX variation, UI interview, roadmap, or implementation planning inside this skill.
+   - Do not validate the market with broad web research. Use light repo/context inspection only; downstream research skills own evidence gathering.
+   - Treat every user claim as a hypothesis unless supported by existing project files.
+
+3. **Surface an Idea Assumptions Manifest**
+   - Before deep questioning, present what you think the concept is.
+   - Tag assumptions as `[from prompt]`, `[from repo]`, `[from research]`, or `[inferred]`.
+   - Cover:
+     - concept summary
+     - problem hypothesis
+     - target beneficiary or user hypothesis
+     - product/category guess
+     - value wedge
+     - constraints
+     - non-goals
+     - riskiest unknowns
+   - Ask the user to confirm, correct, or flag assumptions before writing.
+   - Deliver the manifest inline as the final message text of its own turn; ask the confirmation question in the next turn (consistent with the one-question-per-turn cadence). Never emit it only as mid-turn text in a turn that ends with a tool or command call — harness rendering does not guarantee mid-turn text is shown. A confirmation question must never reference content the user has not been shown.
+
+### Market Structure Handoff
+
+During the Idea Assumptions Manifest, if the concept appears marketplace/platform/B2B2C/multi-sided, add a compact `Market Structure Handoff` note:
+
+- Name the apparent sides and the expected value exchange between them.
+- Mark those sides and exchanges as hypotheses, not validated customer segments; do not decide which side is the customer, buyer, or primary target segment here.
+- Keep the source tag for each side as `[from prompt]`, `[from repo]`, or `[inferred]` unless the user provides a correction.
+- If the concept appears single-sided, omit the handoff or state that no marketplace/platform/B2B2C/multi-sided handoff is apparent.
+
+4. **Interview until concept-ready**
+   - Codex interview cadence is one primary decision question per turn by default. Use short follow-up bullets only when they clarify the same decision, not to batch unrelated questions.
+   - Resolve only concept-level ambiguity:
+     - what problem exists
+     - who might care
+     - what outcome changes for them
+     - what makes the idea different enough to investigate
+     - what must stay out of scope
+     - what constraints are real now
+   - When unsure, recommend a practical default and clearly mark it as an assumption.
+
+5. **Coverage checkpoint**
+   - Present the final concept summary, unknowns, and readiness for customer discovery.
+   - Restate the resolved concept identity, slug, and exact output paths before writing.
+   - If the conversation pivoted from the initial concept to a different central concept, write the pivoted concept to its own slugged brief and preserve the initial concept as a related or future concept in the brief and interview log. Do not merge both concepts into one generic project-level brief.
+   - Ask whether any core premise, constraint, or non-goal is wrong before writing.
+
+6. **Build pre-approval alignment preview**
+   - Before writing any canonical `research/**/idea-brief.md`, `research/**/idea-brief-interview.md`, legacy flat `research/idea-brief-{slug}.md` variant, or `research/.progress.yaml`, build `alignment/idea-scope-brief-{topic}.html` as the review artifact.
+   - The HTML page must render the Idea/Concept Assumptions Manifest, artifact destinations, proposed file changes, coverage checkpoint, and approval gates, including any Market Structure Handoff.
+   - Attempt to open the page in the browser and point the user at the repo-relative path.
+   - Treat coverage-checkpoint confirmation as non-final; it only confirms the draft scope is ready to preview. Only final compiled YAML from the alignment page authorizes canonical writes.
+   - Before compiled YAML approval, the next action is review or revision of the HTML alignment page. Do not include `Recommended next skill`, `Recommended next command`, or downstream routing language until after final compiled YAML approval has been provided and the approved artifacts below have been written or updated.
+   - When feedback-only YAML is provided, revise the alignment page and ask again; do not write canonical artifacts until final compiled YAML approval is provided.
+
+### Review-Only Product Path Approval
+
+When the user approves a product-path fork or split at the alignment page level but explicitly withholds canonical-write approval (e.g., "review only, do not write canonical files"):
+
+1. **Do not write canonical files.** Keep `research/.progress.yaml`, `research/{slug}/idea-brief.md`, and `research/{slug}/idea-brief-interview.md` unchanged.
+2. **Render fully in the alignment page.** The proposed manifest entry, idea brief sections, and interview log for the review-only path must be rendered in full in the alignment page HTML — not summarized, linked, or embedded.
+3. **Mark the page as review-only-approved.** Set `approval_status: review-only-approved` in the alignment page status block. This is distinct from `confirmed` (canonical artifacts written) and `review` (awaiting any approval).
+4. **Downstream treatment.** Downstream skills must treat a review-only-approved path as provisional: it may be referenced as concept context, but it is not a canonical product path until manifest approval is later granted via a subsequent alignment cycle. See the provisional-path evidence rule in customer-discovery and competitive-analysis contracts.
+
+## Output
+
+Before writing anything in this section, verify the alignment page has final compiled YAML approval. Do not write canonical idea briefs, interview logs, or `research/.progress.yaml` until `alignment/idea-scope-brief-{topic}.html` has been reviewed and the user has provided final compiled YAML approval. Coverage-checkpoint confirmation is not final approval and does not authorize these writes.
+
+Write:
+
+- For one unambiguous project-level concept only: `research/idea-brief.md` and `research/idea-brief-interview.md`.
+- When a product identity is known, multiple concepts exist or may exist, or a pivot occurs: prefer `research/{slug}/idea-brief.md` and `research/{slug}/idea-brief-interview.md`; preserve flat `research/idea-brief-{slug}.md` only as legacy compatibility when no product path is being introduced.
+- If `$ARGUMENTS` names a non-archived product path, use unsuffixed scoped files under `research/{slug}/`: `research/{slug}/idea-brief.md` and `research/{slug}/idea-brief-interview.md`.
+- `research/.progress.yaml` — create or update only when multiple concepts, product paths, product lines, product-path scopes, or pivots are present. Use `product_paths` terminology instead of branch terminology.
+
+The idea brief must include:
+
+- `## Summary`
+- `## Problem Hypothesis`
+- `## Beneficiary Hypothesis`
+- `## Product Category Guess`
+- `## Value Wedge`
+- `## Constraints`
+- `## Non-Goals`
+- `## Assumptions And Unknowns`
+- `## Customer Discovery Readiness`
+- `## Next Steps`
+
+The `## Customer Discovery Readiness` section must state whether the concept is ready for `$customer-discovery`, what inputs `$customer-discovery` should use, and which assumptions should be tested first. If a Market Structure Handoff exists, include the apparent sides and value exchange as explicit inputs for `$customer-discovery` to validate or refute.
+
+The `## Next Steps` section must recommend exactly one primary command:
+
+- If the concept appears to be a business app or user-facing product and the business research lane is not enabled: `$pack install business-research` inside Codex, or `npx skillpacks install business-research` from the project shell — this installs the research skills (customer discovery, competitive analysis, value prop, positioning, lean canvas) needed before any repo bootstrapping or development.
+- If `business-research` or the compatibility `business-app` alias is enabled: `$customer-discovery`
+- If the concept already has customer-discovery/market evidence but needs journey, onboarding, conversion, or retention planning: `$pack install customer-lifecycle` inside Codex, or `npx skillpacks install customer-lifecycle` from the project shell.
+- If project type is unclear: `$pack recommend`
+
+Include 1-3 other options only when they are materially useful.
+
+### Alignment Page
+
+When this skill produces durable deliverables (research, specs, plans, reports, prototypes, or any document output), build a full-depth HTML alignment page following `ALIGNMENT-PAGE.md` in this skill's directory. Output: `alignment/idea-scope-brief-{topic}.html`.
+
+## Constraints
+
+- Keep the skill short and pre-research.
+- Do not write specs, UX variants, UI specs, roadmap phases, or implementation tasks.
+- Do not recommend `$scaffold` unless the user explicitly asks to create a package/app shell before research; normal product flow scaffolds after research, prototype consolidation, spec, roadmap, and phase planning identify the first implementation target. `$scaffold` requires the monorepo pack (`$pack install monorepo` inside Codex, or `npx skillpacks install monorepo` from the project shell).
+- Do not update `tasks/todo.md`.
+- New files do not need archive snapshots. Before replacing an existing idea brief, including slugged briefs, archive it to `docs/history/archive/YYYY-MM-DD/HHMMSS/<original-relative-path>`.
+- Migration: if a project already has `research/concept-brief.md`, `research/concept-brief-interview.md`, or any `research/{slug}/concept-brief*.md` / `research/concept-brief-{slug}*.md` from a prior run, rename it to the `idea-brief` equivalent before re-running. Write only the `idea-brief` names and no longer recognizes the legacy `concept-brief` filenames.
+
+## Default Shipping Contract
+
+Follow the shared shipping contract convention in CLAUDE.md.

package/global/codex/init-agentic-skills/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog
 
+## v0.7 - 2026-06-11
+
+- Added npm-aware project-shell pack install guidance alongside Codex `$pack install` guidance for project-local domain workflows.
+
 ## v0.6
 
 - Replace generic fresh-session guidance with the runner-specific skill reload path: Claude Code `/reload-skills`, `/clear`, then restart fallback; Codex fresh CLI session when `$` discovery remains stale.

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

@@ -2,7 +2,7 @@
 name: init-agentic-skills
 description: Initialize this agentic-skills checkout on a developer machine by running the repository init script, verify global managed skill installs, uninstall repo-managed installs when requested, and route project-local pack setup to the pack skill. Use when Codex needs to make all global agentic-skills skills available on the current machine, repair stale installs, confirm initialization status, or explain how to enable packs for a project.
 type: ops
-version: v0.6
+version: v0.7
 argument-hint: "[init|status|doctor|update|latest|--uninstall]"
 ---
 
@@ -10,7 +10,7 @@ argument-hint: "[init|status|doctor|update|latest|--uninstall]"
 
 Invoke as `$init-agentic-skills`.
 
-Initialize this `agentic-skills` checkout on the current machine by installing global core skills for both Claude and Codex. Active installs are repo-managed directories that expose the canonical `SKILL.md` and exclude `archive/`; copied managed launchers resolve this checkout through `.agentic-skills-managed` provenance. Pinned installs intentionally point at `archive/<version>`. Keep domain packs project-local; use `$pack` from the target project when packs are needed.
+Initialize this `agentic-skills` checkout on the current machine by installing global core skills for both Claude and Codex. Active installs are repo-managed directories that expose the canonical `SKILL.md` and exclude `archive/`; copied managed launchers resolve this checkout through `.agentic-skills-managed` provenance. Pinned installs intentionally point at `archive/<version>`. Keep domain packs project-local; use `$pack` from the target project or `npx skillpacks install <pack-or-skill>` from the project shell when packs are needed.
 
 ## Process
 
@@ -24,7 +24,7 @@ Initialize this `agentic-skills` checkout on the current machine by installing g
 2. Report the initializer command, the Claude and Codex skill directories, installed/skipped counts, and warnings about non-repo-managed collisions.
 3. Explain pack access separately:
    - Do not install `packs/*` globally.
-   - In the project that needs domain workflows, run `$pack` for guided setup or `$pack install <pack-or-skill>` for an explicit pack or individual pack skill.
+   - In the project that needs domain workflows, run `$pack` for guided setup, `$pack install <pack-or-skill>` inside Codex for an explicit pack or individual pack skill, or `npx skillpacks install <pack-or-skill>` from the project shell.
    - If a project already has `.agents/project.json`, use `$pack refresh` after this global initialization to recreate local pack skill roots.
 4. If the active session still cannot see a newly installed or refreshed skill, report the skill-visibility reload path:
    - Claude Code: run `/reload-skills` first; `/clear` starts a new empty-context conversation and can pick up the refreshed registry; restart if the top-level `.claude/skills` directory did not exist at session start or the skill is still invisible.
@@ -56,4 +56,3 @@ Initialize this `agentic-skills` checkout on the current machine by installing g
 ## Default Shipping Contract
 
 Follow the shared shipping contract convention in CLAUDE.md.
-

package/global/codex/init-agentic-skills/archive/v0.6/SKILL.md

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

package/global/codex/pack/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog
 
+## v0.7 - 2026-06-11
+
+- Added published `npx skillpacks install` alternatives to pack and individual-skill install guidance while preserving source-checkout `scripts/pack.sh` and Codex `$pack` routes.
+
 ## v0.6
 
 - Updated individual business-discovery skill install/remove examples to use `customer-discovery` as the tracked skill name.