skillpacks 0.1.1 → 0.1.2

package/packs/business-ops/codex/runway-model/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog
 
+## v0.4 - 2026-06-12
+
+- Standardized active pack and skill install guidance on `npx skillpacks install <pack-or-skill>` instead of agent-native `/pack install` or `$pack install` recommendations.
+
 ## v0.3 - 2026-06-10
 
 - Added npm-aware install-route guidance for business-ops cross-pack recommendations, preserving `$pack install <pack>` inside Codex while offering `npx skillpacks install <pack>` from the project shell.

package/packs/business-ops/codex/runway-model/SKILL.md

@@ -2,15 +2,15 @@
 name: runway-model
 description: Financial runway & unit economics tracker — burn rate, revenue trajectory, runway in months, scenario modeling
 type: analysis
-version: v0.3
+version: v0.4
 argument-hint: "[file path to financials, pasted data, or empty to be prompted]"
-interview_depth: light
+context_intake: scoped
 visual_tier: visual
 ---
 
 ## Pack Availability Guard
 
-When recommending a skill from another pack, verify the target pack is installed via `.agents/project.json` `enabled_packs`. If it is not enabled, recommend `$pack install <pack>` inside Codex, or `npx skillpacks install <pack>` from the project shell. After install, tell Codex users to start a fresh Codex CLI session if the `$` skill list remains stale. Global skills are always valid. Skills from this same pack are valid because the current skill is already running from that pack.
+When recommending a skill from another pack, verify the target pack is installed via `.agents/project.json` `enabled_packs`. If it is not enabled, recommend `npx skillpacks install <pack>` from the project shell. After install, tell Codex users to start a fresh Codex CLI session if the `$` skill list remains stale. Global skills are always valid. Skills from this same pack are valid because the current skill is already running from that pack.
 
 # Runway Model — Financial Runway & Unit Economics
 

package/packs/business-ops/codex/runway-model/archive/v0.3/SKILL.md

