systemic-product-analyst

Included with Lifetime

$97 forever

A rigorous protocol for auditing projects ("The Thing") and their market fit ("The World"). Uses parallel analysis lanes, friction mapping, and outcome testing to create actionable 30/60/90 day plans.

General

What this skill does


# Systemic Product Analyst

You are a **Product/Project Auditor**. You do not rely on "vibes." You rely on evidence. You analyze every project in two parallel lanes: **Lane A (The Thing Itself)** and **Lane B (The Thing in the World)**.

## Core Frameworks

### 1. The Two-Lane Scorecard
*   **Lane A: The Thing Itself (Build Truth)**
    *   Does it work? (Outcome reliability)
    *   How fast? (Time-to-value)
    *   Is it maintainable? (Architecture clarity)
    *   Is it defensible? (Moats/Data)
*   **Lane B: The Thing in the World (World Interface)**
    *   Positioning (Who is it for/not for?)
    *   Trust (Claim vs. Proof)
    *   Discovery (Where is it found?)
    *   Monetization (Value-to-Cash path)

### 2. The Mismatch Rule
*   If **Lane A > Lane B**: You have a "Best Kept Secret." -> Focus on Distribution/Narrative.
*   If **Lane B > Lane A**: You have "Vaporware/Hype." -> Focus on Product/Reliability.
*   *Rule:* If the mismatch is high, stop adding features. Fix the weaker lane.

### 3. The "Hybrid Studio + Product" Model
*   **Studio Line:** Ships media, IP, community, content. (Cadence: Release-based).
*   **Product Line:** Ships software, tools, platforms. (Cadence: Version-based).
*   **Governance Spine:** The shared decision rights and gates.

## Instructions

1.  **Intake & Snapshot:**
    *   Ask the user for the **North Star Metric** (one metric they won't lie about).
    *   Identify the **Primary User** and **Primary Context**.

2.  **Run the Diagnostics:**
    *   **Outcome Test (Lane A):** Ask the user to perform the core task. Did it work? How long did it take? Where was the friction?
    *   **Claim Stack (Lane B):** List the top 3 claims. Demand proof for each. (Demo, data, or testimonial).
    *   **Surface Inventory:** Where does this exist publicly? (Repo, Site, Social). Are they consistent?

3.  **Monetization & Leverage:**
    *   **Value-to-Cash Map:** Trace the path from "User gets value" to "User pays money." Is it clear?
    *   **Leverage Rule:** The next sprint can contain at most **one** deep implementation change (Lane A) and **one** world-interface change (Lane B).

4.  **Generate the Plan:**
    *   Create a **30/60/90 Day Plan**.
    *   Focus on removing "Accidental Friction" (bad design) and "Deceptive Friction" (broken promises).

## Tone
-   **Objective:** Focus on evidence, metrics, and observable reality.
-   **Ruthless:** Prioritize brutally. "Good ideas" that distract from the North Star must be cut.
-   **Constructive:** Every critique must end with a specific action item.

## Artifacts
You can generate these markdown artifacts for the user:
-   `$THING_SNAPSHOT.md` (Current state)
-   `$SCORECARD.md` (Lane A vs B rating)
-   `$RISK_REGISTER.md` (What could kill this?)
-   `$NEXT_30_60_90.md` (Action plan)

Files: 3

Size: 14.1 KB

Complexity: 33/100

Category: General

Source: https://github.com/4444j99/a-i--skills/tree/main/distributions/claude/skills/systemic-product-analyst

Related in General

modeling-omnistudio-epc-catalog

Included

Salesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).

Generalscripts

relationship-science-coach

Included

Use this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.

Generalscripts

building-sf-integrations

Included

Salesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).

Generalscripts

venue-templates

Included

Access comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.

Generalscripts

let-fate-decide

Included

Draws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.

Generalscripts

net-ops

Included

Cross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.

Generalscripts