systemic-product-analyst

Audits products across build quality and market fit to generate 30/60/90 day action plans.

Updated May 16, 2026
One-click install
npx skills add https://github.com/organvm-i-theoria/_agent-ontology --skill systemic-product-analyst-organvm-i-theoria
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systemic-product-analyst
Source: https://github.com/organvm-i-theoria/_agent-ontology/tree/main/.agents/skills/systemic-product-analyst
Command: npx skills add https://github.com/organvm-i-theoria/_agent-ontology --skill systemic-product-analyst-organvm-i-theoria

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Product teams often rely on intuition rather than evidence when deciding what to build next, leading to mismatches between product quality and market positioning. This Skill provides a rigorous audit protocol that diagnoses whether a product is a "best kept secret" (strong build, weak distribution) or "vaporware" (strong claims, weak product), then produces a concrete action plan. ## Core Features & Use Cases - Two-Lane Scorecard: Evaluates Lane A (build truth: reliability, time-to-value, architecture, defensibility) against Lane B (world interface: positioning, trust, discovery, monetization) with evidence-based scoring. - Mismatch Diagnosis & Friction Mapping: Identifies accidental friction (bad design), deceptive friction (broken promises), and claim-versus-proof gaps that erode user trust. - Structured Artifacts: Generates ready-to-use markdown deliverables including a snapshot, scorecard, risk register, and 30/60/90 day plan. - Use Case: A founder preparing for a funding milestone runs the audit to discover their product works well but has unverified marketing claims, then receives a 90-day plan focused on proof-building and distribution rather than new features. ## Quick Start Ask the assistant to run a systemic product audit on your project, starting with your North Star metric and primary user.

Frequently Asked Questions about systemic-product-analyst

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

FAQPage Schema
How do I audit a product's market fit systematically?▼

Run the two-lane diagnostic: score Lane A (outcome reliability, time-to-value, architecture, defensibility) and Lane B (positioning, trust, discovery, monetization) from 1-5 each with evidence. The gap between lanes determines whether to focus on distribution or product reliability.

What is the difference between Lane A and Lane B analysis?▼

Lane A measures build truth: whether the product works, how fast it delivers value, and how maintainable it is. Lane B measures world interface: positioning clarity, claim verification, discovery channels, and the value-to-cash path.

How do I verify product claims before launch?▼

Use the Claim Stack method: list your top 3 claims, then demand proof for each in the form of a demo, data, or testimonial. Mark each claim as verified, partial, or unverified, and fix unverified claims before scaling distribution.

When should I stop adding features to my product?▼

Stop adding features when the mismatch between build quality and market presence is high. If Lane A exceeds Lane B, focus on distribution and narrative; if Lane B exceeds Lane A, focus on product reliability instead.

What artifacts does a product audit produce?▼

The audit generates four markdown artifacts: a snapshot of current state, a Lane A versus Lane B scorecard, a risk register of existential threats, and a 30/60/90 day action plan limited to one build change and one interface change per sprint.