skillpacks 0.1.0

package/packs/customer-lifecycle/claude/journey-map/archive/v0.0/SKILL.md

@@ -0,0 +1,91 @@
+---
+name: journey-map
+description: Map the full user and customer lifecycle from trigger and discovery through onboarding, aha, conversion, retention, expansion, and advocacy
+type: analysis
+version: v0.0
+argument-hint: "[optional: app, use case, persona, or lifecycle stage]"
+---
+
+## 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>` 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.
+
+# Journey Map — Lifecycle Overview
+
+
+
+Create or update the canonical lifecycle overview. This is the top-level map for user task journeys and the customer relationship lifecycle; deeper stage docs belong in `/onboarding-map`, `/conversion-map`, `/transaction-map`, `/retention-map`, `/expansion-map`, and `/lifecycle-metrics`.
+
+## Prerequisites
+
+- `research/icp.md` (or `research/{app}/icp.md` in monorepo mode) must exist — run `/icp` first.
+- Specs, competitive analysis, enterprise ICP, customer feedback, and codebase evidence are supporting context when present.
+
+## Workflow
+
+0. **App scope resolution**: If `$ARGUMENTS` names a subdirectory of `research/`, use `research/{app}/` and `specs/{app}/`. If `research/` has multiple app subdirectories and no app is specified, ask the user to choose. If one app subdirectory exists, use it automatically. Otherwise use flat `research/` and `specs/`.
+1. **Load context**: Read ICP, competitive analysis, enterprise ICP, customer feedback, existing lifecycle docs, specs, README/AGENTS/CLAUDE, and relevant source files when they clarify real product surfaces.
+2. **Map user journeys**: For each key persona, identify 3-5 core use cases, entry points, task steps, decision points, happy path, failure modes, outputs, and delta from current state.
+3. **Map customer lifecycle**: Cover trigger, discovery, evaluation, onboarding, aha moment, conversion, transaction, retention, expansion, advocacy, churn, and recovery.
+4. **Identify critical moments**: Name the 3-5 moments where the product wins or loses the user/customer, with evidence and success criteria.
+5. **Present before writing**: Summarize the lifecycle, evidence, open assumptions, and stage docs that should be split out. Ask what needs correction or product-specific context. Continue until validated.
+6. **Write only after validation**, archiving existing canonical files first when replacing them.
+
+## Deliverables
+
+- `research/journey-map.md` (or `research/{app}/journey-map.md`) — canonical lifecycle overview with links or references to deeper stage docs when they exist.
+- `research/journey-map-interview.md` (or `research/{app}/journey-map-interview.md`) — raw interview log and decisions.
+
+The output file must end with `## Next Steps` using "Pick one:" framing. Prefer the first missing deeper lifecycle map in this order: `/onboarding-map`, `/conversion-map`, `/transaction-map`, `/retention-map`, `/expansion-map`, `/lifecycle-metrics`; then route to `/spec-interview`, `/ux-variations`, `/metrics`, `/gtm`, or `/roadmap` when those are the better next step.
+
+## Output Shape
+
+```markdown
+# Journey Map
+
+> Based on: research/icp.md[, other evidence]
+> Date: YYYY-MM-DD
+
+## Summary
+## User Journeys
+## Customer Lifecycle
+## Critical Moments
+## Stage Detail Index
+## Journey Gaps
+## Next Steps
+```
+
+## Alignment Page
+
+When this skill produces durable deliverables (research, specs, plans, reports, prototypes, or any document output), build a full-depth HTML alignment page at `alignment/journey-map-{topic}.html`. Use a normalized topic slug derived from the app, feature, research subject, report subject, or output filename.
+
+**Full content requirement.** The alignment page must contain the complete content of every proposed markdown deliverable -- every section, every finding, every detail, every list item. It is a thorough interactive review document, not a summary. Render the full deliverable content in clean, readable HTML with appropriate hierarchy, styling, and navigation. If the skill writes multiple scoped deliverables in one run, build one alignment page that contains all deliverables with anchor-linked navigation. Durable tracker artifacts, such as `research/assumption-tracker.md`, remain canonical markdown outputs but must also be fully rendered into the alignment page before approval.
+
+**Dark-mode styling.** Use a dark color scheme by default. Base CSS variables: `--bg: #0d1117; --surface: #161b22; --border: #30363d; --text: #c9d1d9; --text-muted: #8b949e; --accent: #58a6ff; --green: #3fb950; --red: #f85149; --orange: #d29922; --purple: #bc8cff;`. Apply `background: var(--bg); color: var(--text);` on body. Use `--surface` for cards, nav, and table headers. Use `--border` for all borders. Use `--purple` for question blocks and gate headings. Use `--accent` for links and section headings. Keep headings `color: #fff` or `var(--accent)` for hierarchy. Question block backgrounds should use `#1c2333`.
+
+**Alignment gates.** Treat gates as explicit review sections inside the HTML page. A gate blocks finalization until its required inline questions are answered and compiled into YAML. Include every gate that applies to the skill output, and include these gate types whenever relevant: evidence coverage, assumptions/confidence, scope/non-goals, candidate/verdict decisions, artifact destination, proposed file changes, coverage checkpoint, and post-approval route.
+
+**Report-only research gates.** For report-only or pre-approval research skills, the alignment page must explicitly contain evidence coverage, assumptions/confidence, recommended path, proposed file changes, and approval gates before any canonical research, spec, or task file is created or updated.
+
+**Discovery-specific gates.** Render evidence coverage, assumptions/confidence, recommended path, artifact destination, proposed file changes, approval, and post-approval route as gates before creating or updating canonical discovery artifacts.
+
+
+**Required inline questions.** Each gate must contain at least one required inline question placed directly under the content it governs, inside a visually distinct question block. Each question must use radio-button inputs and include two standing options after the skill-generated choices: "Other / None of the above" backed by a multi-line text box for free-form input, and "Need clarification" backed by an optional notes box where the user can explain what is unclear. When any radio option other than "Other" or "Need clarification" is selected, show an optional "Additional notes" text box beneath it so the user can qualify their choice. Generate questions based on what genuinely needs user input -- do not add filler questions. Do not create a separate bottom "Decisions & Clarifications" section.
+
+**Gate YAML contract.** At the bottom of the page, include a "Compile Answers" button that aggregates answers from all inline gate questions throughout the page, including free-text notes. The button remains disabled until every required question has a selection, shows a count of remaining unanswered questions, and scrolls to the first unanswered question if clicked early. When every question is answered, generate a structured YAML block with one item per gate answer using this stable shape: `section`, `gate_type`, `status` (`answered`, `other`, or `needs-clarification`), `answer`, optional `notes`, and optional `target_artifact` or `target_path` when the gate controls file output. After successful compilation, automatically attempt to copy the YAML to the clipboard with the Clipboard API, display copy status, and display the YAML in a read-only textarea with an explicit "Copy YAML" button. The copy button must retry clipboard copy when supported and fall back to selecting the textarea contents when clipboard access is unavailable or blocked.
+
+**Pre-approval stop.** Before user approval, the next action is review of the HTML alignment page, not downstream routing. Ask the user to review the page and provide the compiled YAML answers. Do not include `Recommended next skill`, `Recommended next command`, or downstream routing language until after compiled YAML has been provided and the approved artifacts have been written or updated.
+
+**Diff highlighting on updates.** When the agent updates an existing alignment page after receiving compiled answers, highlight what changed since the previous version. The agent chooses inline annotation or side-by-side layout per situation.
+
+**Archiving.** Before replacing an existing alignment page, archive it to `docs/history/archive/YYYY-MM-DD/HHMMSS/alignment/journey-map-{topic}.html`.
+
+**Browser open.** Attempt to open the resulting HTML page in the browser and report whether the open succeeded or was blocked. A blocked browser-open attempt does not make the skill fail when the files were written correctly.
+
+## Constraints
+
+- Keep this file as the overview; put step-level stage detail in the focused lifecycle skills.
+- Ground every important step in ICP, research, specs, feedback, or codebase evidence.
+- Do not prescribe UI or architecture.
+- Present findings before writing.
+- Follow the archive-first replacement policy for canonical research/spec documents.

