launch-governance

Kill gates use pre-committed criteria defined in a YAML file to monitor ongoing project viability. The skill evaluates these thresholds during reviews to determine whether a project should continue or be terminated.

Launch governance manages initial launch plans using specific gate criteria to evaluate readiness. Decision logging tracks rationales behind these evaluations to prevent redundant discussions and maintain project tracking continuity.

Monthly portfolio reviews provide a structured evaluation of ongoing projects and investments against defined criteria. The skill generates these reviews to ensure alignment with business strategies and gate requirements.

Yes, managing launch governance requires YAML file management for defining kill gate criteria and utilizes Obsidian markdown files for memory storage. These formats handle configuration and long-term decision tracking respectively.

Yes, tracking decisions without redundant discussions is achieved through decision logging stored in Obsidian markdown files. This provides a persistent record of decision rationales for ongoing project review and accountability.

Using YAML files for kill gate criteria requires manual configuration and strict syntax management to function correctly. The skill depends on predefined YAML structures and cannot dynamically generate kill criteria autonomously.