failure-navigator

Run five parallel hypothesis agents to diagnose product traction stalls and rank failure modes.

8|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/gvkhosla/founder-skills --skill failure-navigator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: failure-navigator
Source: https://github.com/gvkhosla/founder-skills/tree/main/skills/compound/failure-navigator
Command: npx skills add https://github.com/gvkhosla/founder-skills --skill failure-navigator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Failure to gain traction after multiple build cycles is often explained by one of five fundamental causes. The Failure Navigator runs five parallel hypothesis agents to test Wrong Customer, Wrong Problem, Wrong Solution, Wrong Timing, and Wrong Distribution, then ranks them by evidence and delivers a concrete 2-cycle prescription to pivot or persevere.

Core Features & Use Cases

  • Five parallel hypothesis agents investigate the five failure modes and return evidence-backed likelihoods.
  • Automatic orchestration after 3+ consecutive flat cycles, with synthesis into a ranked diagnosis and actionable next steps.
  • Produces a diagnosis.md report that guides pivot decisions and two-cycle experiments to reorient traction.

Quick Start

Trigger the failure navigator to diagnose cycle stagnation and produce a ranked diagnosis with a 2-cycle prescription.

Frequently Asked Questions about failure-navigator

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

FAQPage Schema
How do I diagnose why product growth stalls after multiple build cycles?

To diagnose growth stalls, run five parallel hypothesis agents testing Wrong Customer, Wrong Problem, Wrong Solution, Wrong Timing, and Wrong Distribution, then synthesize a ranked diagnosis with evidence-backed likelihoods and a 2-cycle prescription.

What causes a startup to lose traction and need a pivot?

Traction loss typically stems from one of five failure modes: targeting the wrong customer, solving the wrong problem, building the wrong solution, wrong timing, or wrong distribution channels. Evidence-based diagnosis ranks these causes by likelihood.

When should I trigger a product cycle stagnation diagnosis?

Trigger a stagnation diagnosis after experiencing 3+ consecutive flat product cycles, or invoke it explicitly anytime growth stalls and you need evidence-backed prescriptions to decide whether to pivot or persevere.

How do I know if my product traction is failing due to wrong distribution or wrong timing?

Parallel hypothesis agents investigate both wrong distribution and wrong timing failure modes, returning evidence-backed likelihoods that are synthesized into a ranked diagnosis to identify which factor is primarily stalling traction.

What's the best way to prescribe a startup pivot after flat growth cycles?

Generate a diagnosis.md report that synthesizes ranked failure modes into a concrete 2-cycle prescription, guiding targeted pivot experiments to reorient product traction based on evidence-backed likelihoods.

Can I automatically detect flat product cycles and diagnose the failure mode?

Yes, the failure navigator auto-triggers after 3+ consecutive flat cycles, running five parallel hypothesis agents to investigate failure modes and producing a ranked diagnosis with actionable next steps without manual invocation.