Run any Skill in Manus with one click

zero-tech-debt

Stars0

Forks0

UpdatedMay 16, 2026 at 22:13

Rework a change as if the intended UX and architecture existed from day one, deleting compatibility cruft and accidental complexity. Trigger: /zero-tech-debt.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

misty-step

misty-step/gradient

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	zero-tech-debt
description	Rework a change as if the intended UX and architecture existed from day one, deleting compatibility cruft and accidental complexity. Trigger: /zero-tech-debt.
user-invocable	true
argument-hint	[--scope <path>] [--report-only] [--apply]

Zero Tech Debt

Use this when a patch preserves old modes, wrappers, aliases, flags, or fallbacks only because they already existed. The goal is the intended end state, not the smallest diff from the historical path.

Decision

This primitive belongs in Gradient's repo-local harness first because Gradient needs it immediately for self-maintenance. It should be upstreamed into Spellbook once a few real Gradient cycles prove the wording and gates are portable across repositories.

Steps

State the intended end state in one or two sentences.
Search for real callers before preserving compatibility. If a mode, prop, wrapper, route alias, fallback, or command path has no current caller, delete it.
Reshape around the final product surface. Prefer one clear component or flow over mode flags. Split only when it creates an obvious boundary such as state, layout, controls, or domain commands.
Move shared rules to one place. Feature flags, permissions, route gating, URL state, and command naming should not be duplicated across pages or hidden in view components.
Verify the intended flow and any deleted assumptions that affect navigation, permissions, persisted state, or public contracts.

Rules

Optimize for the code that should exist, not the smallest diff from the old shape.
Delete dead compatibility paths instead of making them better.
Do not invent a generic framework for one feature.
Keep the refactor scoped to what makes the final shape coherent.
Prefer names that describe product intent over implementation history.

Gradient Gate

For Gradient itself, run:

./scripts/gradient.sh validate
./scripts/gradient.sh eval

The evidence packet should name what compatibility path was deleted or why it was kept because a real caller still exists.

More from this repository

same repository

harness

misty-step/gradient

Maintain Gradient's repo-local agent harness: skills, agents, settings, repo brief, and gate-aligned instructions. Trigger: /harness, /skill, /primitive.

2026-05-180

deliver

misty-step/gradient

Take one shaped Gradient docs/schema/profile task to merge-ready. Composes /shape, /implement, /code-review, /ci, /qa, /demo, and /refactor as needed. Stops before merge. Trigger: /deliver.

2026-05-180

agent-readiness

misty-step/gradient

Assess Gradient's readiness for governed agent work across docs, schemas, profiles, harness, validation, evidence, and public-safe boundaries. Trigger: /agent-readiness, /readiness.

2026-05-160

ceo-review

misty-step/gradient

Dialectical premise-and-alternatives audit for a plan, spec, or context packet. Four moves: premise challenge (is this the right problem?), mandatory structurally-distinct alternatives, cross-model outside voice, user-ratified convergence. Named for Gary Tan's plan-ceo-review pattern; operationalizes the AGENTS.md "Diverge Before You Converge" doctrine at the plan-review stage. Use when: about to commit to a plan/spec/design, reviewing a ticket before shape, when "is this the right problem" would be useful, or any time a proposal smells like a symptom fix instead of a root-cause fix. Trigger: /ceo-review, /challenge, /premise-check.

2026-05-160

misty-step/gradient

Gradient gate audit and validation workflow. Use when checking whether a docs/profile/schema change is safe to ship in this scaffold. Trigger: /ci.

2026-05-160

code-review

misty-step/gradient

Review Gradient docs, profiles, schemas, and harness changes for public-safe boundaries, lifecycle consistency, and contract depth. Trigger: /code-review, /review, /critique.

2026-05-160

Zero Tech Debt

Decision

Steps

State the intended end state in one or two sentences.

Search for real callers before preserving compatibility. If a mode, prop, wrapper, route alias, fallback, or command path has no current caller, delete it.

Reshape around the final product surface. Prefer one clear component or flow over mode flags. Split only when it creates an obvious boundary such as state, layout, controls, or domain commands.

Move shared rules to one place. Feature flags, permissions, route gating, URL state, and command naming should not be duplicated across pages or hidden in view components.

Verify the intended flow and any deleted assumptions that affect navigation, permissions, persisted state, or public contracts.

Rules

Optimize for the code that should exist, not the smallest diff from the old shape.

Delete dead compatibility paths instead of making them better.

Do not invent a generic framework for one feature.

Keep the refactor scoped to what makes the final shape coherent.

Prefer names that describe product intent over implementation history.

Gradient Gate

For Gradient itself, run:

./scripts/gradient.sh validate ./scripts/gradient.sh eval

The evidence packet should name what compatibility path was deleted or why it was kept because a real caller still exists.