scorched-earth-mode

Enforce hard-replace development stances without legacy shims or migrations.

1|Updated May 28, 2026
One-click install
npx skills add https://github.com/SilvrDuck/skills --skill scorched-earth-mode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scorched-earth-mode
Source: https://github.com/SilvrDuck/skills/tree/main/skills/scorched-earth-mode
Command: npx skills add https://github.com/SilvrDuck/skills --skill scorched-earth-mode

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents an agent from “helpfully” preserving outdated structures by default—adding shims, aliases, migrations, and parallel old paths even when you want a true hard replacement.

Core Features & Use Cases

  • Manual, persisted opt-in stance: activates only when the project declares it or you explicitly invoke the skill, and it persists via the best available harness channel.
  • Hard-replace bias at every scale: flips defaults for architecture/layout, conceptual models, schema/data shape, API surface, and larger-scope refactors—not just local edits.
  • Forces explicit conflict handling: when prior constraints appear to be load-bearing, it requires surfacing the conflict and asking you to choose rather than silently overriding.
  • Anti-compat enforcement: discourages re-export shims, deprecations, defensive branches for dead legacy, and “leave migration for later” patterns.

Quick Start

Enable the mode for your project by invoking /scorched-earth-mode on and then ask the agent to rewrite the relevant feature without adding compat layers.

Frequently Asked Questions about scorched-earth-mode

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I stop AI from adding backward compatibility shims during a refactor?

To stop AI from adding backward compatibility shims during a refactor, you need a hard-replace bias that explicitly forbids legacy aliases and migrations. This forces the agent to rewrite structures directly without preserving outdated paths.

What is a scorched-earth approach to schema changes and architecture refactoring?

A scorched-earth approach to schema changes and architecture refactoring means ripping and replacing outdated structures completely without leaving parallel old paths or deprecations. It enforces a strict no-compat bias during active iteration.

How do I configure agent instructions for a radical hard-replace codebase overhaul?

You configure agent instructions for radical hard-replace overhauls by manually activating a persisted project stance. This ensures the agent maintains the hard-replace bias across sessions instead of silently preserving legacy structures.

Does the anti-compat refactor bias apply to API surfaces and conceptual models?

Yes, the anti-compat refactor bias applies to API surfaces and conceptual models. It flips defaults across architecture, schema shapes, and scope-wide changes to ensure true hard replacement at every scale.

When should I avoid using a no-compat hard-replace strategy for refactoring?

You should avoid using a no-compat hard-replace strategy when real named external callers depend on your legacy structures. The stance requires surfacing load-bearing conflicts so you can choose rather than silently overriding dependencies.