annatchijova·annatchijova/SKILLS/known-defect-disposition/SKILL.md

known-defect-disposition

Skill9 starsChanged 4 months agoLicence not identifiedView on GitHub

Severity controls response urgency; it does not authorize neglect. A P0/P1 earns immediate review — but P2/P3/P4 remain known defects requiring disposition, not a silent backlog, and before anything is deferred its severity must be re-tested under interaction, composition, adversarial control, and deployment context, because initial severity usually scores the finding in isolation while the real exposure is reachable only in combination. Use whenever a finding, bug, or audit result is being triaged by priority tier, whenever the phrase "not blocking current work" is used to justify not fixing something, and whenever time runs out before every finding is addressed. Trigger on "P2/P3/P4", "low severity, deferring", "not blocking, ship it", "we'll get to it later", "known issue, out of scope for now", or any triage pass that assigns a tier without asking whether that tier survives composition. Composes with debt-closure-discipline (the three terminal states this skill's gate feeds into) and assume-breach-modeling (the chaining method the escalation questions reuse). It does not lower your bar for what counts as P0 — it raises your bar for what you're allowed to call P3 without having checked.