skills.rest
melissa-pereira-deel
melissa-pereira-deelCOMMUNITY
Explore all skills by this author →
Website𝕏@aistobascistoxGitHub

First-Principles Reduction

Enforce a five-step reduction before automating product designs and processes.

1|Updated Apr 16, 2026
Search Tags:#automation#process-improvement#first-principles#deletion#requirements-analysis#reduction
One-click install
npx skills add https://github.com/melissa-pereira-deel/creative-technologist-agent --skill first-principles-reduction
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: First-Principles Reduction
Source: https://github.com/melissa-pereira-deel/creative-technologist-agent/tree/main/skills/first-principles-reduction
Command: npx skills add https://github.com/melissa-pereira-deel/creative-technologist-agent --skill first-principles-reduction

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Question, delete, and simplify BEFORE optimizing or automating — Musk's Algorithm in strict sequence. Trigger on: 'let's automate this', 'we need to optimize', 'this is too complex', 'how do we scale this?', feature bloat, process overhead, any instinct to improve something that might not need to exist.

Core Features & Use Cases

Five steps, in mandatory sequence. Each must complete before the next. The most common mistake: doing them in reverse. Core inversion — adding feels productive, deleting feels destructive. Optimizing feels intelligent, questioning feels ignorant. Automating feels modern, manual feels primitive.

  • Step 1 — Question the requirements
  • Step 2 — Delete the Part or Process
  • Step 3 — Simplify and Optimize
  • Step 4 — Accelerate Cycle Time
  • Step 5 — Automate Sequence Diagnostic — for any proposed improvement, identify which step it represents. If it's at Step N but Steps 1 through N-1 haven't been performed — stop and go back. Inversion Test — for any system you're about to improve: write what you want to do, invert: what could you DELETE instead?, invert again: what REQUIREMENT could you question? If the inversion reveals a simpler path, take it. Anti-Patterns Premature automation, Optimization worship, Addition bias, Requirement inertia, Sunk cost preservation, Selective application Connections
  • Signal Discrimination — Step 2 (deletion) IS signal discrimination applied to components and processes
  • Deep Deliberation — Step 1 (questioning requirements) demands deliberation before action
  • Constraint Propagation — each deletion propagates; trace effects before and after
  • Coherence Design — the algorithm produces coherence by removing elements that don't strengthen the whole
  • Tools for Thought — Step 5 (automate) raises the amplification vs. automation question: should this be automated or should users retain understanding?

Quick Start

Apply the five-step first-principles reduction to a project by questioning requirements, deleting unnecessary parts, simplifying the remaining design, accelerating cycle time, and only automating if justified.

Frequently Asked Questions about First-Principles Reduction

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

FAQPage Schema
How do I stop feature bloat before automating a product process?▼

Apply a first-principles reduction sequence before automating: question requirements, delete unnecessary parts, simplify, accelerate cycle time, and only then automate. This strict order eliminates wasteful optimization and prevents premature automation in product design.

What is the first step in process improvement when requirements feel too complex?▼

The first step in process improvement is questioning the requirements. You must question and challenge the underlying assumptions of a bloated system before deleting, simplifying, or optimizing any components to ensure changes are justified and traceable.

How do I know if I should delete a process step instead of optimizing it?▼

Use an inversion test: write what you want to optimize, invert it to see what you could delete instead, and invert again to question the requirement. If the inversion reveals a simpler path, deletion is preferred over optimization to reduce waste.

When should I avoid automating an existing workflow?▼

Avoid automating if you have not completed the prior reduction steps: questioning requirements, deleting parts, simplifying, and accelerating cycle time. Premature automation of an unoptimized process is an anti-pattern that preserves sunk costs and bakes in inefficiencies.

What is the best way to simplify a product design before scaling?▼

The best way to simplify before scaling is applying a sequence diagnostic: identify which improvement step you are at, and if steps one through four are incomplete, stop and go back. Ensure deletion and simplification occur before acceleration and automation.

Related Skills

Explore More Product & Management Skills→
pradeepmoulipradeepmouli
2

speckit-baseline

Generate baseline-spec.md and current-state.md from repository analysis.

Community
Advanced
zzxtbetazzxtbeta

land-and-deploy

Merge pull requests, wait for CI, deploy, and verify canary health.

Community
Advanced
DevattomDevattom

workflow-debate

Orchestrate structured adversarial debates between AI councillors to evaluate ideas.

Community
Advanced
herdiansahherdiansah
23

customer-support

Automate customer support with conversational AI and automated ticketing.

Community
Advanced