skillpacks 0.1.1 → 0.1.2

package/packs/customer-lifecycle/claude/journey-map/frameworks/customer-journey-canvas/SKILL.md

@@ -2,14 +2,14 @@
 name: customer-journey-canvas
 description: Stickdorn customer journey canvas — stage×touchpoints×actions×emotion×backstage×pain×opportunities grid
 type: research
-version: v0.3
+version: v0.5
 invocation: sub-skill
 parent: journey-map
 ---
 
 ## 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. 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. Global skills are always valid. Skills from this same pack are valid because the current skill is already running from that pack.
 
 # Customer Journey Canvas — Stickdorn Analysis
 
@@ -28,7 +28,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.

package/packs/customer-lifecycle/claude/journey-map/frameworks/customer-journey-canvas/archive/v0.3/SKILL.md

@@ -0,0 +1,189 @@
+---
+name: customer-journey-canvas
+description: Stickdorn customer journey canvas — stage×touchpoints×actions×emotion×backstage×pain×opportunities grid
+type: research
+version: v0.3
+invocation: sub-skill
+parent: journey-map
+---
+
+## 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. Global skills are always valid. Skills from this same pack are valid because the current skill is already running from that pack.
+
+# Customer Journey Canvas — Stickdorn Analysis
+
+## 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. Push back clearly and cite the evidence when the user appears to misunderstand.
+- For taste, prioritization, or subjective judgment calls: weigh user feedback heavily and adapt unless it conflicts with verified evidence.
+- When uncertain, say what is known, what is inferred, and what would change the conclusion.
+
+## Prerequisites
+
+- **Hard**: `research/icp.md` (or `research/{slug}/icp.md`) must exist. If not, tell the user to run `/customer-discovery` first and stop.
+- **Soft**: `research/competitive-analysis.md`, `research/customer-feedback.md`, specs, and codebase context when available.
+
+## 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.
+
+When product path `{slug}` is active, read and write research under `research/{slug}/`, specs under `specs/{slug}/`.
+
+### 1. Load Context
+
+- Read `research/icp.md` — ICP segments, pain points, trigger events
+- Read `research/competitive-analysis.md` if it exists
+- Read `research/customer-feedback.md` if it exists — touchpoint experiences, satisfaction data
+- Read codebase structure when available — current product surfaces
+- Read CLAUDE.md, README for product context
+
+### 2. Define Journey Stages
+
+Identify the major stages of the customer journey. Use ICP evidence to determine the right granularity. Typical stages: awareness, consideration, acquisition, service/usage, retention, advocacy.
+
+### 3. Map Touchpoints per Stage
+
+For each stage, identify all customer touchpoints:
+- Digital touchpoints (website, app, email, social media, ads)
+- Human touchpoints (sales, support, community, word-of-mouth)
+- Physical touchpoints (packaging, events, printed materials)
+- Third-party touchpoints (review sites, marketplaces, partner integrations)
+
+### 4. Map Customer Actions per Stage
+
+For each stage, document what the customer does:
+- Primary actions (the main thing they're trying to accomplish)
+- Secondary actions (supporting or exploratory behavior)
+- Decision points (moments where they choose a path)
+
+### 5. Map Emotional State per Stage
+
+For each stage, assess the customer's emotional state:
+- Dominant emotion (using a simple scale: very negative → negative → neutral → positive → very positive)
+- Emotional drivers (what causes this emotional state)
+- Emotional trajectory (improving, declining, or stable)
+
+### 6. Map Backstage Processes per Stage
+
+For each stage, document the internal processes that support the customer experience:
+- Systems and tools involved
+- Team/role responsibilities
+- Data flows and handoffs
+- Automation vs manual processes
+
+### 7. Identify Pain Points per Stage
+
+For each stage, catalog specific pain points:
+- Customer-facing pains (friction, confusion, frustration, delays)
+- Backstage pains (manual work, data silos, coordination failures)
+- Root cause for each pain (process, technology, people, policy)
+
+### 8. Identify Opportunities per Stage
+
+For each stage, identify improvement opportunities:
+- Quick wins (low effort, high impact)
+- Strategic improvements (high effort, high impact)
+- Innovations (new touchpoints, channels, or approaches)
+- Priority based on pain severity and business impact
+
+### 9. Validate with User
+
+Present the canvas and ask for corrections, missing stages, touchpoints, or opportunities.
+
+## Output
+
+### `research/journey-map-customer-journey-canvas.md` (or `research/{slug}/journey-map-customer-journey-canvas.md`)
+
+```markdown
+# Customer Journey Canvas
+
+> Based on: research/icp.md[, other evidence]
+> Date: [current date]
+> Methodology: Stickdorn Customer Journey Canvas
+
+## Journey Canvas
+
+| Stage | Touchpoints | Customer Actions | Emotion | Backstage | Pain Points | Opportunities |
+|-------|------------|-----------------|---------|-----------|-------------|---------------|
+| [stage] | [touchpoints] | [actions] | [emotion] | [processes] | [pains] | [opportunities] |
+
+## Stage Detail
+
+### [Stage Name]
+
+**Touchpoints:**
+- [touchpoint]: [description and channel]
+
+**Customer Actions:**
+- [action]: [description]
+
+**Emotional State:** [emotion] ([driver])
+
+**Backstage Processes:**
+- [process]: [team/system responsible]
+
+**Pain Points:**
+| Pain | Severity | Root Cause | Evidence |
+|------|----------|-----------|----------|
+| [pain] | High/Medium/Low | Process/Technology/People/Policy | [source] |
+
+**Opportunities:**
+| Opportunity | Type | Effort | Impact | Evidence |
+|------------|------|--------|--------|----------|
+| [opportunity] | Quick win/Strategic/Innovation | Low/Medium/High | Low/Medium/High | [source] |
+
+## Evidence Matrix
+
+| Claim | Evidence Source | Evidence Type | Confidence |
+|-------|---------------|---------------|------------|
+| [claim] | [source] | Observed/Inferred/Hypothesized | High/Medium/Low |
+```
+
+## Constraints
+
+- Ground every canvas element in ICP, research, specs, feedback, or codebase evidence.
+- Do not prescribe UI or architecture — describe the journey, not the solution.
+- Present findings before writing.
+- Do not overwrite existing output without asking the user first.
+- This is a sub-skill — do not emit next-step routing.
+
+## 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/customer-journey-canvas-{topic}.html`.
+
+## Default Shipping Contract
+
+Follow the shared shipping contract convention in CLAUDE.md.

package/packs/customer-lifecycle/claude/journey-map/frameworks/customer-journey-canvas/archive/v0.4/SKILL.md

@@ -0,0 +1,189 @@
+---
+name: customer-journey-canvas
+description: Stickdorn customer journey canvas — stage×touchpoints×actions×emotion×backstage×pain×opportunities grid
+type: research
+version: v0.4
+invocation: sub-skill
+parent: journey-map
+---
+
+## 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 `npx skillpacks install <pack>` from the project shell, instead of the target skill. Global skills are always valid. Skills from this same pack are valid because the current skill is already running from that pack.
+
+# Customer Journey Canvas — Stickdorn Analysis
+
+## 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. Push back clearly and cite the evidence when the user appears to misunderstand.
+- For taste, prioritization, or subjective judgment calls: weigh user feedback heavily and adapt unless it conflicts with verified evidence.
+- When uncertain, say what is known, what is inferred, and what would change the conclusion.
+
+## Prerequisites
+
+- **Hard**: `research/icp.md` (or `research/{slug}/icp.md`) must exist. If not, tell the user to run `/customer-discovery` first and stop.
+- **Soft**: `research/competitive-analysis.md`, `research/customer-feedback.md`, specs, and codebase context when available.
+
+## 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.
+
+When product path `{slug}` is active, read and write research under `research/{slug}/`, specs under `specs/{slug}/`.
+
+### 1. Load Context
+
+- Read `research/icp.md` — ICP segments, pain points, trigger events
+- Read `research/competitive-analysis.md` if it exists
+- Read `research/customer-feedback.md` if it exists — touchpoint experiences, satisfaction data
+- Read codebase structure when available — current product surfaces
+- Read CLAUDE.md, README for product context
+
+### 2. Define Journey Stages
+
+Identify the major stages of the customer journey. Use ICP evidence to determine the right granularity. Typical stages: awareness, consideration, acquisition, service/usage, retention, advocacy.
+
+### 3. Map Touchpoints per Stage
+
+For each stage, identify all customer touchpoints:
+- Digital touchpoints (website, app, email, social media, ads)
+- Human touchpoints (sales, support, community, word-of-mouth)
+- Physical touchpoints (packaging, events, printed materials)
+- Third-party touchpoints (review sites, marketplaces, partner integrations)
+
+### 4. Map Customer Actions per Stage
+
+For each stage, document what the customer does:
+- Primary actions (the main thing they're trying to accomplish)
+- Secondary actions (supporting or exploratory behavior)
+- Decision points (moments where they choose a path)
+
+### 5. Map Emotional State per Stage
+
+For each stage, assess the customer's emotional state:
+- Dominant emotion (using a simple scale: very negative → negative → neutral → positive → very positive)
+- Emotional drivers (what causes this emotional state)
+- Emotional trajectory (improving, declining, or stable)
+
+### 6. Map Backstage Processes per Stage
+
+For each stage, document the internal processes that support the customer experience:
+- Systems and tools involved
+- Team/role responsibilities
+- Data flows and handoffs
+- Automation vs manual processes
+
+### 7. Identify Pain Points per Stage
+
+For each stage, catalog specific pain points:
+- Customer-facing pains (friction, confusion, frustration, delays)
+- Backstage pains (manual work, data silos, coordination failures)
+- Root cause for each pain (process, technology, people, policy)
+
+### 8. Identify Opportunities per Stage
+
+For each stage, identify improvement opportunities:
+- Quick wins (low effort, high impact)
+- Strategic improvements (high effort, high impact)
+- Innovations (new touchpoints, channels, or approaches)
+- Priority based on pain severity and business impact
+
+### 9. Validate with User
+
+Present the canvas and ask for corrections, missing stages, touchpoints, or opportunities.
+
+## Output
+
+### `research/journey-map-customer-journey-canvas.md` (or `research/{slug}/journey-map-customer-journey-canvas.md`)
+
+```markdown
+# Customer Journey Canvas
+
+> Based on: research/icp.md[, other evidence]
+> Date: [current date]
+> Methodology: Stickdorn Customer Journey Canvas
+
+## Journey Canvas
+
+| Stage | Touchpoints | Customer Actions | Emotion | Backstage | Pain Points | Opportunities |
+|-------|------------|-----------------|---------|-----------|-------------|---------------|
+| [stage] | [touchpoints] | [actions] | [emotion] | [processes] | [pains] | [opportunities] |
+
+## Stage Detail
+
+### [Stage Name]
+
+**Touchpoints:**
+- [touchpoint]: [description and channel]
+
+**Customer Actions:**
+- [action]: [description]
+
+**Emotional State:** [emotion] ([driver])
+
+**Backstage Processes:**
+- [process]: [team/system responsible]
+
+**Pain Points:**
+| Pain | Severity | Root Cause | Evidence |
+|------|----------|-----------|----------|
+| [pain] | High/Medium/Low | Process/Technology/People/Policy | [source] |
+
+**Opportunities:**
+| Opportunity | Type | Effort | Impact | Evidence |
+|------------|------|--------|--------|----------|
+| [opportunity] | Quick win/Strategic/Innovation | Low/Medium/High | Low/Medium/High | [source] |
+
+## Evidence Matrix
+
+| Claim | Evidence Source | Evidence Type | Confidence |
+|-------|---------------|---------------|------------|
+| [claim] | [source] | Observed/Inferred/Hypothesized | High/Medium/Low |
+```
+
+## Constraints
+
+- Ground every canvas element in ICP, research, specs, feedback, or codebase evidence.
+- Do not prescribe UI or architecture — describe the journey, not the solution.
+- Present findings before writing.
+- Do not overwrite existing output without asking the user first.
+- This is a sub-skill — do not emit next-step routing.
+
+## 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/customer-journey-canvas-{topic}.html`.
+
+## Default Shipping Contract
+
+Follow the shared shipping contract convention in CLAUDE.md.

package/packs/customer-lifecycle/claude/journey-map/frameworks/experience-map/ALIGNMENT-PAGE.md

@@ -57,7 +57,13 @@ 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-experience-map-research.md`; product-path mode uses `research/{slug}/_working/preliminary-experience-map-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-experience-map-research.md`; product-path mode uses `research/{slug}/_working/preliminary-experience-map-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.
+
+**Experience map translation.** Research focus: Gather evidence for doing, thinking, feeling, pain, delight, and channel transitions across the end-to-end experience. Separate observed evidence from inferred emotional arc, assumptions, confidence, and decision impact. Review/documentation format: Render an experience map with phase lanes, emotional arc, channel-transition markers, pain/delight moments, confidence by phase, and source gaps. Suggested user feedback: Ask reviewers to confirm phases, emotional highs/lows, channel transitions, pain/delight priority, confidence ratings, missing evidence, and journey synthesis implications. Apply the shared artifact-destination/proposed-file-changes de-duplication rule: combine them into one visual gate when they ask only the same path-destination question, and render separate gates when destination approval differs from downstream mutation scope, timing, or allowed files.
+
+**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.
 
 **Glossary Additions gate.** When this research introduces domain-specific terms, acronyms, or concept definitions that a reader outside the project would not know, include a `## Glossary Additions` section in the alignment page. Render a table of proposed terms with columns: Term, Definition, Source (`experience-map`), Category (business/tooling/workflow/technical/domain), and per-term Approve/Edit/Reject/Flag radio controls. Only user-approved terms are appended to the target glossary (`research/glossary.md` or `research/{slug}/glossary.md` for scoped paths) during the confirmed-page write step. When the skill operates in a product-path scope, ask whether each term belongs in the parent or scoped glossary; default to the scoped glossary.
 

package/packs/customer-lifecycle/claude/journey-map/frameworks/experience-map/CHANGELOG.md

@@ -1,5 +1,13 @@
 # experience-map changelog (claude)
 
+## v0.5 - 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.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-11
 
 - Added npm-aware install-route guidance to the Pack Availability Guard while preserving runner-specific in-agent pack install commands.

package/packs/customer-lifecycle/claude/journey-map/frameworks/experience-map/SKILL.md

@@ -2,14 +2,14 @@
 name: experience-map
 description: Adaptive Path experience map — emotional arc with doing/thinking/feeling layers, pain/delight moments, and channel transitions
 type: research
-version: v0.3
+version: v0.5
 invocation: sub-skill
 parent: journey-map
 ---
 
 ## 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. 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. Global skills are always valid. Skills from this same pack are valid because the current skill is already running from that pack.
 
 # Experience Map — Adaptive Path Analysis
 
@@ -28,7 +28,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.