evidence-based-planning

What problem does it solve?

This Skill enforces a rigorous, evidence-first approach to creating implementation plans, preventing common errors like incorrect line numbers, invalid data assumptions, and designs referencing non-existent code.

Core Features & Use Cases

• Mandatory Evidence Collection: Requires code and runtime verification before defining problems.
• Historical Analysis: Integrates git log to learn from past failures.
• Assumption Verification (CoVe): Uses a structured Chain-of-Verification process to validate every assumption before coding.
• Pre-Mortem Analysis: Proactively identifies potential failure modes.
• Strict Citation Audit: Ensures all plan elements are tied to verified evidence.
• Use Case: When tasked with refactoring a critical service, this Skill ensures that every proposed code change is directly linked to verified evidence of the problem it solves and that all assumptions about the existing code and data are validated, minimizing the risk of introducing new bugs.

Quick Start

Use the evidence-based-planning skill to create an implementation plan for fixing the 'Pipeline zero-validation' problem, starting with evidence collection.