founder-check

To get a single audit verdict for your startup idea, invoke the founder-check orchestrator with a direct command. It coordinates failure-pattern, kill-criteria, and business-fit assessments to synthesize a final GO, REFRAME, PAUSE, or KILL decision.

A GO, REFRAME, PAUSE, or KILL verdict represents the synthesized output of a business risk audit, indicating whether to proceed, pivot, delay, or abandon your startup idea. It clarifies next steps and highlights the hardest-to-hear finding to reduce decision risk.

You should run a founder discipline audit during commitment, exploration, or gut-check scenarios when evaluating a business plan. It explicitly requires a direct user command to trigger, ensuring the assessment does not fire automatically during general planning discussions.

The startup idea evaluation process works by loading relevant inputs and executing three sub-skills: failure-pattern-guard, kill-criteria-enforce, and business-fit-score. It then synthesizes their independent outputs into a single, actionable verdict.

No, the founder audit does not run automatically when you describe your business plan. It triggers only on explicit user commands to ensure it does not fire during standard commitment or exploration language, requiring a direct request to evaluate an idea.

Yes, you can use a single-verdict audit to reduce startup decision risk. By coordinating multiple failure-pattern and business-fit assessments into one GO, REFRAME, PAUSE, or KILL verdict, it clarifies next steps and highlights critical findings.