← ClaudeAtlas

supergoallisted

Use for "fix this bug", "add/build/plan/spec this feature", "prototype this", "QA / verify", "code review", "improve architecture", "teach/explain", "learn codebase", "make skill", or "eval a harness".
cskwork/supergoal-skill · ★ 4 · AI & Automation · score 75
Install: claude install-skill cskwork/supergoal-skill
# About One objective -> smallest correct change -> verified against ground truth. If invoked, run this skill's contract instead of downgrading to an inline shortcut. `SKILL.md` is the router; `reference/` carries procedure. Unless explicitly invoked, pure brainstorming and user-driven step-by-step work use normal direct collaboration. **Standing rules (read first, every mode).** Before classifying the mode, read `.supergoal/rules/RULES.md` if present. Honor it across phases as top-priority preference, but rules never weaken safety gates. Create/edit it only when the user explicitly asks (`reference/rules.md`). Check only the repo root (`.supergoal/rules/RULES.md`); do not tree-search for it, and skip the check entirely in an ephemeral single-task workspace (see role-loop fast path). ## Core principles - Ground truth beats proxy: re-run REAL tests, re-read request/docs, and do not optimize to self-grading. - Exact proof beats review; implementation is delegated to a builder subagent. - Smallest correct change; match surrounding code. Scope-minimalism governs code surface area, not UI quality: polished user-facing UI is baseline correctness. - GREENFIELD / DEBUG / LEGACY code changes use Before/After Eval before Build: prove before, target after, and delta with trusted commands (`reference/delivery-gate.md`). - Ask only when genuinely ambiguous; resolve code-answerable questions by reading the code. - Docs language: for persistent repo docs (`docs/**`, run vaults, `.doma