dhanoopbhaskar/sdlc
Core SDLC skills: planning, root-cause investigation, completion verification, merge-gate review, and behavioral guardrails.
Finds a proven root cause before fixing a failing test, stack trace, or wrong output, then proves the fix. Use for debugging.
Reviews a change before merge and returns an evidence-backed verdict. Use when asked to review a diff, check whether work is done, decide if a branch is merge-ready, or verify a change before merging. Runs a scope pass, a proof pass, three attack lenses (side effects, security, blast radius), and a computed verdict. Never claims MERGE-READY without executed proof, and never executes without a sandbox or tree-bound approval.
Plans a change before code: falsifiable acceptance criteria, risk register, review tier, project profile, and an exhaustive T3 analysis. Use to spec or break down work.
Behavioral guardrails for SDLC planning, implementation, and review. Use when shaping plans, implementing approved scope, or reviewing changes to surface assumptions, keep solutions simple, enforce surgical diffs, and require verifiable checks.
Requires explicit proof before declaring a task done: requirement, test, regression, diff justification, and unproven gaps.