القائمة
Rework a change as if the intended UX and architecture existed from day one, deleting compatibility cruft and accidental complexity. Trigger: /zero-tech-debt.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Maintain Gradient's repo-local agent harness: skills, agents, settings, repo brief, and gate-aligned instructions. Trigger: /harness, /skill, /primitive.
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.
Assess Gradient's readiness for governed agent work across docs, schemas, profiles, harness, validation, evidence, and public-safe boundaries. Trigger: /agent-readiness, /readiness.
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.
Gradient gate audit and validation workflow. Use when checking whether a docs/profile/schema change is safe to ship in this scaffold. Trigger: /ci.
Review Gradient docs, profiles, schemas, and harness changes for public-safe boundaries, lifecycle consistency, and contract depth. Trigger: /code-review, /review, /critique.
| 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] |
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.
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.
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.
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.