vstack-mode — Claude Code skill: verification and installation
The vstack-mode Claude Code skill runs staged verification for concurrent, distributed, and systems software. It takes a property from source investigation through proof and regression.
MIT ★ 89 updated 2026-11-16
/plugin marketplace add hao-ai-lab/vstack
/plugin install vstack@hao-ai-lab-vstackWhat vstack-mode does
The skill routes a software property through source analysis, calibrated models, red-team review, proof, and maintained regression. Its playbooks cover full verification, defect hunting, code intended for deductive proof, and running an existing regression.
The coordinator records the property, source revision, inputs, exit checks, and evidence. Work can go to worker agents, with a separate red-team review; delegation requires available host tools and user authorization. Required stages cannot be skipped and marked complete.
If an earlier assumption fails, the workflow calls for a rollback ticket while preserving frozen artifacts. The package has no generic solver harness, and its gate guide should be read before configuring a project runner.
What it helps with
- verify a distributed-system property through staged checks
- find and confirm system defects with a calibrated model
- prepare new code for deductive proof
- run project regression checks and route failures
Example prompts for the agent
- Run full verification for this concurrent-code property.
- Find system bugs and confirm them with a calibrated model.
- Use
/vstack-modeto run the property's regression.
How to install vstack-mode
1Plugin marketplace
/plugin marketplace add hao-ai-lab/vstack/plugin install vstack@hao-ai-lab-vstackThis installs the whole vstack plugin with all its skills
2Skills CLI (Vercel)
npx skills add hao-ai-lab/vstack --skill vstack-mode -a claude-code3Manually: put the files in place
~/.claude/skills/vstack-mode/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/vstack-mode/
1Skills CLI (Vercel)
npx skills add hao-ai-lab/vstack --skill vstack-mode -a codex2Manually: put the files in place
.agents/skills/vstack-mode/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add hao-ai-lab/vstack --skill vstack-mode -a cursor2Manually: put the files in place
.cursor/skills/vstack-mode/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install hao-ai-lab/vstack skills/vstack-mode2Manually: put the files in place
.github/skills/vstack-mode/SKILL.md1Skills CLI (Vercel)
npx skills add hao-ai-lab/vstack --skill vstack-mode -a gemini-cli2Platform CLI
gemini skills install https://github.com/hao-ai-lab/vstack --path skills/vstack-modeManually: put the files in place
.devin/skills/vstack-mode/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about vstack-mode
How do I install vstack-mode in Claude Code?
Add the marketplace with /plugin marketplace add hao-ai-lab/vstack, then install the skill with /plugin install vstack@hao-ai-lab-vstack.
What does vstack-mode do?
It coordinates staged checks for concurrent, distributed, and systems software, from source investigation to proof and regression. Separate playbooks handle defect hunting and running an existing regression.
What does vstack-mode need for delegation?
Delegation needs available host tools and user authorization. Role documents do not provide scheduling or sandboxing on their own.
Source text
SKILL.md · MIT
--- name: vstack-mode description: Run the Verification Stack for a concurrent, distributed or systems-software property, from source archaeology through calibrated models, red team, proof and maintained regression. Use for /vstack-mode or an end-to-end verification workflow. --- # vstack mode Read [Layer 0: shared operating rules](../../docs/layer-0.md). Select one playbook from the request and keep its stage exits visible. The coordinator owns the route, approval records, frozen inputs and final independent review. A worker reads only Layer 0, its own stage and assigned inputs. | Playbook | Route and purpose | |---|---| | [full-verification](playbooks/full-verification.md) | Run S0 through S8; select the proof tier for each property. | | [hunt-system-bugs](playbooks/hunt-system-bugs.md) | Run S0 through S6 to find and confirm defects with a calibrated model. | | [build-provable-core](playbooks/build-provable-core.md) | Run S0 through S5, then S7 and S8, for new code committed to deductive proof. | | [live-regression](playbooks/live-regression.md) | Run the project-local `verify-<case>` produced in S8 and route drift or failures. | A route from S0 through S5 includes every intervening stage. S4 and S5 cannot be omitted. S6 can be omitted only for newly written code going to deductive proof. If a prerequisite is missing, perform it or report BLOCKED rather than calling the downstream stage complete. Record each task's property, source revision, tier, input hashes, writable paths, exit checklist, budget and evidence locations. Use [the case playbook](../../templates/case-playbook.md). Read [working principles](../../docs/principles.md) when scoping or reviewing experiments. Assign work to [vstack-worker](../../agents/vstack-worker.md), independent review to [vstack-redteam](../../agents/vstack-redteam.md), and keep authority with [vstack-main](../../agents/vstack-main.md). Delegate only with available host tools and user authorization. Role documents provide neither scheduling nor sandboxing. At a failed upstream assumption, issue a [rollback ticket](../../templates/rollback.md), preserving frozen artifacts. A property change needs the property owner's explicit decision and coordinator re-pinning. Deliver PASS, ISSUES or BLOCKED with evidence; incomplete or unknown checks never count as PASS. The [gate interface guide](../../docs/gates.md) describes actual scripts and their limits. Read it before configuring a project runner; the package does not include a generic solver harness. ## Concrete Examples Use [PD KV slot lifecycle regression](../../examples/verify-pd-kv-slot/SKILL.md) to see how a slot-release promise becomes pins, drift checks, model checks, trace conformance and mutation regression. This illustrates the workflow, without supplying a runnable case bundle.
© Hao AI Lab · MIT · hao-ai-lab/vstack