skillpacks 0.1.1 → 0.1.2

package/packs/business-ops/claude/burn-rate/archive/v0.4/SKILL.md

@@ -0,0 +1,341 @@
+---
+name: burn-rate
+description: Estimate monthly burn rate from infrastructure signals and calculate payback period against revenue projections
+type: analysis
+version: v0.4
+argument-hint: "[optional: focus area e.g. \"infrastructure only\", \"team costs\", \"runway\"]"
+interview_depth: light
+visual_tier: visual
+---
+
+# Burn Rate — Infrastructure-Grounded Cost & Runway Analysis
+
+Analyzes a project's infrastructure, third-party services, and team costs to estimate monthly burn rate, then calculates payback period and break-even against revenue projections. Bridges the gap between `/monetization` (abstract unit economics) and `/scale-audit` (infrastructure readiness) with concrete, dollar-denominated cost projections.
+
+## Prerequisites
+
+- **Hard**: None — can run on any codebase.
+- **Soft**: Read these if they exist — each adds revenue/cost context:
+  - `research/monetization.md` (or `research/{slug}/monetization.md`) — pricing tiers, unit economics, revenue model
+  - `research/metrics.md` (or `research/{slug}/metrics.md`) — business metrics, customer counts
+  - `research/gtm.md` (or `research/{slug}/gtm.md`) — revenue projections, channel costs
+  - `research/icp.md` (or `research/{slug}/icp.md`) — market context, buyer budget
+  - `CLAUDE.md`, `README` — product context
+
+## Process
+
+### 0. Product-Path Scope Resolution
+
+Resolve research scope by product path before using code or app structure as a hint:
+
+1. If `$ARGUMENTS` names a non-archived `research/{slug}/` directory or a product-path ID whose `scope_path` points there, use that path. Treat `{slug}` as the product/app name, not the ICP, audience, or segment label.
+2. If `$ARGUMENTS` names only `research/_archive/{slug}/` or a manifest entry with `status: archived` or legacy `status: abandoned`, stop and warn that the path is archived; do not write or update scoped outputs there.
+3. Read `research/.progress.yaml` when present. Normalize legacy `active_path` to `active_paths` on read and write back `active_paths` on manifest updates. Treat legacy `abandoned` as `archived`; exclude `archived`, `abandoned`, `deferred`, `revisit_candidate`, `promoted`, and any `scope_path` under `research/_archive/` from active target selection.
+4. If active product paths exist in the manifest, use those paths. If multiple active paths exist, ask which one to target unless this skill explicitly supports cross-path output.
+5. If no active manifest target exists, list non-archived product directories under `research/`, excluding `research/_archive/` and dot directories. Auto-select only when exactly one exists; ask when multiple exist.
+6. If no product directories exist, use flat `research/` single-product mode.
+7. Detect monorepo/app/package structure only as a secondary hint. Suggest creating a missing `research/{slug}/` product path when code clearly exposes an app, but do not require code or monorepo detection before using `research/{slug}/`.
+
+When product path `{slug}` is active, read and write research under `research/{slug}/`, specs under `specs/{slug}/`, and treat top-level `research/*.md` files as flat-mode documents or cross-path summaries.
+
+### 1. Load Context
+
+a) Read infrastructure files — check for existence of each and read those found:
+   - **Container/orchestration**: `Dockerfile`, `docker-compose.yml`, `docker-compose.*.yml`
+   - **IaC**: `terraform/`, `pulumi/`, `cdk/`, `cloudformation/`
+   - **Kubernetes**: `k8s/`, `kubernetes/`, `*.yaml` in deploy directories, Helm charts
+   - **CI/CD**: `.github/workflows/`, `.circleci/`, `.gitlab-ci.yml`, `Jenkinsfile`
+   - **Serverless**: `serverless.yml`, `serverless.ts`, `sam-template.yaml`
+   - **PaaS**: `fly.toml`, `render.yaml`, `vercel.json`, `netlify.toml`, `railway.json`, `Procfile`, `app.yaml`, `heroku.yml`
+   - **Cloud config**: AWS (`samconfig.toml`, `cdk.json`), GCP (`app.yaml`, `.gcloudignore`), Azure (`azure-pipelines.yml`, `host.json`)
+
+b) Read dependency files for third-party service SDKs:
+   - `package.json`, `yarn.lock`, `pnpm-lock.yaml`
+   - `requirements.txt`, `Pipfile`, `pyproject.toml`
+   - `Cargo.toml`, `go.mod`, `Gemfile`, `build.gradle`, `pom.xml`
+   - Look for: Stripe, Twilio, SendGrid, Resend, AWS SDK, GCP SDK, Azure SDK, OpenAI, Anthropic, Auth0, Clerk, Datadog, Sentry, New Relic, Algolia, Typesense, Supabase, PlanetScale, Neon, etc.
+
+c) Read environment templates for service API keys:
+   - `.env.example`, `.env.template`, `.env.sample`, `.env.development`
+   - Look for: API keys, service URLs, database connection strings that imply paid services
+
+d) Read existing research documents (soft prerequisites listed above) — extract:
+   - Revenue projections, pricing tiers, MRR/ARR estimates
+   - Unit economics (CAC, LTV, margins)
+   - Customer counts or projections
+   - Business metrics
+
+e) Read `CLAUDE.md` and `README` for product context.
+
+### 2. Infrastructure Cost Detection
+
+Scan codebase and build a cost inventory across these categories:
+
+| Category | What to detect |
+|----------|---------------|
+| **Compute** | Cloud provider configs (AWS/GCP/Azure), container orchestration (ECS, k8s, Cloud Run), serverless (Lambda, Cloud Functions), PaaS (Heroku, Fly, Railway, Render, Vercel, Netlify) |
+| **Database** | Database connection strings/configs — Postgres, MySQL, MongoDB, Redis, DynamoDB, Firestore, Supabase, PlanetScale, Neon, CockroachDB |
+| **Storage** | S3/GCS/Azure Blob configs, CDN configs (CloudFront, Cloudflare), file upload services |
+| **Third-party services** | SDK imports and API key references — email (SendGrid, SES, Resend, Postmark), payments (Stripe), auth (Auth0, Clerk, Supabase Auth), monitoring (Datadog, Sentry, New Relic, Grafana Cloud), search (Algolia, Typesense, Meilisearch), AI/ML (OpenAI, Anthropic, Replicate, Hugging Face) |
+| **CI/CD** | GitHub Actions minutes, CircleCI, GitLab CI — from workflow configs |
+| **DNS/Domain** | Domain configs if detectable (Cloudflare, Route53) |
+
+For each detected service:
+a) Use WebSearch (at least 4-6 queries) to find current pricing for the detected services. Prioritize the most expensive categories.
+b) Estimate monthly cost using reasonable defaults for a startup-stage project.
+c) Note all assumptions (instance size, tier, usage level).
+d) Assign confidence: **High** (pricing page with clear tiers), **Medium** (usage-dependent, estimated from codebase signals), **Low** (detected but usage unknown).
+
+### 3. Interview — Fill Cost Gaps
+
+Use AskUserQuestion (2-3 focused questions):
+
+a) Present detected infrastructure with estimated costs in a table. Ask:
+   - "Here's what I found in the codebase. Are these estimates roughly right? Any services I missed or got wrong?"
+
+b) Ask about team and operational costs:
+   - "What's your team size and approximate fully-loaded cost per person per month? (Or total monthly team cost if easier)"
+   - "Any major non-infra costs I can't see in code? (marketing spend, tools/subscriptions, office, legal, etc.)"
+
+c) If revenue data wasn't found in research docs, ask:
+   - "What's your current or projected monthly revenue? (MRR if live, projected if pre-revenue)"
+
+### 4. Revenue Projections
+
+a) Load revenue data from existing research docs:
+   - `monetization.md` — pricing tiers, revenue model
+   - `gtm.md` — revenue projections, traction targets
+   - `metrics.md` — business metrics, customer counts
+
+b) Present what was found as defaults. Use AskUserQuestion:
+   - "I found these revenue figures in your research docs: [summary]. Are these current? Please confirm or override with actual numbers."
+   - Ask for: current MRR/ARR (or projected if pre-revenue), monthly growth rate assumption, customer count (current or projected)
+   - Ask for cash on hand (for runway calculation) — this is optional
+
+### 5. Calculate & Present
+
+Compute the following (with all assumptions visible):
+
+a) **Monthly Burn Rate** = infrastructure + team + other costs
+   - Break down by category with percentages
+
+b) **Runway** = cash on hand / monthly burn rate
+   - Only if cash position was provided
+   - Show in months
+
+c) **Payback Period** = total investment to date / monthly net revenue
+   - Net revenue = gross revenue - infrastructure costs
+   - If pre-revenue, note as "N/A — pre-revenue"
+
+d) **Break-even Point** = month when cumulative revenue exceeds cumulative costs
+   - Model three scenarios: conservative (50% of base growth), base, optimistic (150% of base growth)
+   - If pre-revenue with no projections, skip
+
+e) **Cost per Customer** = infrastructure costs / customer count
+   - Only if customer count is known or estimable
+
+f) **Cost Optimization Opportunities** — identify quick wins:
+   - Over-provisioned resources
+   - Services with cheaper alternatives
+   - Free tier headroom not being used
+   - Reserved instance / committed use discounts
+
+Present the full analysis to the user. Use AskUserQuestion:
+- "Here's the complete burn rate analysis. Ready to write to `research/burn-rate.md`? Anything to adjust?"
+
+### 6. Downstream Impact Check
+
+After writing, check for downstream research documents that may be affected. Only check documents that exist on disk.
+
+**Downstream documents to check** (use `{slug}/` prefix when product-path scope is active):
+- `research/monetization.md`
+
+For each existing downstream document:
+1. Read it — focus on `> Based on:` header, `## Summary`, and sections that reference cost assumptions, unit economics, or margins
+2. Identify **specific conflicts**: claims, assumptions, or references that contradict the burn rate analysis. Examples:
+   - Gross margin estimates that don't account for actual infrastructure costs
+   - Unit economics assumptions that use different cost figures
+   - Payback period estimates that diverge from the infrastructure-grounded calculation
+3. Note each conflict: downstream file, section, the stale claim (quote it), and what it should now say
+
+**Classify the impact**:
+- **None**: No downstream documents exist, or no conflicts found. Skip display entirely.
+- **Minor** (1-2 small conflicts): Display conflicts to user inline.
+- **Major** (3+ conflicts OR a foundational assumption changed — e.g., burn rate is 2x+ what monetization assumed): Display conflicts and strongly recommend `/reconcile-research`.
+
+### 7. Populate Next Steps
+
+Check which files exist to populate the `## Next Steps` section contextually. Include 3-5 applicable items with "Pick one:" framing:
+
+**Impact-aware adjustments:**
+- IF downstream impact is **Major**: prepend `/reconcile-research — [N] conflicts found in downstream docs` as the first item
+- IF downstream impact is **Minor**: annotate relevant skill suggestions with "(stale — [brief description])"
+- If downstream impact has not been classified yet, run the downstream impact check against the proposed output before selecting the final recommendation. Do not emit a Minor/Major impact recommendation speculatively.
+
+Conditional items:
+- IF no `research/monetization.md`: check `.agents/project.json.enabled_packs` for `business-growth` — if `business-growth` is not enabled, recommend `/pack install business-growth` inside Claude Code, or `npx skillpacks install business-growth` from the project shell, first; if `business-growth` is enabled, recommend `/monetization` — Build pricing strategy informed by actual infrastructure costs
+- IF `research/monetization.md` exists but unit economics differ: check `.agents/project.json.enabled_packs` for `business-growth` — if `business-growth` is not enabled, recommend `/pack install business-growth` inside Claude Code, or `npx skillpacks install business-growth` from the project shell, first; if `business-growth` is enabled, recommend `/monetization` — Update unit economics with infrastructure-grounded costs
+- IF no `research/gtm.md`: check `.agents/project.json.enabled_packs` for `business-growth` — if `business-growth` is not enabled, recommend `/pack install business-growth` inside Claude Code, or `npx skillpacks install business-growth` from the project shell, first; if `business-growth` is enabled, recommend `/gtm` — Build go-to-market plan with cost-aware pricing
+- IF no `research/metrics.md`: check `.agents/project.json.enabled_packs` for `business-growth` — if `business-growth` is not enabled, recommend `/pack install business-growth` inside Claude Code, or `npx skillpacks install business-growth` from the project shell, first; if `business-growth` is enabled, recommend `/metrics` — Define metrics to track burn rate health (cost per customer, infrastructure efficiency)
+- IF no `research/scale-audit.md` and infrastructure is complex: `/scale-audit` — Evaluate infrastructure readiness before scaling costs
+- IF codebase exists and optimization opportunities found: check `.agents/project.json.enabled_packs` for `product-design` — if `product-design` is not enabled, recommend `/pack install product-design` inside Claude Code, or `npx skillpacks install product-design` from the project shell, first; if `product-design` is enabled, recommend `/brainstorm` — Explore cost optimization as a feature priority
+
+### 8. Write Output
+
+Only after the user has validated the findings, write the output file.
+
+## Output
+
+### `research/burn-rate.md` (or `research/{slug}/burn-rate.md`)
+
+```markdown
+# Burn Rate Analysis
+
+> Based on: codebase infrastructure analysis[, research/monetization.md, research/metrics.md, research/gtm.md]
+> Date: [current date]
+
+## Summary
+[2-3 sentences: total monthly burn rate, largest cost drivers, and runway/payback headline]
+
+## Infrastructure Cost Breakdown
+
+| Service | Category | Monthly Estimate | Assumption | Confidence |
+|---------|----------|-----------------|------------|------------|
+| [e.g. AWS EC2] | Compute | $X | [e.g. t3.medium, on-demand] | High/Medium/Low |
+| [e.g. Supabase] | Database | $X | [e.g. Pro plan] | High/Medium/Low |
+| ... | ... | ... | ... | ... |
+| **Infrastructure Total** | | **$X** | | |
+
+## Team & Operational Costs
+
+| Category | Monthly Cost | Notes |
+|----------|-------------|-------|
+| Team (N people) | $X | [fully-loaded cost per person] |
+| Marketing | $X | [if provided] |
+| Tools & Subscriptions | $X | [if provided] |
+| Other | $X | [if provided] |
+| **Operational Total** | | **$X** |
+
+## Total Monthly Burn Rate
+
+| Category | Monthly Cost | % of Total |
+|----------|-------------|-----------|
+| Infrastructure | $X | X% |
+| Team | $X | X% |
+| Other Operational | $X | X% |
+| **Total** | **$X** | **100%** |
+
+## Revenue Projections
+
+| Metric | Value | Source |
+|--------|-------|--------|
+| Current MRR | $X | [user-provided / monetization.md] |
+| Growth Rate | X%/mo | [assumption] |
+| Customer Count | N | [user-provided / metrics.md] |
+| Projected MRR (6 mo) | $X | [calculated] |
+| Projected MRR (12 mo) | $X | [calculated] |
+
+## Payback Period Analysis
+
+| Scenario | Monthly Growth | Break-even Month | Payback Period |
+|----------|---------------|-----------------|----------------|
+| Conservative | X%/mo | Month N | N months |
+| Base | X%/mo | Month N | N months |
+| Optimistic | X%/mo | Month N | N months |
+
+### Assumptions
+[List key assumptions behind each scenario]
+
+## Runway
+
+| Metric | Value |
+|--------|-------|
+| Cash on Hand | $X |
+| Monthly Burn | $X |
+| Runway | N months |
+| Runway at 50% Burn | N months |
+
+[Omit this section if cash position was not provided]
+
+## Cost per Customer
+
+| Metric | Value |
+|--------|-------|
+| Infrastructure Cost / Customer | $X |
+| Total Cost / Customer | $X |
+| Revenue / Customer (ARPU) | $X |
+| Gross Margin per Customer | X% |
+
+[Omit this section if customer count is unknown]
+
+## Cost Optimization Opportunities
+
+1. **[Opportunity]** — [description, estimated savings]
+2. **[Opportunity]** — [description, estimated savings]
+3. ...
+
+## Assumptions & Data Gaps
+[List all assumptions made, data that would improve accuracy, and recommended next steps for better estimates]
+
+<!-- Only include this section when downstream impact is Minor or Major. Omit entirely for None. -->
+## Downstream Impact
+
+> Checked: [list of downstream docs checked]
+> Impact: Minor | Major
+
+### Conflicts Found
+
+1. **research/[file].md** — [Section Name]
+   - **Stale**: "[exact quote from downstream doc]"
+   - **Now**: [what this skill's output says instead]
+
+[For Major only:]
+> **Recommended action**: Run `/reconcile-research` to audit and fix all affected downstream documents.
+
+## Next Steps
+
+Pick one:
+- [conditional items from step 7 — only include items whose conditions are met]
+```
+
+### `research/burn-rate-interview.md` (or `research/{slug}/burn-rate-interview.md`)
+Raw interview log — questions asked, infrastructure detected, user responses, cost validations, and a closing summary of key figures and assumptions.
+
+Create the `research/` (or `research/{slug}/`) directory if it doesn't exist.
+
+## Task Classification
+
+When this skill produces follow-up work, file it by execution semantics:
+
+- Immediately actionable implementation or documentation work goes in `tasks/todo.md`.
+- Human-only external actions tied to automated steps go in `tasks/manual-todo.md` with `_(blocks: Step N.X)_` or `_(after: Step N.X)_`; repo edits, SDK wiring, generated assets, local commands, tests, audits, and authenticated CLI/API work stay in `tasks/todo.md`.
+- One-time condition-gated records, baselines, or future measurements go in `tasks/record-todo.md` with source, condition, non-blocking reason, evidence, and promotion rule.
+- Cadence-based reviews, playtests, adoption checks, investor updates, retros, or docs-health checks go in `tasks/recurring-todo.md` with cadence, owner/agent, next due, evidence path, and escalation conditions.
+- Do not put non-blocking records or recurring obligations in `tasks/todo.md` unless they have been explicitly promoted into current execution work.
+
+## Constraints
+
+- **Evidence-based costs.** Every cost estimate must trace to a detected service in the codebase or a user-provided figure. Do not invent costs.
+- **Present before writing.** Never write output files until the full analysis has been presented and validated by the user.
+- **State assumptions.** Every cost estimate must include the assumption behind it (tier, instance size, usage level) and a confidence level. Never present estimates as facts.
+- **Don't prescribe architecture changes.** If infrastructure is over-provisioned or poorly structured, note it as a cost optimization opportunity — architecture decisions belong in `/scale-audit` or `/brainstorm`.
+- **Don't duplicate monetization.** If `research/monetization.md` already has unit economics, compare and reconcile rather than contradict. Note any differences and ask the user to resolve.
+- **Do not overwrite existing `research/burn-rate.md`** (or `research/{slug}/burn-rate.md`) without asking the user first.
+- **Minimum research depth**: at least 4 WebSearch queries for pricing data before presenting cost estimates.
+- **Use current pricing.** Always search for current pricing — cached or memorized pricing may be outdated.
+
+## Context Gathering
+
+**Step 1 — Scope questions.** Before researching, ask the user 1–3 questions via `AskUserQuestion` to understand: their product/service, target audience, and what they hope to learn or decide from this research.
+
+**Step 2 — Research.** Conduct research scoped by the user's answers.
+
+**Step 3 — Findings validation.** Before building the alignment page, present the 3–5 most important findings and ask the user to validate or correct any critical assumptions.
+
+## 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/burn-rate-{topic}.html`.
+
+## Default Shipping Contract
+
+Follow the shared shipping contract convention in CLAUDE.md.

