/supergoal

English | 한국어

One objective in, a verified result out. The smallest correct change, checked against the real tests. Nothing extra to install. Clone the repo, symlink it into your skills directory, then run /supergoal . Landing page: cskwork.github.io/supergoal-skill.

An agent skill for heavy coding objectives where a normal “just edit it” pass is too easy to fool. It takes one objective, chooses the right workflow route, uses fresh-context roles for code delivery, makes the smallest correct change, checks the request and project docs against the real behavior, then stops.

What /supergoal does

/supergoal is a routing and verification wrapper around an agent. The useful mental model:

1. Route the objective. The mode table classifies the real work kind, then routes as build, debug, legacy change, spec, wayfinding, prototype, QA, review, architecture, teaching, domain onboarding, harness eval, or skill mining. Broad new-app builds stay GREENFIELD but first get a wayfinder/ Frontier Map so only one vertical slice enters delivery.

2. Load only the needed playbook. The root SKILL.md stays small; each route loads its own reference/ and agents/ files only when needed.

3. Keep contexts fresh, keep dispatches few. Code delivery runs five gates: Frame, Plan approval, Build, Exact Verify/QA, Finalize. Each iteration uses one fresh-context builder and one auditor. Browser/CLI work adds one evidence-only tester before the auditor. Frame discovers full-spec and edge-case coverage into the plan. The builder implements only the approved plan. The tester captures execution evidence. The auditor reruns the real tests and owns the verdict, the GOAL.md ticks, and R-LOOP.md. One optional extra dispatch exists: a trigger-gated pre-Build plan attack for risky or under-specified work.

   Workflow weight comes in three tiers. LIGHT handles narrow tasks with an explicit spec, running the same five gates with state held in context and no vault or role fan-out. STANDARD runs the full loop. DEEP adds the plan attack and an uncapped clarifying interview. Saying “quick” or “thorough” overrides the detection, and upgrades only go one way. Non-trivial runs spec out the request first: interview answers complete the GOAL.md spec, with Given/When/Then criteria, before PLAN.md exists. User-facing reports follow reference/reporting.md. Outcome first, Simplified Technical English, the project’s own vocabulary.

4. Run Before/After Eval. Capture the before state, define the after target, write a completion promise, and keep a resumable run state plus command manifest so the final claim proves the delta instead of just saying “tests passed.”