package/packs/customer-lifecycle/claude/journey-map/archive/v0.1/SKILL.md

@@ -0,0 +1,91 @@
+---
+name: journey-map
+description: Map the full user and customer lifecycle from trigger and discovery through onboarding, aha, conversion, retention, expansion, and advocacy
+type: analysis
+version: v0.1
+argument-hint: "[optional: app, use case, persona, or lifecycle stage]"
+---
+
+## 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>` 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.
+
+# Journey Map — Lifecycle Overview
+
+
+
+Create or update the canonical lifecycle overview. This is the top-level map for user task journeys and the customer relationship lifecycle; deeper stage docs belong in `/onboarding-map`, `/conversion-map`, `/transaction-map`, `/retention-map`, `/expansion-map`, and `/lifecycle-metrics`.
+
+## Prerequisites
+
+- `research/icp.md` (or `research/{app}/icp.md` in monorepo mode) must exist — run `/icp` first.
+- Specs, competitive analysis, enterprise ICP, customer feedback, and codebase evidence are supporting context when present.
+
+## Workflow
+
+0. **App scope resolution**: If `$ARGUMENTS` names a subdirectory of `research/`, use `research/{app}/` and `specs/{app}/`. If `research/` has multiple app subdirectories and no app is specified, ask the user to choose. If one app subdirectory exists, use it automatically. Otherwise use flat `research/` and `specs/`.
+1. **Load context**: Read ICP, competitive analysis, enterprise ICP, customer feedback, existing lifecycle docs, specs, README/AGENTS/CLAUDE, and relevant source files when they clarify real product surfaces.
+2. **Map user journeys**: For each key persona, identify 3-5 core use cases, entry points, task steps, decision points, happy path, failure modes, outputs, and delta from current state.
+3. **Map customer lifecycle**: Cover trigger, discovery, evaluation, onboarding, aha moment, conversion, transaction, retention, expansion, advocacy, churn, and recovery.
+4. **Identify critical moments**: Name the 3-5 moments where the product wins or loses the user/customer, with evidence and success criteria.
+5. **Present before writing**: Summarize the lifecycle, evidence, open assumptions, and stage docs that should be split out. Ask what needs correction or product-specific context. Continue until validated.
+6. **Write only after validation**, archiving existing canonical files first when replacing them.
+
+## Deliverables
+
+- `research/journey-map.md` (or `research/{app}/journey-map.md`) — canonical lifecycle overview with links or references to deeper stage docs when they exist.
+- `research/journey-map-interview.md` (or `research/{app}/journey-map-interview.md`) — raw interview log and decisions.
+
+The output file must end with `## Next Steps` using "Pick one:" framing. Default AFPS routing after the overview is `/positioning` when `research/positioning.md` is missing, because positioning should use ICP, competitive analysis, and journey evidence. Then route to `/ux-variations`, `/ui-interview`, prototype work, `/uat --variant-evaluation`, `/consolidate-variations`, `/research-roadmap --post-prototype`, `/spec-interview`, and `/roadmap` as evidence becomes available. Recommend deeper lifecycle maps (`/onboarding-map`, `/conversion-map`, `/transaction-map`, `/retention-map`, `/expansion-map`, `/lifecycle-metrics`) only when the overview exposes a specific stage risk that needs detail before positioning or UX work.
+
+## Output Shape
+
+```markdown
+# Journey Map
+
+> Based on: research/icp.md[, other evidence]
+> Date: YYYY-MM-DD
+
+## Summary
+## User Journeys
+## Customer Lifecycle
+## Critical Moments
+## Stage Detail Index
+## Journey Gaps
+## Next Steps
+```
+
+## Alignment Page
+
+When this skill produces durable deliverables (research, specs, plans, reports, prototypes, or any document output), build a full-depth HTML alignment page at `alignment/journey-map-{topic}.html`. Use a normalized topic slug derived from the app, feature, research subject, report subject, or output filename.
+
+**Full content requirement.** The alignment page must contain the complete content of every proposed markdown deliverable -- every section, every finding, every detail, every list item. It is a thorough interactive review document, not a summary. Render the full deliverable content in clean, readable HTML with appropriate hierarchy, styling, and navigation. If the skill writes multiple scoped deliverables in one run, build one alignment page that contains all deliverables with anchor-linked navigation. Durable tracker artifacts, such as `research/assumption-tracker.md`, remain canonical markdown outputs but must also be fully rendered into the alignment page before approval.
+
+**Dark-mode styling.** Use a dark color scheme by default. Base CSS variables: `--bg: #0d1117; --surface: #161b22; --border: #30363d; --text: #c9d1d9; --text-muted: #8b949e; --accent: #58a6ff; --green: #3fb950; --red: #f85149; --orange: #d29922; --purple: #bc8cff;`. Apply `background: var(--bg); color: var(--text);` on body. Use `--surface` for cards, nav, and table headers. Use `--border` for all borders. Use `--purple` for question blocks and gate headings. Use `--accent` for links and section headings. Keep headings `color: #fff` or `var(--accent)` for hierarchy. Question block backgrounds should use `#1c2333`.
+
+**Alignment gates.** Treat gates as explicit review sections inside the HTML page. A gate blocks finalization until its required inline questions are answered and compiled into YAML. Include every gate that applies to the skill output, and include these gate types whenever relevant: evidence coverage, assumptions/confidence, scope/non-goals, candidate/verdict decisions, artifact destination, proposed file changes, coverage checkpoint, and post-approval route.
+
+**Report-only research gates.** For report-only or pre-approval research skills, the alignment page must explicitly contain evidence coverage, assumptions/confidence, recommended path, proposed file changes, and approval gates before any canonical research, spec, or task file is created or updated.
+
+**Discovery-specific gates.** Render evidence coverage, assumptions/confidence, recommended path, artifact destination, proposed file changes, approval, and post-approval route as gates before creating or updating canonical discovery artifacts.
+
+
+**Required inline questions.** Each gate must contain at least one required inline question placed directly under the content it governs, inside a visually distinct question block. Each question must use radio-button inputs and include two standing options after the skill-generated choices: "Other / None of the above" backed by a multi-line text box for free-form input, and "Need clarification" backed by an optional notes box where the user can explain what is unclear. When any radio option other than "Other" or "Need clarification" is selected, show an optional "Additional notes" text box beneath it so the user can qualify their choice. Generate questions based on what genuinely needs user input -- do not add filler questions. Do not create a separate bottom "Decisions & Clarifications" section.
+
+**Gate YAML contract.** At the bottom of the page, include a "Compile Answers" button that aggregates answers from all inline gate questions throughout the page, including free-text notes. The button remains disabled until every required question has a selection, shows a count of remaining unanswered questions, and scrolls to the first unanswered question if clicked early. When every question is answered, generate a structured YAML block with one item per gate answer using this stable shape: `section`, `gate_type`, `status` (`answered`, `other`, or `needs-clarification`), `answer`, optional `notes`, and optional `target_artifact` or `target_path` when the gate controls file output. After successful compilation, automatically attempt to copy the YAML to the clipboard with the Clipboard API, display copy status, and display the YAML in a read-only textarea with an explicit "Copy YAML" button. The copy button must retry clipboard copy when supported and fall back to selecting the textarea contents when clipboard access is unavailable or blocked.
+
+**Pre-approval stop.** Before user approval, the next action is review of the HTML alignment page, not downstream routing. Ask the user to review the page and provide the compiled YAML answers. Do not include `Recommended next skill`, `Recommended next command`, or downstream routing language until after compiled YAML has been provided and the approved artifacts have been written or updated.
+
+**Diff highlighting on updates.** When the agent updates an existing alignment page after receiving compiled answers, highlight what changed since the previous version. The agent chooses inline annotation or side-by-side layout per situation.
+
+**Archiving.** Before replacing an existing alignment page, archive it to `docs/history/archive/YYYY-MM-DD/HHMMSS/alignment/journey-map-{topic}.html`.
+
+**Browser open.** Attempt to open the resulting HTML page in the browser and report whether the open succeeded or was blocked. A blocked browser-open attempt does not make the skill fail when the files were written correctly.
+
+## Constraints
+
+- Keep this file as the overview; put step-level stage detail in the focused lifecycle skills.
+- Ground every important step in ICP, research, specs, feedback, or codebase evidence.
+- Do not prescribe UI or architecture.
+- Present findings before writing.
+- Follow the archive-first replacement policy for canonical research/spec documents.

