archflow-agent-post-launch-analyst

Analyzes product usage data and writes analytics tracking plans and optimization reports.

28|4|Updated Mar 12, 2026
One-click install
npx skills add https://github.com/AZidan/archflow --skill archflow-agent-post-launch-analyst-azidan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: archflow-agent-post-launch-analyst
Source: https://github.com/AZidan/archflow/tree/main/adapters/generic/.agents/skills/archflow-agent-post-launch-analyst
Command: npx skills add https://github.com/AZidan/archflow --skill archflow-agent-post-launch-analyst-azidan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After launch, teams struggle to turn raw usage data into concrete product decisions. This Skill acts as a post-launch analytics specialist that sets up event tracking and converts behavior data into prioritized improvement proposals. ## Core Features & Use Cases - Analytics Setup: Designs event tracking schemas, conversion funnels, cohort and retention tracking for platforms like Google Analytics, Mixpanel, or Amplitude, with GDPR-compliant implementations. - Behavior Analysis: Examines user flows, engagement metrics, feature adoption, and A/B test results with attention to statistical significance. - Actionable Deliverables: Writes docs/analytics-setup.md in Phase 5 and docs/optimization-recommendations.md in Phase 6, routing new product ideas to backlog stubs instead of editing roadmap.yaml. - Use Case: After releasing a new onboarding flow, dispatch this role to analyze drop-off points in the funnel and produce a prioritized list of UX improvements with estimated impact. ## Quick Start Ask the agent to analyze post-launch user behavior data and write an optimization recommendations report based on the project context.

Frequently Asked Questions about archflow-agent-post-launch-analyst

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up product analytics event tracking?

Define an event tracking schema capturing meaningful user interactions, then configure platforms like Google Analytics, Mixpanel, or Amplitude with conversion funnels and cohort tracking. This role writes the full tracking plan to docs/analytics-setup.md.

How to turn user behavior data into product improvements?

Analyze user flows, engagement metrics, and feature adoption to find friction points, then translate findings into prioritized proposals with estimated impact. This role writes results to docs/optimization-recommendations.md and routes new work to backlog stubs.

Which analytics platforms does this role support?

It covers Google Analytics, Mixpanel, Amplitude, and similar platforms, including attribution models, UTM strategies, and GDPR-compliant tracking implementations.

Can this role write stories directly into the product roadmap?

No. It never writes stories into roadmap.yaml, which is only an index of epic labels and the release pipeline. Findings implying new product work become backlog stubs via the archflow-feature flow or candidate goals for the next release.

What happens when project context is missing during analysis?

The role reads .archflow/project-context.md for goals and personas and cannot ask questions mid-run. Unknowns are recorded as explicit assumptions under an Open questions section in the report.