Coding agents lose the goal across compactions and cold sessions; superstack keeps it.
A per-workspace record carries your goals, corrections, and evidence, surfaced at every session start, and shell hooks fire at the chokepoints whether or not a skill loads: the claims gate bounces a bare done-claim, the publish gate holds a push until a fresh sweep exists. Specialist skills cover the lifecycle from shaping an idea to shipping it.
Skills 25 in the Claude listing
superstack Superstack autonomy Unattended work — "go ahead while I'm away", "run overnight", "proceed autonomously", a mandate for hours of solo work — and the return report after. Superstack cocreate A wanted artifact with latent requirements — doc, plan, spec, schema, API shape, a look — where questions get "show me options" and requirements arrive as reactions. Superstack continuity Resuming or handing off — after a crash, session limit, compaction, or model handoff; picking up a HANDOFF or state file; closing a session with work in flight; the SessionStart continuity line. Superstack debug Use when behavior contradicts expectation — a bug, an unexplained error, a failing test, output that looks wrong, a fix that didn't hold — or when you're about to retry the same category of fix a seco Superstack decide A mid-work technical fork — "which way should we go", a design/architecture/tooling choice about to lock — or the user ruling on how the thing is built (conduct rulings are superstack-doctrine's). Superstack deps Dependencies need moving — an EOL or deprecation notice, a security advisory, "upgrade to vX", "how far behind are we". Superstack digest A period report for a reader outside the session — a weekly update, client status, "what did we get done this month". Superstack doctrine A correction or standing ruling from the user — a rebuke of a working habit, "make this a rule", "always do X", "never do Y again". Superstack execute Run a campaign — a build with milestone structure spanning many sessions — from an opened plan through audited milestones to closure, surviving compaction and cold starts. Superstack experiential An artifact with a face — a UI, dashboard, chart, game, rendered document, CLI output a human reads — whenever one is built or changed, before claiming done; and before trusting any new check or harne Superstack inception A new idea with no spec — a product, tool, feature, or app arriving as "I have an idea", "let's build", "create/make me X". Superstack incident A live incident — production down or degraded, users affected, data at risk, a deploy gone wrong — however phrased ("why is this broken" included); mitigation outranks diagnosis while harm is ongoing. Superstack migrate A schema or data change with real data behind it — DDL on a live table, a backfill, retyping/renaming columns, moving data between stores. Superstack outward Going public — a push, PR creation or merge, a package publish, a release, an infra apply; run before any of them, and when the outward gate bounces a publish command. Superstack queue Parked work — "park this", "add it to the backlog", "someday", a shaped idea inception parks, a deferral with a revisit trigger; read the queue first when starting fresh work. Superstack review Use before trusting or shipping an answer, design, plan, analysis, or risky code change — when you are about to commit to it. Superstack scope Use at the start of a non-trivial task, or when the goal is fuzzy, the request is solution-shaped, or you cannot yet state in one sentence what "correct" will be checked against. Superstack ship Use when finishing a task — writing the final report or status, shipping a change, or handing off — to produce a calibrated done-claim and the docs that make the work reproducible by someone else. Superstack smith A new skill or pack for a superstack-family plugin — "new skill", "add a module", "build a pack for X" — or a recurring moment applying for admission. Superstack spike A feasibility question, not a delivery — "can X even do Y", "is this viable", "how expensive would Z be" — where throwaway code is the cheapest probe. Superstack status Use when the user asks for the superstack status, overlay health, the calibration record, or what the method has been tracking in this workspace. Superstack teach The human wants to understand — "walk me through this", "explain at my level", "teach me" — or a handover where the maintainer is the human. Superstack value An outcome claim shipping — "this should increase signups", "this saves the team time" — recorded as a dated, falsifiable prediction; settled when the SessionStart line says due. Superstack verify Use when about to claim work is complete, fixed, passing, correct, or done — before committing, opening a PR, or moving to the next task. 