Menu

Individual skill

principle-redesign-from-first-principles

Use when a new requirement has to fit into an existing design. Rework the design as though the requirement had been there from the beginning, and carry it into every type, doc, and example, instead of attaching it at the side.

plugins/requie/endostack/skills/principle-redesign-from-first-principles/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,533
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Redesign from first principles

Rework the design so that a new requirement looks like it was there from day one. Bolting it onto the side of the existing structure is the failure this principle prevents.

## When it applies

Fitting a new requirement into a design that already exists. Compare [principle-attack-the-premise](../principle-attack-the-premise/SKILL.md), which challenges a factual belief behind a string of failed fixes.

## What to do

1. Read every affected file and understand the current design before changing it.
2. Ask what you would build from scratch if this requirement had been there on day one.
3. Carry the change into everything that refers to the old design: types, documentation, examples, and the rationale sections explaining why the design looks the way it does.
4. Plan the complete redesign, then deliver it in verifiable increments ([principle-sequence-verifiable-units](../principle-sequence-verifiable-units/SKILL.md)).