a-organvm/systemic-product-analyst
distributions/codex/skills/systemic-product-analyst/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add a-organvm/a-i--skills systemic-product-analystInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 27, 2026, 6:15 AM17.7s3 files scanned
SKILL.md
- name:
- systemic-product-analyst
- description:
- 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.
- license:
- MIT
- governance_phases:
- [frame]
- organ_affinity:
- [meta, organ-iii]
- triggers:
- [user-asks-about-product-analysis, user-asks-about-market-fit, context:strategic-analysis]
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
-
Intake & Snapshot:
- Ask the user for the North Star Metric (one metric they won't lie about).
- Identify the Primary User and Primary Context.
-
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?
-
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).
-
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)
Related Skills
a-organvm/movement-notation-systems
testing
VerifiedTrustedCommunity
Designs systems for encoding, scoring, and generating choreographic movement using Laban notation, computational geometry, and procedural animation principles.
8SKILL.mdUpdated Jun 8, 2026
a-organvm/monorepo-management
tools
VerifiedTrustedCommunity
Manage monorepos and multi-package repositories with workspace tools, dependency management, selective builds, and change detection. Covers npm/pnpm workspaces, Turborepo, and Python monorepo patterns. Triggers on monorepo setup, workspace management, or multi-package repository requests.
8SKILL.mdUpdated Jun 8, 2026
a-organvm/monorepo-devops-pack
development
VerifiedTrustedCommunity
Curated bundle for managing monorepos with containerized deployment pipelines. Includes monorepo management, Docker containerization, CI/CD deployment, and coding standards. Use when setting up or improving multi-package repository infrastructure.
8SKILL.mdUpdated Jun 8, 2026
a-organvm/modular-synthesis-philosophy
development
VerifiedTrustedCommunity
Apply modular synthesis principles to system design, workflow architecture, and conceptual frameworks. Use when designing modular systems, creating architecture diagrams using synthesis metaphors, applying signal flow thinking to data pipelines, or translating between audio engineering and software concepts. Triggers on modular architecture design, signal flow diagrams, synthesis-inspired system thinking, or "oscillator/patch" metaphors.
8SKILL.mdUpdated Jun 8, 2026