skillpacks 0.1.1 → 0.1.2

package/packs/business-ops/codex/platform-strategy/archive/v0.9/SKILL.md

@@ -0,0 +1,182 @@
+---
+name: platform-strategy
+description: Expand from a single product into a multi-product platform — map vertical and horizontal growth vectors, score candidates, design validation experiments, and sequence the portfolio
+type: research
+version: v0.9
+argument-hint: "[optional: expansion direction e.g. \"vertical\", \"horizontal\", or specific adjacent market]"
+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.
+
+# Platform Strategy — Multi-Product Expansion Planning
+
+Invoke as `$platform-strategy`.
+
+## Report-First Approval Gate
+
+Default to scope-first approval: before synthesized research, inspect only enough repository, user, and source context to propose research scope, source plan, assumptions, output paths, and approval questions in a `review` alignment page plus a concise conversation summary.
+
+Do not perform synthesized research, rank candidates, make recommendations, or write working packets or canonical deliverables until final compiled YAML approves the research scope. Minimal pre-approval discovery may identify available files, source categories, and open questions; label it as scope evidence, not findings.
+
+After approved research-scope YAML, perform the research and write only the non-canonical working packet defined in the staged workflow. Then update the `review` alignment page with findings and stop again for feedback-only YAML or final compiled YAML artifact approval before creating or updating canonical research, spec, or task files.
+
+Do not include `Recommended next skill`, `Recommended next command`, or downstream routing language. The approval request itself is the next action. Only emit next-skill routing after the approved artifact has been written or updated.
+
+## Staged Research Workflow
+
+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.
+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.
+
+## Evidence And Feedback Handling
+
+Treat user feedback as input to evaluate, not as automatic ground truth.
+
+- For factual, evidentiary, technical, or source-backed claims: verify against available evidence. If the user appears to misunderstand the evidence or states something factually incorrect, push back clearly and cite the evidence. Do not rewrite findings merely to agree.
+- For taste, brand, positioning preference, risk appetite, prioritization, or other subjective judgment calls: weigh user feedback heavily and adapt the recommendation unless it conflicts with verified evidence.
+- When feedback mixes facts and preference, separate them explicitly: correct the factual part, then incorporate the preference where it is a legitimate judgment call.
+- When uncertain, say what is known, what is inferred, and what would change the conclusion.
+
+## Prerequisites
+
+**Required (at least one):**
+- `research/icp.md` (or `research/{slug}/icp.md`) — who you serve today
+- A working product/codebase to analyse for extensibility
+
+If neither exists, tell the user: "Platform expansion requires a foundation. Run `$customer-discovery` first to define who you serve today, then come back."
+
+**Strongly recommended** (read if they exist):
+- `research/competitive-analysis.md` — market gaps
+- `research/journey-map.md` — user flows, drop-off points
+- `research/metrics.md` — retention, activation baselines
+
+**Optional:** `research/monetization.md`, `research/positioning.md`, `research/customer-feedback.md`, `research/enterprise-icp.md`, `research/assumption-tracker.md`
+
+## 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. Assess Core Product Health
+
+Read the codebase, existing research, and metrics to evaluate: PMF signals (retention, activation, satisfaction), technical extensibility (shared infra — auth, billing, data — vs. tightly coupled), team/resource signals, revenue stability.
+
+**Checkpoint 1 — Present core health assessment.** Show health summary, shareable infrastructure, red flags. Ask: "Does this match your sense of where the core product is? Resource constraints to factor in?"
+
+### 2. Map Expansion Vectors
+
+Use web search with **8-12 diverse queries**: adjacent markets, vertical depth (enterprise features, advanced use cases), horizontal breadth (related categories, tools used alongside), platform precedents, user workflow gaps, ecosystem opportunities, acquisition patterns, market trends, adjacent pain points, bundling precedents.
+
+Also analyse codebase and existing research for internal signals: adjacent feature requests from customer feedback, competitor product lines, journey map drop-offs, data/infra that could power new products.
+
+### 3. Identify Expansion Candidates — Present & Validate
+
+Cluster findings into **4-8 candidates** across two axes:
+
+**Vertical:** advanced tiers, deeper workflow coverage, industry-specific variants, data products from existing data.
+
+**Horizontal:** complementary tools, adjacent persona products, same tech applied to different problem, marketplace/platform plays.
+
+For each: problem, audience, relationship to core, market signal, vertical vs. horizontal.
+
+Record the 4-8 candidates in `research/.progress.yaml` as `product_paths[]` entries with `source_skill: platform-strategy`. The top candidate may be `status: active` or `status: revisit_candidate` depending on whether the user is ready to validate it now; non-selected candidates should default to `status: deferred` with validation triggers. Include `id`, `label`, `source_skill: platform-strategy`, `pipeline_stage: platform-strategy`, `scope_path`, `status`, `reason`, `archive_reason`, `archived_at`, `promoted_at`, `evidence_refs`, `revisit_trigger`, `next_skill`, and `last_touched`.
+
+**Checkpoint 2 — Present candidates.** Group by vertical/horizontal with rationale and evidence. Ask: "Expansion directions I missed? Any clearly wrong? Internal signals pointing toward any of these?"
+
+### 4. Score Expansion Candidates
+
+Score each across five dimensions (1-5 each):
+
+- **Synergy** — shared users, data, infra, cross-sell potential
+- **Market Opportunity** — size, competitive density, willingness to pay, growth
+- **Effort & Risk** — build complexity, time to revenue, tech risk, cannibalization
+- **Strategic Value** — defensibility, brand coherence, sequencing value
+- **Validation Cost** — how cheaply can we test demand
+
+Build a scoring matrix with weighted totals.
+
+### 5. Design Validation Experiments for Top Candidates
+
+For **top 2-3 candidates**: cheapest test method (landing page, fake-door, survey, pre-sale, concierge), audience, success criteria, timeline (1-4 weeks), decision rules (proceed/pivot/kill). Reference `$experiment` for full experiment design.
+
+### 6. Sequence the Portfolio — Present & Validate
+
+Recommend a portfolio sequence: **Now** (next quarter), **Next** (quarter +1), **Later** (6-12 months), **Watch** (12+ months). For each: shared infra needed, dependencies, revenue expectation, kill criteria.
+
+**Checkpoint 3 — Present full portfolio plan.** Show scoring matrix, validation experiments, portfolio sequence, shared platform considerations. Ask: "Sequencing match your priorities? Different experiments to run first? Dependencies I'm missing?"
+
+### 7. Write Output
+
+Only after user validates, write the output files.
+
+## Deliverables
+
+- `research/platform-strategy.md` (or `research/{slug}/platform-strategy.md`) — Full platform strategy: summary, core health, expansion vector map, scoring matrix, validation experiments, portfolio sequence, shared platform considerations, next steps.
+- `research/platform-strategy-search-log.md` (or `research/{slug}/platform-strategy-search-log.md`) — Raw research log: every query, findings, source attribution, scoring rationale.
+- `research/.progress.yaml` — product-path manifest updated with 4-8 expansion candidates. This does not require every candidate to become a full research track.
+
+`## Next Steps` section with a **Recommended** item and **Other options** (2–4 alternatives). Use this format in the output:
+
+## Next Steps
+
+**Recommended:** `$experiment [top candidate]` — validate demand for the highest-scored expansion candidate before committing resources
+
+Other options:
+- `$assumption-tracker` — track which platform assumptions need validation (if no `research/assumption-tracker.md`)
+- `$competitive-analysis [adjacent category]` — research the competitive landscape for the top expansion candidate
+- `$customer-discovery [new audience]` — run customer discovery for the new audience the top candidate targets
+- `$enterprise-icp` — map enterprise requirements if the expansion targets enterprise (if no `research/enterprise-icp.md`)
+- `$roadmap` — sequence the expansion into the build plan (if `specs/` exist for the candidate)
+- `$roadmap` — sequence the expansion into the build plan (if `specs/` exist)
+
+The recommendation (`$experiment [top candidate]`) is always applicable — platform expansion should be validated before built.
+
+## 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
+
+- Use web search extensively — every market signal must trace to research evidence.
+- Cite sources for market signals, competitor product lines, trend data.
+- Be honest about uncertainty.
+- Stay in strategy mode — no architecture, features, or technical solutions.
+- Core health is gating — flag PMF problems directly.
+- Score honestly — low-synergy, high-effort candidates should score low.
+- Present before writing — never write until findings are validated.
+- Do not overwrite existing `research/platform-strategy.md` (or `research/{slug}/platform-strategy.md`) without asking.
+- Keep validation experiments lightweight — full design belongs in `$experiment`.
+- `## Next Steps` must be the final section in the output file, with a recommended next step and 2–4 other 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/platform-strategy-{topic}.html`.
+
+## Default Shipping Contract
+
+Follow the shared shipping contract convention in CLAUDE.md.

package/packs/business-ops/codex/product-line/ALIGNMENT-PAGE.md

@@ -1,6 +1,6 @@
 # Alignment Page — product-line
 
-When this skill produces durable deliverables (research, specs, plans, reports, prototypes, or any document output), build a full-depth HTML alignment page at `alignment/product-line-{topic}.html`. Use a normalized topic slug derived from the app, feature, research subject, report subject, or output filename.
+Alignment pages are optional for this operational skill. By default, report the outcome inline and write only the skill's normal durable artifacts (`tasks/*.md`, reports, queues, benchmark notes, status docs, or other skill-specific files). Build `alignment/product-line-{topic}.html` only when the user explicitly requests an alignment page or when the agent explicitly identifies a concrete clarification/review need that cannot be resolved cleanly in conversation or the normal artifacts. When an alignment page is created, use the full contract below and a normalized topic slug derived from the app, feature, research subject, report subject, or output filename.
 
 **Visual rendering tier.** Each alignment page declares a rendering tier:
 - `document` (default) — text, tables, approval gates. No charts or interactive elements.
@@ -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-product-line-research.md`; product-path mode uses `research/{slug}/_working/preliminary-product-line-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-product-line-research.md`; product-path mode uses `research/{slug}/_working/preliminary-product-line-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/product-line/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## v0.6 - 2026-06-12
+
+- Made alignment pages optional by default: report inline and write the skill's normal durable artifacts unless the user requests an alignment page or the agent identifies a concrete clarification/review need.
+
+## v0.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/product-line/SKILL.md

@@ -2,15 +2,15 @@
 name: product-line
 description: Manage the portfolio of product paths — review, activate, archive, restore, promote, fork, and check revisit triggers across the product-path manifest
 type: ops
-version: v0.4
+version: v0.6
 argument-hint: "review | activate <path-id> | archive <path-id> | restore <path-id> | promote <path-id> | fork <label> [--from <skill>] | triggers"
-interview_depth: none
+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.
 
 # Product Line — Product Path Portfolio Management
 
@@ -178,7 +178,7 @@ Update `research/.progress.yaml`. `archive` and `restore` may also move product-
 
 ## 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/product-line-{topic}.html`.
+By default, this skill reports results inline and writes only its normal durable artifacts (for example `tasks/*.md`, reports, queues, benchmark notes, status docs, or other skill-specific files). Do not build an alignment page automatically. Create `alignment/product-line-{topic}.html` only when the user explicitly requests an alignment page or when you explicitly identify a concrete clarification/review need that cannot be handled cleanly inline; when you create one, follow `ALIGNMENT-PAGE.md` in this skill's directory.
 
 ## Default Shipping Contract
 

package/packs/business-ops/codex/product-line/archive/v0.4/SKILL.md

@@ -0,0 +1,185 @@
+---
+name: product-line
+description: Manage the portfolio of product paths — review, activate, archive, restore, promote, fork, and check revisit triggers across the product-path manifest
+type: ops
+version: v0.4
+argument-hint: "review | activate <path-id> | archive <path-id> | restore <path-id> | promote <path-id> | fork <label> [--from <skill>] | triggers"
+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.
+
+# Product Line — Product Path Portfolio Management
+
+Invoke as `$product-line`.
+
+Manage product paths tracked in `research/.progress.yaml`. Product paths are research divergences — different products, apps, ICPs, expansion candidates, pivots, or competitive gaps — not git branches. Each path tracks its scope directory, status, evidence, pipeline stage, and revisit conditions.
+
+Use `activate` when a deferred or revisit candidate path should become active research again. Use `promote` only when a research path graduates to an `apps/{slug}/` code/app scope.
+
+## Prerequisites
+
+`research/.progress.yaml` must exist for all modes except `fork` (which can create it). If missing, tell the user: "No product-path manifest found. Run `$idea-scope-brief` or `$customer-discovery` first — they create the manifest when multiple product directions emerge."
+
+## Manifest Schema
+
+The canonical manifest lives at `research/.progress.yaml`:
+
+```yaml
+active_paths:
+  - "cost-intel"
+max_concurrent: 1
+product_paths:
+  - id: "cost-intel"
+    label: "Cost Intel"
+    scope_path: "research/cost-intel/"
+    status: active # active | deferred | archived | promoted | revisit_candidate
+    source_skill: "icp"
+    reason: "Why this path exists"
+    archive_reason: null
+    archived_at: null
+    promoted_at: null
+    evidence_refs: []
+    revisit_trigger: null
+    next_skill: "$competitive-analysis"
+    pipeline_stage: "icp"
+    last_touched: "YYYY-MM-DD"
+```
+
+### Backward Compatibility
+
+- Read legacy `active_path` as `active_paths: [<value>]` when `active_paths` is absent.
+- Read legacy `status: abandoned` as `status: archived`.
+- On writes, remove `active_path`, write plural `active_paths`, and prefer `status: archived` instead of `abandoned`.
+- Treat `status: promoted` as graduated to code/app scope, not reactivated research.
+- Exclude `research/_archive/` paths from active-path selection and directory suggestions.
+
+## Modes
+
+### 1. `review` — Portfolio Dashboard
+
+**Invocation**: `$product-line review`
+
+Present a dashboard comparing all paths:
+
+| Path | Status | Scope | Pipeline Stage | Last Touched | Evidence Maturity | Revisit Trigger |
+|------|--------|-------|----------------|--------------|-------------------|-----------------|
+
+Group by `active`, `deferred`, `revisit_candidate`, `archived`, and `promoted`. For `deferred` and `revisit_candidate` paths, highlight the revisit trigger. For `archived` paths, show `archive_reason` and `archived_at`. For `promoted` paths, show `promoted_at` and the expected `apps/{slug}/` scope.
+
+Evidence maturity is derived from files under `scope_path` or `evidence_refs`:
+- **Early** — only concept brief or initial ICP
+- **Developing** — ICP plus competitive analysis, positioning, or journey map
+- **Mature** — journey map plus metrics, GTM, monetization, or experiments
+- **Graduated** — promoted to an app/code scope
+
+When 3+ deferred or revisit-candidate paths exist with no recent activation, recommend `$product-line triggers`.
+
+### 2. `activate <path-id>` — Reactivate Research
+
+**Invocation**: `$product-line activate <path-id>`
+
+1. Validate the path exists and has status `deferred` or `revisit_candidate`.
+2. Check `max_concurrent` against the current active-path count. If at capacity, ask whether to deactivate another path or increase `max_concurrent`.
+3. Ensure `scope_path` is not under `research/_archive/`. If it is archived, tell the user to run `$product-line restore <path-id>` first.
+4. Scan existing research files to infer `pipeline_stage`.
+5. Update the manifest:
+   - Set `status: active`
+   - Add the path ID to `active_paths`
+   - Set `last_touched` to today
+   - Set `pipeline_stage` from the scan when clearer than the existing value
+6. Recommend the next skill from `next_skill` or the inferred pipeline stage.
+
+### 3. `archive <path-id>` — Archive A Research Path
+
+**Invocation**: `$product-line archive <path-id>`
+
+1. Validate the path exists and is not already `archived` or legacy `abandoned`.
+2. Ask for a concise archive rationale.
+3. If `scope_path` is `research/{slug}/` and the directory exists, create `research/_archive/` as needed and move it to `research/_archive/{slug}/`.
+4. Update the manifest:
+   - Set `status: archived`
+   - Remove the path ID from `active_paths`
+   - Set `scope_path` to `research/_archive/{slug}/` when the directory was moved
+   - Set `archive_reason`, `archived_at`, and `last_touched`
+5. Present confirmation with the archived directory and rationale.
+
+### 4. `restore <path-id>` — Restore An Archived Path
+
+**Invocation**: `$product-line restore <path-id>`
+
+1. Validate the path exists and has status `archived` or legacy `abandoned`.
+2. If `scope_path` is `research/_archive/{slug}/` and the directory exists, move it back to `research/{slug}/`.
+3. Ask whether to restore as `deferred` (default) or `active`. If active, enforce `max_concurrent`.
+4. Update the manifest:
+   - Set `status: deferred` by default, or `active` only when approved
+   - Add to `active_paths` only when restored as active
+   - Set `scope_path` back to `research/{slug}/`
+   - Clear `archived_at`; keep the old archive rationale in `reason` or history, but set `archive_reason: null`
+   - Set `last_touched` to today
+5. Recommend `$product-line activate <path-id>` if restored as deferred.
+
+### 5. `promote <path-id>` — Graduate To App Scope
+
+**Invocation**: `$product-line promote <path-id>`
+
+Use this only when research is ready to become or connect to an app under `apps/{slug}/`.
+
+1. Validate the path exists and is not `archived` or legacy `abandoned`.
+2. Derive `{slug}` from the path ID or `scope_path`.
+3. Confirm or create `apps/{slug}/` during the monorepo scaffolding flow. If scaffolding requires another skill, recommend `$scaffold` or the appropriate monorepo command instead of inventing app files here.
+4. Keep research docs under `research/{slug}/` as product evidence unless a separate scaffolder explicitly moves or links docs.
+5. Update the manifest:
+   - Set `status: promoted`
+   - Remove the path ID from `active_paths`
+   - Set `promoted_at` and `last_touched` to today
+   - Keep `scope_path` pointing at the research evidence path
+6. Present the app graduation result and the next implementation/scaffolding command.
+
+### 6. `fork <label> [--from <skill>]` — Create A New Path
+
+**Invocation**: `$product-line fork "Enterprise vertical" --from competitive-analysis`
+
+1. Generate a stable product-path ID from the label.
+2. Confirm that the slug is the intended product/app name, not merely an ICP, audience, or segment label.
+3. Ask for supporting evidence, revisit trigger, and initial status (`active` or `deferred`).
+4. Create or update `research/.progress.yaml` with the full schema fields.
+5. Use `scope_path: research/{slug}/`.
+6. If status is `active`, enforce `max_concurrent` and create `research/{slug}/`.
+7. If status is `deferred`, create the manifest entry without forcing downstream research.
+
+### 7. `triggers` — Check Revisit Conditions
+
+**Invocation**: `$product-line triggers`
+
+Scan paths with `status: deferred` or `status: revisit_candidate` and evaluate their `revisit_trigger` conditions:
+- **File-based triggers** — check whether the referenced file exists.
+- **Evidence-based triggers** — check active research files for relevant evidence.
+- **Time-based triggers** — compare against today's date.
+- **External triggers** — flag as requiring manual confirmation.
+
+Classify each trigger as **fired**, **pending**, or **manual**. For fired triggers, recommend `$product-line activate <path-id>`.
+
+## Output
+
+Update `research/.progress.yaml`. `archive` and `restore` may also move product-path directories between `research/{slug}/` and `research/_archive/{slug}/`. `promote` may confirm or route creation of `apps/{slug}/`, but it does not move research docs.
+
+## Constraints
+
+- Do not run downstream research or implementation skills.
+- Do not treat archived, legacy abandoned, deferred, revisit-candidate, or promoted paths as active research targets.
+- Do not use `promote` to mean "make active"; use `activate`.
+- Do not use `archive` without a documented rationale.
+- Respect `max_concurrent` for active paths.
+- Use product-path terminology. Never use "branch" to mean a product path.
+
+## 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/product-line-{topic}.html`.
+
+## Default Shipping Contract
+
+Follow the shared shipping contract convention in CLAUDE.md (adapted for Codex: commit and push changes to the repository primary branch).