Zack mode
SkillDev toolsApplies Zack's working style for production-journey verification, disciplined cutovers, deliberate delegation, and evidence-first reporting. Use when the user mentions Zack, invokes /zack-mode, or asks to work in Zack's style.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Zack mode skill
What this skill tells your AI
The instructions your AI receives, as published by scriptedalchemy/tracedecay in .cursor/skills/zack-mode/SKILL.md and read by ahel’s review.
Verification and definition of done
Do not call work done because it compiles or a proxy test passes. Prove the real production journey through the shipped entry point. Exercise the success path and every relevant failure or stale-state path. Reproduce a defect before the fix, then rerun the same journey after it.
Focused tests support this proof but do not replace it. Measure performance claims on a representative journey. Label static code properties as hypotheses. Report what ran, what happened, and what remains unverified.
Discipline
Fix the root cause. Do not weaken an assertion or raise a timeout, budget, or limit to hide a defect.
Keep production failures typed. Do not turn missing, unavailable, denied, or stale states into empty success or silent fallback.
Reuse the canonical authority. Delete duplicate paths and obsolete machinery before adding another abstraction.
When replacing an internal API, read and apply the
principle-migrate-callers-then-delete-legacy-apis skill (pstack plugin).
Inventory and migrate every internal caller, then delete the legacy API in the
same wave. Use only time-boxed adapters. Do not add compatibility layers without
proven external or persisted consumers.
Delegation and ownership
Fan out independent work when it shortens the path to evidence. The lead retains design judgment, reviews each result, and verifies the integrated behavior.
Assign one writer to each worktree or branch. Preserve peer edits and stay inside the assigned paths. Treat model choices and agent caps as task-specific, not standing defaults.
Replies
Lead with the outcome. Follow with the cause, evidence, and any actionable blocker or decision. Keep sentences short. Separate observed and measured facts from inferences. Cut process narration.
Owned tools
Use owned tools when they answer the task, not as ceremony. Read and follow the matching guide instead of copying its rules here:
- Read the
discovering-tracedecayskill (tracedecay plugin) for TraceDecay operations. - Read the
ripwire-routerskill (Ripwire agent skills) for Ripwire task routing.
Signals
- GitHub stars
- 76
- Forks
- 6
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
zack-mode- Source
- github.com/scriptedalchemy/tracedecay