package/packs/customer-lifecycle/claude/journey-map/archive/v0.10/SKILL.md

@@ -0,0 +1,276 @@
+---
+name: journey-map
+description: Orchestrator — detect pre-product vs product-exists mode, recommend journey-mapping frameworks, synthesize outputs into unified lifecycle overview
+type: analysis
+version: v0.10
+argument-hint: "[optional: \"product\" | \"--synthesize\" | app, use case, persona]"
+invocation: orchestrator
+---
+
+## 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>` 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.
+
+# Journey Map — Orchestrator
+
+This is an **orchestrator skill** using the parent router delegation pattern. It detects context, recommends applicable journey-mapping frameworks, and synthesizes their outputs. Individual frameworks live as child skills under `frameworks/`.
+
+## Report-First Approval Gate
+
+Default to report-only: present findings, evidence coverage, assumptions, recommended artifact path, and proposed file changes in a pre-approval alignment page plus a concise conversation summary for user approval before creating or updating canonical research, spec, or task files.
+
+Do not write or overwrite synthesized deliverables until the user explicitly approves, unless the user invoked an explicit write/update/fix mode or clearly asked to write files upfront. Raw evidence capture may be persisted before analysis when reproducibility requires it; report those raw paths separately and still gate synthesized research/report writes.
+
+When stopping for approval, build and attempt to open the alignment preview page first, then ask the user to review it and approve, question, or request adjustments. 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.
+
+## Prerequisites
+
+- **Hard**: `research/icp.md` (or `research/{slug}/icp.md` in product-path mode) must exist — run `/customer-discovery` first.
+- **Soft**: Read these if they exist:
+  - `research/competitive-analysis.md` — competitor landscape
+  - `research/customer-feedback.md` — real customer language
+  - Specs, README/CLAUDE, and relevant source files for product context
+
+## Operational Modes
+
+### Mode A: Framework Selection (default first invocation)
+
+Activated by: `/journey-map` or `/journey-map [focus area]` (no special flags).
+
+### Mode B: Synthesis
+
+Activated by: `/journey-map --synthesize`
+
+### Mode C: Product-Exists Shortcut
+
+Activated by: `/journey-map product`
+
+---
+
+## 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.
+
+0b. **Product-path manifest**: Read `research/.progress.yaml` when present. Normalize `active_path` (singular legacy) to `active_paths` (plural list) when reading; treat legacy `abandoned` as `archived` and exclude archived/deferred/revisit/promoted paths plus `research/_archive/` scopes from active target selection. Scope the journey map to the active product path by default. When journey mapping reveals lifecycle stages or user flows that only apply to a deferred product path, add a `## Product Path Implications` section noting the finding and recommending `/product-line fork` if it implies a new product surface.
+
+### 1. Mode Detection
+
+Detect **pre-product mode** (default) or **product-exists mode**:
+
+**Pre-product mode** activates when:
+- No production codebase with live users detected, AND
+- No `research/customer-feedback.md` with post-launch customer evidence, AND
+- `$ARGUMENTS` does not contain "product"
+
+Available frameworks in pre-product mode:
+- `jtbd-timeline` (default) — Moesta/Switch timeline with push/pull/anxiety/habit forces
+- `experience-map` (default) — Adaptive Path emotional arc with doing/thinking/feeling
+- `customer-journey-canvas` (optional) — Stickdorn stage×touchpoints×actions canvas
+- `service-blueprint` (optional) — Shostack front-stage/backstage/support lines
+- `user-story-map` (optional) — Jeff Patton activity→task→story hierarchy
+
+**Product-exists mode** activates when:
+- Production code or deployment exists, OR
+- `research/customer-feedback.md` exists with real customer data, OR
+- `$ARGUMENTS` contains "product"
+
+Available frameworks in product-exists mode:
+- `service-blueprint` (default) — operational gaps visible with a running product
+- `user-story-map` (default) — release slicing grounded in real usage
+- `customer-journey-canvas` (optional) — full-stage touchpoint audit
+- `experience-map` (optional) — emotional arc refresh with real feedback
+- `jtbd-timeline` (optional) — switching timeline with post-launch evidence
+
+### 2. Load Context
+
+- Read `research/icp.md` — ICP segments, pain points, value props, trigger events
+- Read `research/competitive-analysis.md` if it exists — competitor landscape
+- Read `research/customer-feedback.md` if it exists — real customer language
+- Read CLAUDE.md, README for product context
+- Read any existing `research/journey-map-*.md` intermediate artifacts (from prior runs)
+
+### 3. Mode A — Framework Selection
+
+Build an alignment page with:
+
+1. **Mode explanation**: which mode was detected and why (evidence for detection)
+2. **Available evidence summary**: what research exists and what's missing
+3. **Multi-select framework section**: checkboxes for each available framework with:
+   - Framework name and one-line description
+   - Why it's recommended or optional for this context
+   - Pre-checked defaults based on detected mode (see mode detection above)
+4. **Execution plan explanation**: selected frameworks will be written to `tasks/todo.md` for sequential `/exec` execution
+5. **Approval gate**: framework selection confirmation
+
+After user approval via compiled YAML (which includes `selected_frameworks` list):
+
+Write selected frameworks as sequential steps in `tasks/todo.md`:
+
+```markdown
+## Journey Map Framework Execution
+
+- [ ] Run `/journey-map/frameworks/jtbd-timeline` — JTBD switching timeline
+- [ ] Run `/journey-map/frameworks/experience-map` — Adaptive Path experience map
+- [ ] Synthesize: `/journey-map --synthesize` — Combine framework outputs into research/journey-map.md
+```
+
+Only include frameworks the user selected. Always append the synthesis step last.
+
+Stop after writing `tasks/todo.md`. The user runs `/exec` to execute each framework sequentially.
+
+### 4. Mode B — Synthesis (`/journey-map --synthesize`)
+
+Read all intermediate framework outputs:
+- `research/journey-map-jtbd-timeline.md`
+- `research/journey-map-experience-map.md`
+- `research/journey-map-customer-journey-canvas.md`
+- `research/journey-map-service-blueprint.md`
+- `research/journey-map-user-story-map.md`
+
+At least one must exist. If none exist, tell user to run framework selection first.
+
+Synthesize into unified `research/journey-map.md`:
+
+**Synthesis includes:**
+- Unified customer lifecycle: trigger, discovery, evaluation, onboarding, aha moment, conversion, transaction, retention, expansion, advocacy, churn, recovery
+- User journey map per key persona with core use cases, entry points, task steps, decision points, happy path, failure modes
+- Critical moments: the 3-5 moments where the product wins or loses the user/customer
+- Evidence matrix: each claim mapped to which framework(s) support it
+- Confidence levels per claim (strong/moderate/hypothesized)
+- Stage detail index: links to deeper stage docs when they exist
+- Journey gaps: stages needing deeper analysis
+- Mode header: `> Mode: Pre-Product (hypothesized)` or `> Mode: Product-Exists (grounded)`
+
+Build alignment page for synthesis approval with:
+- Full proposed `research/journey-map.md` content
+- Evidence matrix combining all framework sources
+- Confidence/assumption register
+- Critical-moment evidence matrix
+- Proposed file changes gate
+- Approval gate
+
+After approval: write `research/journey-map.md`, then emit next-step routing.
+
+### 5. Mode C — Product-Exists Shortcut
+
+Skip multi-select. Build an alignment page for the shortcut execution plan with:
+
+1. **Shortcut explanation**: product-exists shortcut selected and why `service-blueprint` + `user-story-map` are the queued defaults
+2. **Evidence readiness**: available product/customer evidence and any caveats
+3. **Proposed execution plan**: the exact `tasks/todo.md` framework queue shown below
+4. **Approval gate**: require final compiled YAML approval before writing `tasks/todo.md`
+
+Do not write `tasks/todo.md` before alignment approval. The next action is review of the HTML alignment page.
+
+After user approval via final compiled YAML, write this execution plan to `tasks/todo.md`:
+
+```markdown
+## Journey Map Framework Execution
+
+- [ ] Run `/journey-map/frameworks/service-blueprint` — Shostack service blueprint
+- [ ] Run `/journey-map/frameworks/user-story-map` — Jeff Patton user story map
+- [ ] Synthesize: `/journey-map --synthesize` — Write research/journey-map.md
+```
+
+Stop — user runs `/exec`.
+
+### 6. Next Steps (after synthesis only)
+
+Priority-ordered decision tree — recommend the **first** match:
+
+1. **Blocking optional research trigger** — the overview exposed a stage, fit, measurement, or product-loop risk that must be resolved before positioning or UX choices harden → use the Optional Research Trigger Map below. Cite the exact journey evidence, why it blocks the next AFPS step, and which existing framework skill owns it.
+2. **Positioning missing** (`research/positioning.md` does not exist) → check `.agents/project.json.enabled_packs` for `business-discovery` — if `business-discovery` is not enabled, recommend `/pack install business-discovery` first; if `business-discovery` is enabled, recommend `/positioning` — Positioning needs ICP, competitive analysis, and journey evidence, so it is the natural next step.
+3. **Positioning done, user-flow map missing** → check `.agents/project.json.enabled_packs` for `product-design` — if `product-design` is not enabled, recommend `/pack install product-design` first; if `product-design` is enabled, recommend `/user-flow-map` — Map screen flow, decisions, branches, states, and low-fidelity wireframe structure before UI requirements.
+4. **Never** recommend `/spec-interview` from this skill — it is many steps downstream in the AFPS chain.
+
+## Optional Research Trigger Map
+
+These detours are conditional framework owners, not required AFPS chain links. Use them only when the journey evidence shows that the answer will change positioning, product-loop direction, flow/design shape, or prototype choices. When the trigger is absent, continue to `/positioning` or `/user-flow-map` using the decision tree above.
+
+| Journey signal | Existing owner | Trigger threshold |
+| --- | --- | --- |
+| Signup, setup, activation, first-success, or time-to-value path is unclear | `/onboarding-map` | The journey cannot identify the first success path, onboarding drop-offs, or activation criteria well enough to shape UX. |
+| Evaluation, trial, pricing decision, objections, or buyer roles are unresolved | `/conversion-map` | Conversion decision logic affects the primary screen flow, offer, or proof sequence. |
+| Purchase, checkout, payment, fulfillment, refund, dispute, or trust state is material | `/transaction-map` | Transaction mechanics create product risk before UX/prototype choices. |
+| Repeat-use job, return trigger, churn risk, recovery path, or retention signal is unclear | `/retention-map` | The product needs a natural return model before designing engagement, lifecycle messages, or saved state. |
+| Stage instrumentation, leading indicators, or lifecycle handoff metrics are unclear | `/lifecycle-metrics` | The journey has stage risks but needs measurement before growth or implementation planning. Prefer this over `/hook-model` for enterprise, infrastructure, transactional, or naturally infrequent products. |
+| Product value depends on repeat use, habit formation, engagement loops, retention triggers, saved state, social rewards, or investment compounding | Check `.agents/project.json.enabled_packs` for `business-growth` — if missing, recommend `/pack install business-growth`; if enabled, recommend `/hook-model` | Use only for consumer, prosumer, PLG, marketplace, community, or B2B-with-consumer-component products where habit-loop design should shape flow and prototype choices before `/user-flow-map`. Do not force this on B2B/enterprise, infrastructure, transactional, or naturally infrequent products; route those to `/lifecycle-metrics` or, when `business-growth` is enabled and a broader success framework is needed, `/metrics`. |
+| Expansion, upgrade, seat growth, referral, advocacy, or land-and-expand path is material | `/expansion-map` | Expansion mechanics change lifecycle sequencing, account roles, or product surface priorities. |
+| Jobs, pains, gains, aha moment, or solution fit are weak, disputed, or need explicit scoring | Check `.agents/project.json.enabled_packs` for `business-discovery` — if missing, recommend `/pack install business-discovery`; if enabled, recommend `/value-prop-canvas` | Use the existing Strategyzer-style framework only when fit risk would make positioning or UX premature. |
+| Revenue, channel, cost, defensibility, or unfair-advantage assumptions are material risks | Check `.agents/project.json.enabled_packs` for `business-discovery` — if missing, recommend `/pack install business-discovery`; if enabled, recommend `/lean-canvas` | Use the existing Ash Maurya Lean Canvas framework when the journey exposes business-model risk before UX/prototype decisions. |
+| Pricing gates, packaging, free-to-paid timing, or willingness-to-pay moments are central to the journey | Check `.agents/project.json.enabled_packs` for `business-growth` — if missing, recommend `/pack install business-growth`; if enabled, recommend `/monetization` | Use when pricing architecture must be grounded before conversion, transaction, or prototype choices. |
+| Acquisition source, launch channel, messaging route, or early traction mechanism is a journey blocker | Check `.agents/project.json.enabled_packs` for `business-growth` — if missing, recommend `/pack install business-growth`; if enabled, recommend `/gtm` | Use after enough ICP/competitive/journey evidence exists and the channel path changes product or UX priorities. |
+
+`/growth-model` is an existing Reforge-style framework owner for compounding acquisition, retention, and monetization loops, but do not route to it directly from `journey-map` unless metrics/GTM prerequisites are already satisfied. In most AFPS cases, `/hook-model`, `/metrics`, `/monetization`, or `/gtm` is the earlier business-growth detour.
+
+## Output
+
+### Mode A output: `tasks/todo.md` update
+
+Framework execution steps (see section 3 above).
+
+### Mode B output: `research/journey-map.md` (or `research/{slug}/journey-map.md`)
+
+```markdown
+# Journey Map
+
+> Based on: [list of framework outputs used]
+> Date: [current date]
+> Mode: Pre-Product (hypothesized) | Product-Exists (grounded)
+> Frameworks applied: [list]
+
+## Summary
+
+## User Journeys
+
+## Customer Lifecycle
+
+## Critical Moments
+
+## Evidence Matrix
+
+| Claim | Supporting Framework(s) | Evidence | Confidence |
+|-------|------------------------|----------|------------|
+| [claim] | JTBD Timeline / Experience Map / Service Blueprint / User Story Map / Customer Journey Canvas | [source] | Strong / Moderate / Hypothesized |
+
+## Stage Detail Index
+
+## Journey Gaps
+
+## Next Steps
+```
+
+## 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/journey-map-{topic}.html`.
+
+**Journey research translation.** Render the lifecycle overview as approval-ready research, not a chat-only summary. The alignment page must include the proposed `research/journey-map.md` content, proposed file changes, evidence coverage by journey stage, assumptions/confidence register, critical-moment evidence matrix, and approval gates before canonical research files are created or updated.
+
+Before approval, the next action is review of `alignment/journey-map-{topic}.html` and compiled YAML answers from that page. Do not treat a plain-text lifecycle summary as a substitute for the HTML alignment preview.
+
+## Constraints
+
+- **Parent does not execute frameworks.** It selects and queues them. `/exec` handles execution.
+- **Synthesis requires at least one framework output.** Do not synthesize from zero evidence.
+- **Mode detection is evidence-based.** Do not override mode detection without user confirmation.
+- Ground every important step in ICP, research, specs, feedback, or codebase evidence.
+- Do not prescribe UI or architecture.
+- Present findings before writing.
+- Follow the archive-first replacement policy for canonical research/spec documents.
+- Do not overwrite existing `research/journey-map.md` without asking the user first.
+
+## Default Shipping Contract
+
+Follow the shared shipping contract convention in CLAUDE.md.