package/packs/business-ops/claude/cohort-review/ALIGNMENT-PAGE.md

@@ -9,6 +9,8 @@ When this skill produces durable deliverables (research, specs, plans, reports,
 
 The tier is set per skill via `visual_tier` in SKILL.md frontmatter (or detected by the upgrade script). The bundled ALIGNMENT-PAGE.md receives tier-appropriate rendering guidance from the generator.
 
+**Context intake.** This skill declares `context_intake: artifact_only` (Artifact-driven). Work from concrete artifacts, data, logs, or existing instructions by default; ask concise clarification questions only when the available artifacts are missing, contradictory, or unsafe to interpret.
+
 **Alignment lifecycle.** Alignment pages have three lifecycle states. `review` is the draft/pre-approval page: it contains the complete deliverable preview, evidence, required inline gate questions, section feedback controls, local section-feedback YAML only after a section feedback choice is selected, and one bottom `Compile Responses` control. `confirmed` is the post-approval page after the agent has consumed final compiled response YAML, made any approved user-requested edits, and written or updated the approved canonical artifacts. A confirmed page is finished and current for the completed alignment cycle, but it remains amendable when later research changes or extends the conclusions. `amended` is a future revision of a confirmed page: archive the previous confirmed page first, mark what changed, preserve the prior approval record, and highlight the new evidence, decisions, or scope that changed the earlier conclusion.
 
 **Central alignment index.** When a research-producing skill writes or updates an HTML alignment page, also maintain the repository's central alignment index. Look for `alignment/index.html` at the repository root; if the target repo documents a different central alignment-index path, use that path and report it. If the index does not exist, create it as a self-contained HTML page that works from `file://`, links to every active `alignment/*.html` page except itself, and includes the newly written page. Every index entry must include the page's alignment date in a muted meta span after the link, formatted `YYYY-MM-DD`, for example `<a href="page.html">Title</a> <span class="meta">2026-06-09</span>`. The alignment date is the review or confirmed date written inside the page itself; new pages use today's date. If the index exists, update it instead of blindly appending: preserve valid existing entries, metadata, and entry dates; remove duplicate entries for the same page path; keep links repo-relative; and include the new or updated page. When updating an existing index, add a date only to entries that are missing one, deriving it from the page's internal alignment date, or from file history when the page has no internal date. If a `new` marker is used, combine it with the date as `<span class="meta">new · YYYY-MM-DD</span>`, and remove stale `new` markers from entries that are no longer the latest addition.
@@ -57,7 +59,9 @@ The tier is set per skill via `visual_tier` in SKILL.md frontmatter (or detected
 
 **Report-only research gates.** For report-only or pre-approval research skills, the first `review` alignment page must explicitly contain proposed research scope, source plan, assumptions/confidence, recommended output path, proposed file changes, and approval gates before synthesized research begins and before any working packet, canonical research, spec, or task file is created or updated.
 
-**Staged research workflow.** Heavy report-first research uses a scope-first three-stage approval workflow. Stage 1 is minimal scope discovery only: inspect enough repository, user, and source context to propose research scope, source plan, assumptions, output paths, and approval questions. Build the `review` alignment page before synthesized research. The page must render the proposed scope, available source categories, known context, assumptions/confidence, proposed working-packet and canonical output paths, and research-scope approval gates. Stop for final compiled response YAML approval of the research scope. Do not synthesize findings, rank candidates, recommend a path, or create working packets, canonical research, spec, or task files in Stage 1. Stage 2 starts only after final compiled response YAML approves the research scope with no unresolved `needs-clarification`, unresolved `down` feedback, or other unresolved negative feedback. Perform the synthesized research, run required source/code checks, and write only a non-canonical working packet. Flat mode uses `research/_working/preliminary-cohort-review-research.md`; product-path mode uses `research/{slug}/_working/preliminary-cohort-review-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-cohort-review-research.md`; product-path mode uses `research/{slug}/_working/preliminary-cohort-review-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.
 
 **Risk-validation gates.** Render assumption/risk evidence coverage, confidence, candidate verdicts or mitigations, output-location/change-scope decisions, coverage checkpoint, and post-approval route as gates. Durable tracker outputs remain canonical markdown artifacts and must also be fully rendered in the alignment page. 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.
 

package/packs/business-ops/claude/cohort-review/CHANGELOG.md

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

package/packs/business-ops/claude/cohort-review/SKILL.md

@@ -2,15 +2,15 @@
 name: cohort-review
 description: Post-launch metrics & funnel analysis — cohort retention, channel performance, and progress against targets from /metrics
 type: analysis
-version: v0.3
+version: v0.4
 argument-hint: "[file path to data, pasted data, or empty to be prompted]"
-interview_depth: none
+context_intake: artifact_only
 visual_tier: visual
 ---
 
 ## Pack Availability Guard
 
-When recommending a skill from another pack, verify the target pack is installed via `.agents/project.json` `enabled_packs`. If it is not enabled, recommend `/pack install <pack>` inside Claude Code, or `npx skillpacks install <pack>` from the project shell. After install, tell Claude users to run `/reload-skills`, then `/clear` or restart if the skill remains invisible. Global skills are always valid. Skills from this same pack are valid because the current skill is already running from that pack.
+When recommending a skill from another pack, verify the target pack is installed via `.agents/project.json` `enabled_packs`. If it is not enabled, recommend `npx skillpacks install <pack>` from the project shell. After install, tell Claude users to run `/reload-skills`, then `/clear` or restart if the skill remains invisible. Global skills are always valid. Skills from this same pack are valid because the current skill is already running from that pack.
 
 # Cohort Review — Post-Launch Metrics & Funnel Analysis