kill-criteria-enforce

Project kill criteria are predefined conditions that trigger project termination to prevent premature commitments. You need them before committing time or money to a new project, ensuring founder discipline and structured project governance.

To enforce kill criteria, validate the presence of a kill-criteria.md file in your project root. If missing, an interactive prompt asks four essential questions to help draft and save the kill-criteria document before proceeding.

Defining project kill criteria requires answering four essential questions interactively. These questions establish commitment control boundaries, forming a reusable template that saves directly to the project folder as kill-criteria.md.

Yes, a kill-criteria.md file is required in the project root folder. This governance tool validates its presence before any commitment action, generating one through four interactive prompts if the file is missing.

The best way to maintain startup governance discipline is by enforcing kill criteria rules across any project folder. This process validates required documentation, creating an audit trail for reviews and accountability before resource commitment.

Yes, you can validate existing commitment rules by checking for the kill-criteria.md file in the project root. If present, the enforcement process recognizes it, skipping the interactive questions and preserving your current governance setup.