package/packs/customer-lifecycle/claude/journey-map/archive/v0.2/SKILL.md

@@ -0,0 +1,79 @@
+---
+name: journey-map
+description: Map the full user and customer lifecycle from trigger and discovery through onboarding, aha, conversion, retention, expansion, and advocacy
+type: analysis
+version: v0.2
+argument-hint: "[optional: app, use case, persona, or lifecycle stage]"
+---
+
+## 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>` 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.
+
+# Journey Map — Lifecycle Overview
+
+
+
+Create or update the canonical lifecycle overview. This is the top-level map for user task journeys and the customer relationship lifecycle; deeper stage docs belong in `/onboarding-map`, `/conversion-map`, `/transaction-map`, `/retention-map`, `/expansion-map`, and `/lifecycle-metrics`.
+
+## Prerequisites
+
+- `research/icp.md` (or `research/{app}/icp.md` in monorepo mode) must exist — run `/icp` first.
+- Specs, competitive analysis, enterprise ICP, customer feedback, and codebase evidence are supporting context when present.
+
+## Workflow
+
+0. **App scope resolution**: If `$ARGUMENTS` names a subdirectory of `research/`, use `research/{app}/` and `specs/{app}/`. If `research/` has multiple app subdirectories and no app is specified, ask the user to choose. If one app subdirectory exists, use it automatically. Otherwise use flat `research/` and `specs/`.
+1. **Load context**: Read ICP, competitive analysis, enterprise ICP, customer feedback, existing lifecycle docs, specs, README/AGENTS/CLAUDE, and relevant source files when they clarify real product surfaces.
+2. **Map user journeys**: For each key persona, identify 3-5 core use cases, entry points, task steps, decision points, happy path, failure modes, outputs, and delta from current state.
+3. **Map customer lifecycle**: Cover trigger, discovery, evaluation, onboarding, aha moment, conversion, transaction, retention, expansion, advocacy, churn, and recovery.
+4. **Identify critical moments**: Name the 3-5 moments where the product wins or loses the user/customer, with evidence and success criteria.
+5. **Present before writing**: Summarize the lifecycle, evidence, open assumptions, and stage docs that should be split out. Ask what needs correction or product-specific context. Continue until validated.
+6. **Write only after validation**, archiving existing canonical files first when replacing them.
+
+## Deliverables
+
+- `research/journey-map.md` (or `research/{app}/journey-map.md`) — canonical lifecycle overview with links or references to deeper stage docs when they exist.
+- `research/journey-map-interview.md` (or `research/{app}/journey-map-interview.md`) — raw interview log and decisions.
+
+The output file must end with `## Next Steps` using "Pick one:" framing. Follow the Next-Step Routing contract below to decide the recommendation.
+
+## Next-Step Routing
+
+Priority-ordered decision tree — recommend the **first** match:
+
+1. **Positioning missing** (`research/positioning.md` does not exist) → recommend `/positioning` (business-discovery pack). Positioning needs ICP, competitive analysis, and journey evidence, so it is the natural next step.
+2. **Positioning done, UX variations missing** → recommend `/ux-variations` (product-design pack).
+3. **Specific stage risk** — the overview exposed a lifecycle-stage risk that must be resolved before positioning or UX work can proceed → recommend the relevant lifecycle map (`/onboarding-map`, `/conversion-map`, `/transaction-map`, `/retention-map`, `/expansion-map`, or `/lifecycle-metrics`). Cite the risk and explain why it blocks the next AFPS step.
+4. **Never** recommend `/spec-interview` from this skill — it is many steps downstream in the AFPS chain.
+
+Cross-pack notes: `/positioning` lives in the `business-discovery` pack; `/ux-variations` lives in the `product-design` pack. Check `.agents/project.json` `enabled_packs` and recommend `/pack install <pack>` when the target pack is not enabled.
+
+## Output Shape
+
+```markdown
+# Journey Map
+
+> Based on: research/icp.md[, other evidence]
+> Date: YYYY-MM-DD
+
+## Summary
+## User Journeys
+## Customer Lifecycle
+## Critical Moments
+## Stage Detail Index
+## Journey Gaps
+## Next Steps
+```
+
+## Alignment Page
+
+Follow the shared Alignment Page convention in CLAUDE.md. Output: `alignment/journey-map-{topic}.html`.
+
+## Constraints
+
+- Keep this file as the overview; put step-level stage detail in the focused lifecycle skills.
+- Ground every important step in ICP, research, specs, feedback, or codebase evidence.
+- Do not prescribe UI or architecture.
+- Present findings before writing.
+- Follow the archive-first replacement policy for canonical research/spec documents.

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

