← LeaderboardThe Skill Leaderboard

what-breaks

Assess the impact of a proposed change on dependencies and shared infrastructure. Use before touching unfamiliar or consequential systems.

Published by suboss87 ↗suboss87/FDEOps

Try your first task

what-breaks

Start a fresh conversation. Replace the highlighted placeholders.

Use what-breaks to perform a blast-radius assessment and create a mitigation plan for [proposed change description] within [target system/module], providing a what-breaks declaration including classification, affected components, data impact, rollback strategy, and monitoring plan.

Required inputs

  • [proposed change description]
  • [target system/module]

User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗

SKILL.md

name: what-breaksdescription: Assess the impact of a proposed change on dependencies and shared infrastructure. Use before touching unfamiliar or consequential systems.

what-breaks

Purpose

A blast-radius assessment and mitigation plan.

Before investigating or acting:

  1. Read the task context contract.
  2. Read the method.

Load further references only when the task needs them. Everything linked is included in this skill; no other skill pack is required.

Principles

  • Work directly from the supplied permitted context. Standalone work does not require an engagement folder or initialization. Record filenames in the method are optional persistence destinations when no engagement is bound.
  • If called by @fde, reuse its current sanitized packet and scope. Do not restart setup, discovery or questions already answered.
  • The task context contract controls persistence and authority in both modes. Preserve unknowns and distinguish implementation, verification, deployment and acceptance.
  • Use the customer's repository instructions and available tools. Report a missing capability or unrun check honestly; do not claim that installing a skill provisions infrastructure.