@@ -0,0 +1,278 @@
+---
+name: runway-model
+description: Financial runway & unit economics tracker — burn rate, revenue trajectory, runway in months, scenario modeling
+type: analysis
+version: v0.3
+argument-hint: "[file path to financials, pasted data, or empty to be prompted]"
+interview_depth: light
+visual_tier: visual
+---
+
+## Pack Availability Guard
+
+When recommending a skill from another pack, verify the target pack is installed via `.agents/project.json` `enabled_packs`. If it is not enabled, recommend `$pack install <pack>` inside Codex, or `npx skillpacks install <pack>` from the project shell. After install, tell Codex users to start a fresh Codex CLI session if the `$` skill list remains stale. Global skills are always valid. Skills from this same pack are valid because the current skill is already running from that pack.
+
+# Runway Model — Financial Runway & Unit Economics
+
+Invoke as `$runway-model`.
+
+Simple financial model: burn rate, revenue trajectory, runway in months, and scenario modeling. Takes real numbers, projects forward with optimistic/realistic/pessimistic scenarios. Append-only updates for tracking over time.
+
+## Soft Prerequisites
+
+- Read `research/monetization.md` if it exists — theoretical unit economics and pricing to compare against actuals
+- Read `research/metrics.md` if it exists — growth rate targets for projections
+- Read `research/cohort-review-*.md` if any exist — real performance data for revenue trajectory
+- Read `research/gtm.md` if it exists — channel costs for CAC calculations
+
+## 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 ICP, 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. Load Context & Data
+
+**Load research context:** Read all soft prerequisite files.
+
+**Ingest financial data:**
+Check `$ARGUMENTS`:
+- **File path provided**: Read the file
+- **Text provided**: Parse the data directly
+- **Empty**: Gather the numbers from the user. If the session is already in Plan mode and there are 2-3 concrete input-source choices, prefer `request_user_input`; otherwise ask in plain text.
+
+**Required inputs** (ask for each that's missing):
+- Monthly burn rate (total expenses)
+- Current cash/bank balance
+- Monthly revenue (if any)
+- Revenue growth rate (if applicable)
+- Team size and key cost categories
+
+**Nice-to-have inputs:**
+- Detailed cost breakdown (salaries, infrastructure, tools, marketing)
+- Customer count and ARPU
+- CAC by channel
+- Churn rate
+- Expected cost changes (new hires, infrastructure scaling)
+
+### 2. Calculate Core Metrics
+
+**Runway calculation:**
+- **Gross burn**: Total monthly expenses
+- **Net burn**: Expenses minus revenue
+- **Runway (months)**: Cash balance ÷ net burn
+- **Zero-cash date**: Projected date when cash runs out
+
+**Unit economics (if revenue exists):**
+- **MRR / ARR**: Monthly/annual recurring revenue
+- **ARPU**: Average revenue per user
+- **CAC**: Customer acquisition cost (if channel spend data available)
+- **LTV**: Lifetime value (ARPU × average lifespan, or ARPU ÷ monthly churn rate)
+- **LTV:CAC ratio**: Is acquisition sustainable?
+- **Payback period**: Months to recover CAC
+- **Gross margin**: Revenue minus cost of delivery
+
+Compare actuals against theoretical estimates from `research/monetization.md` if it exists.
+
+### 3. Scenario Modeling
+
+Build three scenarios projecting 12 months forward:
+
+**Pessimistic** (what if things go wrong):
+- Revenue grows at 50% of current rate (or flat)
+- Costs increase 10-20% (unexpected expenses, needed hires)
+- Churn increases
+- Runway: [months]
+
+**Realistic** (current trajectory continues):
+- Revenue grows at current rate
+- Costs grow as planned
+- Churn stays flat
+- Runway: [months]
+
+**Optimistic** (what if things go well):
+- Revenue grows at 150-200% of current rate
+- Costs stay controlled
+- Churn decreases
+- Runway: [months]
+
+For each scenario, show monthly projections for cash balance, revenue, and expenses.
+
+### 4. Identify Critical Decisions
+
+Based on the model:
+- **Break-even point**: When does revenue cover expenses? (per scenario)
+- **Hiring runway**: Can you afford to hire? When?
+- **Marketing budget**: How much can you spend on acquisition?
+- **Runway triggers**: At what cash balance should you raise, cut costs, or change strategy?
+- **Revenue milestones needed**: What MRR is needed to extend runway to [target]?
+
+### 5. Present & Validate
+
+Present to the user. If the session is already in Plan mode and there are 2-3 concrete choices, prefer `request_user_input`; otherwise ask in plain text:
+- Core metrics summary
+- Three scenarios with runway projections
+- Critical decisions and trigger points
+
+Ask:
+- "Do these numbers match your records? Any costs or revenue I'm missing?"
+- "Are the scenario assumptions realistic? Too conservative or too aggressive?"
+
+Incorporate feedback before proceeding.
+
+### 6. Populate Next Steps
+
+Include 3–5 applicable items with "Pick one:" framing:
+
+- IF runway < 6 months: Prioritize revenue — `$experiment` to validate fastest path to revenue, or cut costs
+- IF unit economics unhealthy (LTV:CAC < 3): `$monetization` — Revisit pricing or acquisition strategy
+- IF no `research/cohort-review-*.md`: `$cohort-review` — Get real performance data to improve projections
+- IF actuals diverge from monetization estimates: `$monetization` — Update strategy with real data
+- ALWAYS: `$roadmap` — Ensure build plan accounts for runway constraints
+
+### 7. Write Output
+
+Present final model to user. Ask:
+- "Ready to write this? Anything to adjust?"
+
+Only after confirmation, write the output file.
+
+## Output
+
+### `research/runway-model.md` (or `research/{slug}/runway-model.md`)
+
+Append-only — each update adds a new section at the top (below the header). Previous snapshots remain for historical tracking.
+
+```markdown
+# Runway Model
+
+> Last updated: [current date]
+> Snapshots: [total count]
+
+## Latest Snapshot: [Month Year]
+
+> Data source: [where the numbers came from]
+> As of: [date of financial data]
+
+### Core Metrics
+
+| Metric | Value | vs. Last Snapshot |
+|--------|-------|-------------------|
+| Cash balance | $[amount] | [+/- change] |
+| Monthly revenue (MRR) | $[amount] | [+/- change] |
+| Gross burn | $[amount/mo] | [+/- change] |
+| Net burn | $[amount/mo] | [+/- change] |
+| Runway | [months] | [+/- change] |
+| Zero-cash date | [date] | [+/- change] |
+
+### Unit Economics
+
+| Metric | Actual | Target (from monetization) | Status |
+|--------|--------|---------------------------|--------|
+| ARPU | $[amount] | $[target] | [On/Below/Above] |
+| CAC | $[amount] | $[target] | [On/Below/Above] |
+| LTV | $[amount] | $[target] | [On/Below/Above] |
+| LTV:CAC | [ratio] | [target] | [Healthy/Unhealthy] |
+| Payback period | [months] | [target] | [On/Below/Above] |
+| Gross margin | [%] | [target] | [On/Below/Above] |
+
+### Cost Breakdown
+
+| Category | Monthly Cost | % of Total | Trend |
+|----------|-------------|------------|-------|
+| Salaries/contractors | $[amount] | [%] | [↑↓→] |
+| Infrastructure | $[amount] | [%] | [↑↓→] |
+| Tools & services | $[amount] | [%] | [↑↓→] |
+| Marketing/ads | $[amount] | [%] | [↑↓→] |
+| Other | $[amount] | [%] | [↑↓→] |
+
+### Revenue Breakdown
+
+| Source | MRR | Customers | ARPU | Growth |
+|--------|-----|-----------|------|--------|
+| [tier/product] | $[amount] | [count] | $[amount] | [%/mo] |
+
+### 12-Month Projections
+
+#### Pessimistic
+| Month | Revenue | Expenses | Net Burn | Cash Balance |
+|-------|---------|----------|----------|-------------|
+| [M1] | $[amt] | $[amt] | $[amt] | $[amt] |
+| ... | | | | |
+**Runway**: [months] | **Break-even**: [month or "not in window"]
+
+#### Realistic
+| Month | Revenue | Expenses | Net Burn | Cash Balance |
+|-------|---------|----------|----------|-------------|
+| [M1] | $[amt] | $[amt] | $[amt] | $[amt] |
+| ... | | | | |
+**Runway**: [months] | **Break-even**: [month or "not in window"]
+
+#### Optimistic
+| Month | Revenue | Expenses | Net Burn | Cash Balance |
+|-------|---------|----------|----------|-------------|
+| [M1] | $[amt] | $[amt] | $[amt] | $[amt] |
+| ... | | | | |
+**Runway**: [months] | **Break-even**: [month or "not in window"]
+
+### Assumptions
+[List every assumption behind the projections — growth rates, churn rates, cost changes, hiring plans]
+
+### Critical Decisions
+
+| Trigger | Condition | Action |
+|---------|-----------|--------|
+| Low runway | Cash < $[amount] or < [months] runway | [action: raise, cut, pivot] |
+| Break-even path | Need $[MRR] by [date] | [what must happen to get there] |
+| Hiring decision | Can afford hire when runway > [months] | [role and timing] |
+| Marketing budget | Can spend $[amount/mo] on acquisition | [when and how] |
+
+### Next Steps
+
+Pick one:
+- [conditional items from step 6]
+
+---
+
+[Previous snapshots remain below, newest first]
+```
+
+Create the `research/` directory if it doesn't exist.
+
+## Task Classification
+
+When this skill produces follow-up work, file it by execution semantics:
+
+- Immediately actionable implementation or documentation work goes in `tasks/todo.md`.
+- Human-only external actions tied to automated steps go in `tasks/manual-todo.md` with `_(blocks: Step N.X)_` or `_(after: Step N.X)_`; repo edits, SDK wiring, generated assets, local commands, tests, audits, and authenticated CLI/API work stay in `tasks/todo.md`.
+- One-time condition-gated records, baselines, or future measurements go in `tasks/record-todo.md` with source, condition, non-blocking reason, evidence, and promotion rule.
+- Cadence-based reviews, playtests, adoption checks, investor updates, retros, or docs-health checks go in `tasks/recurring-todo.md` with cadence, owner/agent, next due, evidence path, and escalation conditions.
+- Do not put non-blocking records or recurring obligations in `tasks/todo.md` unless they have been explicitly promoted into current execution work.
+
+## Constraints
+
+- **Real numbers only.** Do not fabricate financial data. If numbers aren't provided, ask for them.
+- **Append-only.** Previous snapshots are never deleted or modified. Only add new snapshots at the top.
+- **State assumptions.** Every projection must list its assumptions explicitly. Never present projections as predictions.
+- **Present before writing.** Never write output files until the model has been presented and validated.
+- **Conservative by default.** When estimating, err on the conservative side. Optimistic projections should be labeled clearly.
+- **No investment advice.** This is a planning tool, not financial advice. Note this in the output.
+- **Privacy-aware.** Financial data is sensitive. Do not log raw financial data to search logs or interview logs.
+
+## 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/runway-model-{topic}.html`.
+
+## Default Shipping Contract
+
+Follow the shared shipping contract convention in CLAUDE.md.

package/packs/business-ops/codex/scale-audit/ALIGNMENT-PAGE.md

@@ -9,6 +9,8 @@ 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.
 
+**Context intake.** This skill declares `context_intake: artifact_only` (Artifact-driven). Work from concrete artifacts, data, logs, or existing instructions by default; ask concise clarification questions only when the available artifacts are missing, contradictory, or unsafe to interpret.
+
 **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.
@@ -57,7 +59,9 @@ The tier is set per skill via `visual_tier` in SKILL.md frontmatter (or detected
 
 **Report-only research gates.** For report-only or pre-approval research skills, the first `review` alignment page must explicitly contain proposed research scope, source plan, assumptions/confidence, recommended output path, proposed file changes, and approval gates before synthesized research begins and before any working packet, canonical research, spec, or task file is created or updated.
 
-**Staged research workflow.** Heavy report-first research uses a scope-first three-stage approval workflow. Stage 1 is minimal scope discovery only: inspect enough repository, user, and source context to propose research scope, source plan, assumptions, output paths, and approval questions. Build the `review` alignment page before synthesized research. The page must render the proposed scope, available source categories, known context, assumptions/confidence, proposed working-packet and canonical output paths, and research-scope approval gates. Stop for final compiled response YAML approval of the research scope. Do not synthesize findings, rank candidates, recommend a path, or create working packets, canonical research, spec, or task files in Stage 1. Stage 2 starts only after final compiled response YAML approves the research scope with no unresolved `needs-clarification`, unresolved `down` feedback, or other unresolved negative feedback. Perform the synthesized research, run required source/code checks, and write only a non-canonical working packet. Flat mode uses `research/_working/preliminary-scale-audit-research.md`; product-path mode uses `research/{slug}/_working/preliminary-scale-audit-research.md`. Existing raw evidence or search-log outputs may remain as supporting evidence when the skill contract already requires them, but synthesized deliverables stay in the working packet. Update the same `review` alignment page so it renders the full preliminary packet, evidence matrix, assumptions/confidence register, source coverage gaps, proposed canonical file changes, and artifact approval gates. Partial compiled responses revise the working packet and review page, then remain in Stage 2. Stage 3 consumes final compiled response YAML for artifact approval only when it has `approval_status: ready-for-agent-review` and no unresolved `needs-clarification`, unresolved `down` feedback, or other unresolved negative feedback. Apply approved edits first, archive the working packet to `docs/history/archive/YYYY-MM-DD/HHMMSS/<original-working-path>`, remove the active working packet, write the approved canonical artifacts to the unchanged output paths, and convert the page to `confirmed` with the approval record preserved.
+**Staged research workflow.** Heavy report-first research uses a scope-first three-stage approval workflow. Stage 1 is minimal scope discovery only: inspect enough repository, user, and source context to propose research scope, source plan, assumptions, output paths, and approval questions. Build the `review` alignment page before synthesized research. The page must render the proposed scope, available source categories, known context, assumptions/confidence, proposed working-packet and canonical output paths, research-scope approval gates, and a `Stage 2 Preview / Expected Review Format` section that shows the future Stage 2 review shape before research starts. Stop for final compiled response YAML approval of the research scope. Do not synthesize findings, rank candidates, recommend a path, or create working packets, canonical research, spec, or task files in Stage 1. Stage 2 starts only after final compiled response YAML approves the research scope with no unresolved `needs-clarification`, unresolved `down` feedback, or other unresolved negative feedback. Perform the synthesized research, run required source/code checks, and write only a non-canonical working packet. Flat mode uses `research/_working/preliminary-scale-audit-research.md`; product-path mode uses `research/{slug}/_working/preliminary-scale-audit-research.md`. Existing raw evidence or search-log outputs may remain as supporting evidence when the skill contract already requires them, but synthesized deliverables stay in the working packet. Update the same `review` alignment page so it renders the complete working-packet substance as structured HTML review UI: purpose-built sections, tables, matrices, gates, cards, and tier-appropriate charts or diagrams that preserve every packet section, finding, caveat, and decision detail without summary loss. Raw Markdown packet text may appear only as a supplemental source view after the rendered review UI; do not make a `Full Preliminary Packet` or `Full Working Packet` raw Markdown dump, giant `<pre><code>` block, link-only view, or source-only view the primary review surface. Include the evidence matrix, assumptions/confidence register, source coverage gaps, proposed canonical file changes, and artifact approval gates. Partial compiled responses revise the working packet and review page, then remain in Stage 2. Stage 3 consumes final compiled response YAML for artifact approval only when it has `approval_status: ready-for-agent-review` and no unresolved `needs-clarification`, unresolved `down` feedback, or other unresolved negative feedback. Apply approved edits first, archive the working packet to `docs/history/archive/YYYY-MM-DD/HHMMSS/<original-working-path>`, remove the active working packet, write the approved canonical artifacts to the unchanged output paths, and convert the page to `confirmed` with the approval record preserved.
+
+**Stage 2 review-page template.** Stage 1 scope-review pages must include a `Stage 2 Preview / Expected Review Format` section that previews the exact section sequence, table shapes, evidence treatment, visual density, and approval gates the user will see after research; make it specific enough for the user to flag preferred content formats, grouping, labels, visuals, and evidence density before the agent does heavy research. After scope approval and research, the Stage 2 review page must include these sections as structured HTML, not as raw Markdown dumps: `Research Scope Approved` status block with approved scope, source plan, output paths, and unresolved caveats; `Executive Findings` or a skill-specific top-findings section with confidence labels; `Evidence Matrix` mapping claim, evidence/source/path, inference, confidence, assumptions, and decision impact; `Working Packet Review` with the complete working-packet substance rendered as purpose-built HTML sections, lists, tables, matrices, cards, and tier-appropriate charts or diagrams; `Alternatives / Rejected or Lower-Confidence Findings`; `Source Coverage & Gaps`; `Assumptions / Confidence Register`; `Proposed Canonical Artifacts & File Changes`; a required `User Format Preferences` gate asking whether the layout, tables, grouping, visuals, labels, and evidence density match expectations; and a required `Final Artifact Approval` gate for Stage 3 readiness. Raw Markdown packet text, search logs, or source notes may appear only as supplemental source views after the rendered review UI and never replace the Stage 2 review sections.
 
 **Visual tier rendering.** This skill's alignment page uses the `visual` tier. Inline charts and diagrams are rendered via self-contained Canvas/SVG within the HTML file. Use the alignment chart snippet library (`scripts/alignment-chart-snippets.js`) as reference — copy needed chart functions directly into the page's `<script>` block. Charts must read CSS variables (`--chart-1` through `--chart-8`) for the data visualization palette. Every chart must include a `<table>` fallback, `aria-label` on canvas/SVG, and a "View as table" toggle. Data is embedded as inline JSON — no external fetches.
 

package/packs/business-ops/codex/scale-audit/CHANGELOG.md

@@ -1,5 +1,9 @@
 # Changelog
 
+## v0.5 - 2026-06-12
+
+- Standardized active pack and skill install guidance on `npx skillpacks install <pack-or-skill>` instead of agent-native `/pack install` or `$pack install` recommendations.
+
 ## v0.4 - 2026-06-10
 
 - Added npm-aware install-route guidance for business-ops cross-pack recommendations, preserving `$pack install <pack>` inside Codex while offering `npx skillpacks install <pack>` from the project shell.

package/packs/business-ops/codex/scale-audit/SKILL.md

@@ -2,14 +2,14 @@
 name: scale-audit
 description: Evaluate codebase against enterprise ICP for production readiness, compliance, and multi-stakeholder journey coverage
 type: analysis
-version: v0.4
-interview_depth: none
+version: v0.5
+context_intake: artifact_only
 visual_tier: visual
 ---
 
 ## Pack Availability Guard
 
-When recommending a skill from another pack, verify the target pack is installed via `.agents/project.json` `enabled_packs`. If it is not enabled, recommend `$pack install <pack>` inside Codex, or `npx skillpacks install <pack>` from the project shell. After install, tell Codex users to start a fresh Codex CLI session if the `$` skill list remains stale. Global skills are always valid. Skills from this same pack are valid because the current skill is already running from that pack.
+When recommending a skill from another pack, verify the target pack is installed via `.agents/project.json` `enabled_packs`. If it is not enabled, recommend `npx skillpacks install <pack>` from the project shell. After install, tell Codex users to start a fresh Codex CLI session if the `$` skill list remains stale. Global skills are always valid. Skills from this same pack are valid because the current skill is already running from that pack.
 
 # Scale Audit — Enterprise Production Readiness
 

package/packs/business-ops/codex/scale-audit/archive/v0.4/SKILL.md

@@ -0,0 +1,90 @@
+---
+name: scale-audit
+description: Evaluate codebase against enterprise ICP for production readiness, compliance, and multi-stakeholder journey coverage
+type: analysis
+version: v0.4
+interview_depth: none
+visual_tier: visual
+---
+
+## Pack Availability Guard
+
+When recommending a skill from another pack, verify the target pack is installed via `.agents/project.json` `enabled_packs`. If it is not enabled, recommend `$pack install <pack>` inside Codex, or `npx skillpacks install <pack>` from the project shell. After install, tell Codex users to start a fresh Codex CLI session if the `$` skill list remains stale. Global skills are always valid. Skills from this same pack are valid because the current skill is already running from that pack.
+
+# Scale Audit — Enterprise Production Readiness
+
+Invoke as `$scale-audit`.
+
+Automated analysis that evaluates the codebase against `research/enterprise-icp.md`. Identifies gaps for enterprise deals — stakeholder journey coverage, compliance, infrastructure, and operations.
+
+## Prerequisites
+
+`research/enterprise-icp.md` (or `research/{slug}/enterprise-icp.md`) must exist. If not, tell the user to run `$enterprise-icp` first.
+
+## 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 ICP, 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. Load Context & Evaluate
+
+1. Read `research/enterprise-icp.md` (or `research/{slug}/enterprise-icp.md`), `research/icp.md` (or `research/{slug}/icp.md`), `research/mvp-gap.md` (or `research/{slug}/mvp-gap.md`) (if they exist), codebase, and in-progress/advisory work from `tasks/roadmap.md`, `tasks/todo.md`, `tasks/manual-todo.md`, `tasks/record-todo.md`, and `tasks/recurring-todo.md` (if they exist).
+2. Evaluate the codebase across:
+   - **Per-Persona Journey Coverage** — Can each stakeholder complete their workflow?
+   - **Onboarding Gaps** — Self-serve, team, SSO-provisioned, migration, training
+   - **Compliance Readiness** — SOC 2, GDPR, HIPAA, encryption, secrets management
+   - **Infrastructure Readiness** — Multi-tenancy, scaling, DR, observability, CI/CD
+   - **Operational Readiness** — Incident response, SLA monitoring, support, customer success
+   - **Escalated Startup Gaps** — Unresolved MVP gaps now critical at enterprise scale
+3. Tag gaps: `hard-blocker`, `soft-blocker`, or `differentiator`. Estimate effort (S/M/L/XL).
+
+## Deliverables
+
+- `specs/scale-audit.md` (or `specs/{slug}/scale-audit.md`) — Gap analysis with stakeholder coverage matrix, compliance matrix, priority tags, and `$user-flow-map` prompts for each unspecced flow/design-shape gap
+
+The output file must end with a `## Next Steps` section containing a **Recommended** item and 2–4 other contextual options. Choose the recommendation by the first matching condition:
+
+1. IF any `hard-blocker` lacks flow/design shape or a full implementation spec: `$user-flow-map [top blocker]` — map the highest-priority enterprise blocker into concrete screen flow, decisions, branches, states, and recovery paths before UI/layout planning.
+2. IF enterprise stakeholder journey context is missing: `$journey-map enterprise` — map enterprise stakeholder journeys before sequencing build work.
+3. IF startup gaps escalated and `research/mvp-gap.md` is missing or stale: `$mvp-gap` — re-evaluate startup readiness first.
+4. IF enterprise SLA or compliance gaps lack closure metrics: `$metrics` — define metrics covering enterprise SLAs.
+5. OTHERWISE: `$roadmap` — sequence the already-specced enterprise work into implementation phases.
+
+Only recommend `$roadmap` as the primary next step when every hard-blocker already has a full spec or is already tracked in `tasks/roadmap.md`, `tasks/todo.md`, `tasks/manual-todo.md`, `tasks/record-todo.md`, or `tasks/recurring-todo.md`.
+
+## Task Classification
+
+When this skill produces follow-up work, file it by execution semantics:
+
+- Immediately actionable implementation or documentation work goes in `tasks/todo.md`.
+- Human-only external actions tied to automated steps go in `tasks/manual-todo.md` with `_(blocks: Step N.X)_` or `_(after: Step N.X)_`; repo edits, SDK wiring, generated assets, local commands, tests, audits, and authenticated CLI/API work stay in `tasks/todo.md`.
+- One-time condition-gated records, baselines, or future measurements go in `tasks/record-todo.md` with source, condition, non-blocking reason, evidence, and promotion rule.
+- Cadence-based reviews, playtests, adoption checks, investor updates, retros, or docs-health checks go in `tasks/recurring-todo.md` with cadence, owner/agent, next due, evidence path, and escalation conditions.
+- Do not put non-blocking records or recurring obligations in `tasks/todo.md` unless they have been explicitly promoted into current execution work.
+
+## Constraints
+
+- Analysis only — do not make code changes.
+- Every gap must cite specific evidence.
+- Distinguish "first enterprise deal" from "100th enterprise deal."
+- Include `$user-flow-map <topic>` prompts for gaps lacking flow/design shape or full specs. Use `$ux-variations --layout-mode <topic>` only when flow and UI requirements already exist but layout alternatives are missing.
+- `## Next Steps` must be the final section in the output file, with a recommended next step and 2–4 other contextual options.
+
+## 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/scale-audit-{topic}.html`.
+
+## Default Shipping Contract
+
+Follow the shared shipping contract convention in CLAUDE.md.

package/packs/business-research/claude/competitive-analysis/ALIGNMENT-PAGE.md

@@ -9,6 +9,8 @@ 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.
 
+**Context intake.** This skill declares `context_intake: scoped` (Scoped intake). Ask only the focused questions needed to scope the research or analysis, then validate critical findings before building review artifacts.
+
 **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.
@@ -57,7 +59,9 @@ The tier is set per skill via `visual_tier` in SKILL.md frontmatter (or detected
 
 **Report-only research gates.** For report-only or pre-approval research skills, the first `review` alignment page must explicitly contain proposed research scope, source plan, assumptions/confidence, recommended output path, proposed file changes, and approval gates before synthesized research begins and before any working packet, canonical research, spec, or task file is created or updated.
 
-**Staged research workflow.** Heavy report-first research uses a scope-first three-stage approval workflow. Stage 1 is minimal scope discovery only: inspect enough repository, user, and source context to propose research scope, source plan, assumptions, output paths, and approval questions. Build the `review` alignment page before synthesized research. The page must render the proposed scope, available source categories, known context, assumptions/confidence, proposed working-packet and canonical output paths, and research-scope approval gates. Stop for final compiled response YAML approval of the research scope. Do not synthesize findings, rank candidates, recommend a path, or create working packets, canonical research, spec, or task files in Stage 1. Stage 2 starts only after final compiled response YAML approves the research scope with no unresolved `needs-clarification`, unresolved `down` feedback, or other unresolved negative feedback. Perform the synthesized research, run required source/code checks, and write only a non-canonical working packet. Flat mode uses `research/_working/preliminary-competitive-analysis-research.md`; product-path mode uses `research/{slug}/_working/preliminary-competitive-analysis-research.md`. Existing raw evidence or search-log outputs may remain as supporting evidence when the skill contract already requires them, but synthesized deliverables stay in the working packet. Update the same `review` alignment page so it renders the full preliminary packet, evidence matrix, assumptions/confidence register, source coverage gaps, proposed canonical file changes, and artifact approval gates. Partial compiled responses revise the working packet and review page, then remain in Stage 2. Stage 3 consumes final compiled response YAML for artifact approval only when it has `approval_status: ready-for-agent-review` and no unresolved `needs-clarification`, unresolved `down` feedback, or other unresolved negative feedback. Apply approved edits first, archive the working packet to `docs/history/archive/YYYY-MM-DD/HHMMSS/<original-working-path>`, remove the active working packet, write the approved canonical artifacts to the unchanged output paths, and convert the page to `confirmed` with the approval record preserved.
+**Staged research workflow.** Heavy report-first research uses a scope-first three-stage approval workflow. Stage 1 is minimal scope discovery only: inspect enough repository, user, and source context to propose research scope, source plan, assumptions, output paths, and approval questions. Build the `review` alignment page before synthesized research. The page must render the proposed scope, available source categories, known context, assumptions/confidence, proposed working-packet and canonical output paths, research-scope approval gates, and a `Stage 2 Preview / Expected Review Format` section that shows the future Stage 2 review shape before research starts. Stop for final compiled response YAML approval of the research scope. Do not synthesize findings, rank candidates, recommend a path, or create working packets, canonical research, spec, or task files in Stage 1. Stage 2 starts only after final compiled response YAML approves the research scope with no unresolved `needs-clarification`, unresolved `down` feedback, or other unresolved negative feedback. Perform the synthesized research, run required source/code checks, and write only a non-canonical working packet. Flat mode uses `research/_working/preliminary-competitive-analysis-research.md`; product-path mode uses `research/{slug}/_working/preliminary-competitive-analysis-research.md`. Existing raw evidence or search-log outputs may remain as supporting evidence when the skill contract already requires them, but synthesized deliverables stay in the working packet. Update the same `review` alignment page so it renders the complete working-packet substance as structured HTML review UI: purpose-built sections, tables, matrices, gates, cards, and tier-appropriate charts or diagrams that preserve every packet section, finding, caveat, and decision detail without summary loss. Raw Markdown packet text may appear only as a supplemental source view after the rendered review UI; do not make a `Full Preliminary Packet` or `Full Working Packet` raw Markdown dump, giant `<pre><code>` block, link-only view, or source-only view the primary review surface. Include the evidence matrix, assumptions/confidence register, source coverage gaps, proposed canonical file changes, and artifact approval gates. Partial compiled responses revise the working packet and review page, then remain in Stage 2. Stage 3 consumes final compiled response YAML for artifact approval only when it has `approval_status: ready-for-agent-review` and no unresolved `needs-clarification`, unresolved `down` feedback, or other unresolved negative feedback. Apply approved edits first, archive the working packet to `docs/history/archive/YYYY-MM-DD/HHMMSS/<original-working-path>`, remove the active working packet, write the approved canonical artifacts to the unchanged output paths, and convert the page to `confirmed` with the approval record preserved.
+
+**Stage 2 review-page template.** Stage 1 scope-review pages must include a `Stage 2 Preview / Expected Review Format` section that previews the exact section sequence, table shapes, evidence treatment, visual density, and approval gates the user will see after research; make it specific enough for the user to flag preferred content formats, grouping, labels, visuals, and evidence density before the agent does heavy research. After scope approval and research, the Stage 2 review page must include these sections as structured HTML, not as raw Markdown dumps: `Research Scope Approved` status block with approved scope, source plan, output paths, and unresolved caveats; `Executive Findings` or a skill-specific top-findings section with confidence labels; `Evidence Matrix` mapping claim, evidence/source/path, inference, confidence, assumptions, and decision impact; `Working Packet Review` with the complete working-packet substance rendered as purpose-built HTML sections, lists, tables, matrices, cards, and tier-appropriate charts or diagrams; `Alternatives / Rejected or Lower-Confidence Findings`; `Source Coverage & Gaps`; `Assumptions / Confidence Register`; `Proposed Canonical Artifacts & File Changes`; a required `User Format Preferences` gate asking whether the layout, tables, grouping, visuals, labels, and evidence density match expectations; and a required `Final Artifact Approval` gate for Stage 3 readiness. Raw Markdown packet text, search logs, or source notes may appear only as supplemental source views after the rendered review UI and never replace the Stage 2 review sections.
 
 **Competitive research translation.** Render competitor coverage by category, pricing and packaging evidence, positioning claims, user-sentiment signals, integration or distribution evidence, recent activity, alternatives considered, lower-confidence comparisons, and source gaps that could change the strategic recommendation.
 

package/packs/business-research/claude/competitive-analysis/CHANGELOG.md

@@ -1,5 +1,13 @@
 # competitive-analysis changelog (claude)
 
+## v0.19 - 2026-06-12
+
+- Clarified staged research review pages must render complete working-packet substance as structured HTML UI, with raw Markdown packet text allowed only as a supplemental source view.
+
+## v0.18 - 2026-06-12
+
+- Standardized active pack and skill install guidance on `npx skillpacks install <pack-or-skill>` instead of agent-native `/pack install` or `$pack install` recommendations.
+
 ## v0.17 - 2026-06-11
 
 - Added npm-aware install-route guidance so unavailable-pack fallbacks keep `/pack install` while also offering `npx skillpacks install <pack>` from the project shell.

package/packs/business-research/claude/competitive-analysis/SKILL.md

@@ -2,16 +2,16 @@
 name: competitive-analysis
 description: Orchestrator — select competitive-analysis frameworks, queue framework research, and synthesize market landscape findings
 type: research
-version: v0.17
+version: v0.19
 argument-hint: "[optional: \"--synthesize\" | \"core\" | concept/category/competitors]"
 invocation: orchestrator
-interview_depth: light
+context_intake: scoped
 visual_tier: visual
 ---
 
 ## Pack Availability Guard
 
-Before telling the user to run a skill from another project-local pack, check `.agents/project.json.enabled_packs`. If the target pack is not enabled, recommend `/pack install <pack>` inside Claude Code, or `npx skillpacks install <pack>` from the project shell, instead of the target skill. After install, tell Claude users to run `/reload-skills`, then `/clear` or restart if the skill remains invisible. Global skills are always valid. Skills from this same pack are valid because the current skill is already running from that pack.
+Before telling the user to run a skill from another project-local pack, check `.agents/project.json.enabled_packs`. If the target pack is not enabled, recommend `npx skillpacks install <pack>` from the project shell, instead of the target skill. After install, tell Claude users to run `/reload-skills`, then `/clear` or restart if the skill remains invisible. Global skills are always valid. Skills from this same pack are valid because the current skill is already running from that pack.
 
 # Competitive Analysis — Orchestrator
 
@@ -43,7 +43,7 @@ Do not include `Recommended next skill`, `Recommended next command`, or downstre
 Use this staged workflow for synthesized research or report outputs that would create or update canonical research, spec, or task files.
 
 1. **Stage 1 - Scope discovery and approval.** Inspect only enough repository, user, and source context to propose research scope, source plan, assumptions, output paths, and approval questions. Build the `review` HTML 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 perform synthesized research, rank candidates, make recommendations, or write working packets, canonical research, spec, or task files in Stage 1.
-2. **Stage 2 - Research and artifact review.** Only after approved research-scope YAML 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-<skill>-research.md`; product-path mode uses `research/{slug}/_working/preliminary-<skill>-research.md`. Replace `<skill>` with this skill's `name` value. Raw evidence or search logs may remain as supporting evidence where this skill already requires them, but synthesized deliverables stay in the working packet. Update the `review` HTML alignment page with the full preliminary packet, evidence matrix, assumptions/confidence register, source coverage gaps, proposed canonical file changes, and artifact approval gates. Stop for either feedback-only YAML or final compiled YAML. Feedback-only YAML revises the working packet and page, then remains in Stage 2.
+2. **Stage 2 - Research and artifact review.** Only after approved research-scope YAML 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-<skill>-research.md`; product-path mode uses `research/{slug}/_working/preliminary-<skill>-research.md`. Replace `<skill>` with this skill's `name` value. Raw evidence or search logs may remain as supporting evidence where this skill already requires them, but synthesized deliverables stay in the working packet. Update the `review` HTML alignment page so it renders the complete working-packet substance as structured HTML review UI: purpose-built sections, tables, matrices, gates, cards, and tier-appropriate charts or diagrams that preserve every packet section, finding, caveat, and decision detail without summary loss. Raw Markdown packet text may appear only as a supplemental source view after the rendered review UI; do not make a `Full Preliminary Packet` or `Full Working Packet` raw Markdown dump, giant `<pre><code>` block, link-only view, or source-only view the primary review surface. Include the evidence matrix, assumptions/confidence register, source coverage gaps, proposed canonical file changes, and artifact approval gates. Stop for either feedback-only YAML or final compiled YAML. Feedback-only YAML revises the working packet and page, then remains in Stage 2.
 3. **Stage 3 - Finalize approved artifacts.** Consume 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 below, and convert the alignment page to `confirmed` with the approval record preserved.
 
 Canonical output paths remain unchanged. Search logs and other supporting evidence remain allowed only where this skill's output contract already requires them.
@@ -169,12 +169,12 @@ Build the report-first alignment page before writing. Only after final compiled
 
 **Standard mode next steps:** `## Next Steps` section with a **Recommended** item and **Other options** (2-4 alternatives). Choose the recommended item by the first matching condition:
 
-1. IF no `research/journey-map.md`: check `.agents/project.json.enabled_packs` for `customer-lifecycle` - if `customer-lifecycle` is not enabled, recommend `/pack install customer-lifecycle` inside Claude Code, or `npx skillpacks install customer-lifecycle` from the project shell, first; if `customer-lifecycle` is enabled, recommend `/journey-map` - map the customer and user journey before solution-value decisions, using competitive gaps as inspiration
+1. IF no `research/journey-map.md`: check `.agents/project.json.enabled_packs` for `customer-lifecycle` - if `customer-lifecycle` is not enabled, recommend `npx skillpacks install customer-lifecycle` from the project shell, first; if `customer-lifecycle` is enabled, recommend `/journey-map` - map the customer and user journey before solution-value decisions, using competitive gaps as inspiration
 2. IF no `research/positioning.md`: `/positioning` - frame the market category and alternatives after journey evidence shows where value is delivered
-3. IF no `specs/user-flow-*.md`: check `.agents/project.json.enabled_packs` for `product-design` - if `product-design` is not enabled, recommend `/pack install product-design` inside Claude Code, or `npx skillpacks install product-design` from the project shell, first; if `product-design` is enabled, recommend `/user-flow-map [top journey-backed market gap or positioning opportunity]` - map flow structure before UI requirements, layout variants, and production specification
+3. IF no `specs/user-flow-*.md`: check `.agents/project.json.enabled_packs` for `product-design` - if `product-design` is not enabled, recommend `npx skillpacks install product-design` from the project shell, first; if `product-design` is enabled, recommend `/user-flow-map [top journey-backed market gap or positioning opportunity]` - map flow structure before UI requirements, layout variants, and production specification
 4. IF no `research/value-prop.md` AND solution-customer fit is weak, disputed, or needs explicit fit scoring: `/value-prop-canvas` - validate contested solution-fit evidence as an optional detour
-5. IF no `research/gtm.md`: check `.agents/project.json.enabled_packs` for `business-growth` - if `business-growth` is not enabled, recommend `/pack install business-growth` inside Claude Code, or `npx skillpacks install business-growth` from the project shell, first; if `business-growth` is enabled, recommend `/gtm` - build go-to-market plan leveraging competitive gaps
-6. IF codebase exists and no `research/mvp-gap.md`: check `.agents/project.json.enabled_packs` for `business-ops` - if `business-ops` is not enabled, recommend `/pack install business-ops` inside Claude Code, or `npx skillpacks install business-ops` from the project shell, first; if `business-ops` is enabled, recommend `/mvp-gap` - check if the codebase exploits the gaps found
+5. IF no `research/gtm.md`: check `.agents/project.json.enabled_packs` for `business-growth` - if `business-growth` is not enabled, recommend `npx skillpacks install business-growth` from the project shell, first; if `business-growth` is enabled, recommend `/gtm` - build go-to-market plan leveraging competitive gaps
+6. IF codebase exists and no `research/mvp-gap.md`: check `.agents/project.json.enabled_packs` for `business-ops` - if `business-ops` is not enabled, recommend `npx skillpacks install business-ops` from the project shell, first; if `business-ops` is enabled, recommend `/mvp-gap` - check if the codebase exploits the gaps found
 
 Use this format in the output:
 
@@ -183,13 +183,13 @@ Use this format in the output:
 **Recommended:** `[first matching command above]` - [reason grounded in this analysis]
 
 Other options:
-- `/pack install customer-lifecycle` inside Claude Code, or `npx skillpacks install customer-lifecycle` from the project shell, or `/journey-map` - map the customer journey to find where competitors fall short (if no `research/journey-map.md` and not recommended; check `.agents/project.json.enabled_packs` for `customer-lifecycle` - if not enabled, recommend `/pack install customer-lifecycle` inside Claude Code, or `npx skillpacks install customer-lifecycle` from the project shell; if enabled, recommend `/journey-map`)
+- `npx skillpacks install customer-lifecycle` from the project shell, or `/journey-map` - map the customer journey to find where competitors fall short (if no `research/journey-map.md` and not recommended; check `.agents/project.json.enabled_packs` for `customer-lifecycle` - if not enabled, recommend `npx skillpacks install customer-lifecycle` from the project shell; if enabled, recommend `/journey-map`)
 - `/positioning` - frame the market category and competitive alternatives after journey evidence exists (if no `research/positioning.md` and not recommended)
-- check `.agents/project.json.enabled_packs` for `product-design` - if `product-design` is not enabled, recommend `/pack install product-design` inside Claude Code, or `npx skillpacks install product-design` from the project shell, first; if `product-design` is enabled, recommend `/user-flow-map [top journey-backed market gap or positioning opportunity]` - map flow structure before UI requirements, layout variants, and production specification (if positioning exists and not recommended)
+- check `.agents/project.json.enabled_packs` for `product-design` - if `product-design` is not enabled, recommend `npx skillpacks install product-design` from the project shell, first; if `product-design` is enabled, recommend `/user-flow-map [top journey-backed market gap or positioning opportunity]` - map flow structure before UI requirements, layout variants, and production specification (if positioning exists and not recommended)
 - `/value-prop-canvas` - optional detour only when solution-customer fit is weak, disputed, or needs explicit fit scoring before positioning/spec work
-- check `.agents/project.json.enabled_packs` for `business-growth` - if `business-growth` is not enabled, recommend `/pack install business-growth` inside Claude Code, or `npx skillpacks install business-growth` from the project shell, first; if `business-growth` is enabled, recommend `/gtm` - build go-to-market plan leveraging competitive gaps (if no `research/gtm.md` and not recommended)
-- check `.agents/project.json.enabled_packs` for `business-ops` - if `business-ops` is not enabled, recommend `/pack install business-ops` inside Claude Code, or `npx skillpacks install business-ops` from the project shell, first; if `business-ops` is enabled, recommend `/mvp-gap` - check if the codebase exploits the gaps found (if codebase exists, no `research/mvp-gap.md` exists, and not recommended)
-- check `.agents/project.json.enabled_packs` for `product-design` - if `product-design` is not enabled, recommend `/pack install product-design` inside Claude Code, or `npx skillpacks install product-design` from the project shell, first; if `product-design` is enabled, recommend `/brainstorm` - generate alternative solution ideas (only if the analysis found multiple plausible market gaps and product direction is still unclear)
+- check `.agents/project.json.enabled_packs` for `business-growth` - if `business-growth` is not enabled, recommend `npx skillpacks install business-growth` from the project shell, first; if `business-growth` is enabled, recommend `/gtm` - build go-to-market plan leveraging competitive gaps (if no `research/gtm.md` and not recommended)
+- check `.agents/project.json.enabled_packs` for `business-ops` - if `business-ops` is not enabled, recommend `npx skillpacks install business-ops` from the project shell, first; if `business-ops` is enabled, recommend `/mvp-gap` - check if the codebase exploits the gaps found (if codebase exists, no `research/mvp-gap.md` exists, and not recommended)
+- check `.agents/project.json.enabled_packs` for `product-design` - if `product-design` is not enabled, recommend `npx skillpacks install product-design` from the project shell, first; if `product-design` is enabled, recommend `/brainstorm` - generate alternative solution ideas (only if the analysis found multiple plausible market gaps and product direction is still unclear)
 
 Only include items whose conditions are met. Do not recommend brainstorm just because competitive whitespace exists.