@@ -0,0 +1,77 @@
+---
+name: journey-map
+description: Map the full user and customer lifecycle from trigger and discovery through onboarding, aha, conversion, retention, expansion, and advocacy
+type: analysis
+version: v0.3
+argument-hint: "[optional: app, use case, persona, or lifecycle stage]"
+---
+
+## 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>` 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.
+
+# Journey Map — Lifecycle Overview
+
+
+
+Create or update the canonical lifecycle overview. This is the top-level map for user task journeys and the customer relationship lifecycle; deeper stage docs belong in `/onboarding-map`, `/conversion-map`, `/transaction-map`, `/retention-map`, `/expansion-map`, and `/lifecycle-metrics`.
+
+## Prerequisites
+
+- `research/icp.md` (or `research/{app}/icp.md` in monorepo mode) must exist — run `/icp` first.
+- Specs, competitive analysis, enterprise ICP, customer feedback, and codebase evidence are supporting context when present.
+
+## Workflow
+
+0. **App scope resolution**: If `$ARGUMENTS` names a subdirectory of `research/`, use `research/{app}/` and `specs/{app}/`. If `research/` has multiple app subdirectories and no app is specified, ask the user to choose. If one app subdirectory exists, use it automatically. Otherwise use flat `research/` and `specs/`.
+1. **Load context**: Read ICP, competitive analysis, enterprise ICP, customer feedback, existing lifecycle docs, specs, README/AGENTS/CLAUDE, and relevant source files when they clarify real product surfaces.
+2. **Map user journeys**: For each key persona, identify 3-5 core use cases, entry points, task steps, decision points, happy path, failure modes, outputs, and delta from current state.
+3. **Map customer lifecycle**: Cover trigger, discovery, evaluation, onboarding, aha moment, conversion, transaction, retention, expansion, advocacy, churn, and recovery.
+4. **Identify critical moments**: Name the 3-5 moments where the product wins or loses the user/customer, with evidence and success criteria.
+5. **Present before writing**: Summarize the lifecycle, evidence, open assumptions, and stage docs that should be split out. Ask what needs correction or product-specific context. Continue until validated.
+6. **Write only after validation**, archiving existing canonical files first when replacing them.
+
+## Deliverables
+
+- `research/journey-map.md` (or `research/{app}/journey-map.md`) — canonical lifecycle overview with links or references to deeper stage docs when they exist.
+- `research/journey-map-interview.md` (or `research/{app}/journey-map-interview.md`) — raw interview log and decisions.
+
+The output file must end with `## Next Steps` using "Pick one:" framing. Follow the Next-Step Routing contract below to decide the recommendation.
+
+## Next-Step Routing
+
+Priority-ordered decision tree — recommend the **first** match:
+
+1. **Positioning missing** (`research/positioning.md` does not exist) → check `.agents/project.json.enabled_packs` for `business-discovery` — if `business-discovery` is not enabled, recommend `/pack install business-discovery` first; if `business-discovery` is enabled, recommend `/positioning` — Positioning needs ICP, competitive analysis, and journey evidence, so it is the natural next step.
+2. **Positioning done, UX variations missing** → check `.agents/project.json.enabled_packs` for `product-design` — if `product-design` is not enabled, recommend `/pack install product-design` first; if `product-design` is enabled, recommend `/ux-variations` — Explore experience directions before production specification.
+3. **Specific stage risk** — the overview exposed a lifecycle-stage risk that must be resolved before positioning or UX work can proceed → recommend the relevant lifecycle map (`/onboarding-map`, `/conversion-map`, `/transaction-map`, `/retention-map`, `/expansion-map`, or `/lifecycle-metrics`). Cite the risk and explain why it blocks the next AFPS step.
+4. **Never** recommend `/spec-interview` from this skill — it is many steps downstream in the AFPS chain.
+
+## Output Shape
+
+```markdown
+# Journey Map
+
+> Based on: research/icp.md[, other evidence]
+> Date: YYYY-MM-DD
+
+## Summary
+## User Journeys
+## Customer Lifecycle
+## Critical Moments
+## Stage Detail Index
+## Journey Gaps
+## Next Steps
+```
+
+## Alignment Page
+
+Follow the shared Alignment Page convention in CLAUDE.md. Output: `alignment/journey-map-{topic}.html`.
+
+## Constraints
+
+- Keep this file as the overview; put step-level stage detail in the focused lifecycle skills.
+- Ground every important step in ICP, research, specs, feedback, or codebase evidence.
+- Do not prescribe UI or architecture.
+- Present findings before writing.
+- Follow the archive-first replacement policy for canonical research/spec documents.