skillpacks 0.1.1 → 0.1.2

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

@@ -0,0 +1,193 @@
+---
+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 Claude Code, or `npx skillpacks install <pack>` from the project shell. 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.
+
+# Product Line — Product Path Portfolio Management
+
+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.
+
+## 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
+
+- 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.

package/packs/business-ops/claude/product-line/archive/v0.5/SKILL.md

@@ -0,0 +1,193 @@
+---
+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.5
+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 `npx skillpacks install <pack>` from the project shell. 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.
+
+# Product Line — Product Path Portfolio Management
+
+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.
+
+## 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
+
+- 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.

package/packs/business-ops/claude/reconcile-research/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-reconcile-research-research.md`; product-path mode uses `research/{slug}/_working/preliminary-reconcile-research-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-reconcile-research-research.md`; product-path mode uses `research/{slug}/_working/preliminary-reconcile-research-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.
 
 **Research-pack translation.** For business, devtool, game, creator, and media research packs, render the claim/evidence/inference/assumption/decision-impact structure, source coverage categories appropriate to the domain, lower-confidence findings, and downstream implications before asking for approval or routing to the next skill.
 

package/packs/business-ops/claude/reconcile-research/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## v0.10 - 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.9 - 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.8 - 2026-06-10
 
 - Added npm-aware install-route guidance for business-ops cross-pack recommendations, preserving `/pack install <pack>` inside Claude Code while offering `npx skillpacks install <pack>` from the project shell.

package/packs/business-ops/claude/reconcile-research/SKILL.md

@@ -2,9 +2,9 @@
 name: reconcile-research
 description: Cross-document consistency audit across research outputs — find contradictions, stale assumptions, and gaps
 type: research
-version: v0.8
+version: v0.10
 argument-hint: "[audit|fix] [all|icp|pricing|journey|enterprise|feedback|specs]"
-interview_depth: none
+context_intake: artifact_only
 ---
 
 # Reconcile Research — Cross-Document Consistency Audit
@@ -24,7 +24,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.
@@ -256,9 +256,9 @@ After presenting findings (audit mode) or applying resolutions (fix mode), displ
 **Recommended:** [skill with most conflicts] — [N] conflicts traced to this document; re-running it will resolve the most inconsistencies at once
 
 Other options:
-- check `.agents/project.json.enabled_packs` for `research-admin` — if `research-admin` is not enabled, recommend `/pack install research-admin` inside Claude Code, or `npx skillpacks install research-admin` from the project shell, first; if `research-admin` is enabled, recommend `/research-roadmap` — rebuild the ordered documentation queue after reconciliation
-- check `.agents/project.json.enabled_packs` for `agent-work-admin` — if `agent-work-admin` is not enabled, recommend `/pack install agent-work-admin` inside Claude Code, or `npx skillpacks install agent-work-admin` from the project shell, first; if `agent-work-admin` is enabled, recommend `/spec-drift` — check whether code/spec drift remains after research reconciliation
-- check `.agents/project.json.enabled_packs` for `agent-work-admin` — if `agent-work-admin` is not enabled, recommend `/pack install agent-work-admin` inside Claude Code, or `npx skillpacks install agent-work-admin` from the project shell, first; if `agent-work-admin` is enabled, recommend `/roadmap` — resequence implementation if reconciliation changed priorities
+- check `.agents/project.json.enabled_packs` for `research-admin` — if `research-admin` is not enabled, recommend `npx skillpacks install research-admin` from the project shell, first; if `research-admin` is enabled, recommend `/research-roadmap` — rebuild the ordered documentation queue after reconciliation
+- check `.agents/project.json.enabled_packs` for `agent-work-admin` — if `agent-work-admin` is not enabled, recommend `npx skillpacks install agent-work-admin` from the project shell, first; if `agent-work-admin` is enabled, recommend `/spec-drift` — check whether code/spec drift remains after research reconciliation
+- check `.agents/project.json.enabled_packs` for `agent-work-admin` — if `agent-work-admin` is not enabled, recommend `npx skillpacks install agent-work-admin` from the project shell, first; if `agent-work-admin` is enabled, recommend `/roadmap` — resequence implementation if reconciliation changed priorities
 ```
 
 ## Output