vstack-s0-decompose — Claude Code skill: system mapping
vstack-s0-decompose is a Claude Code skill that maps system control, data flow, and boundaries, then builds evidence-backed historical anchors. It runs during analysis of a pinned source revision before verification.
MIT ★ 89 updated 2026-11-16
/plugin marketplace add hao-ai-lab/vstack
/plugin install vstack@hao-ai-lab-vstackWhat vstack-s0-decompose does
The skill separates mutable state and its writers from data and computation consumers, then maps handoffs across system boundaries. Each recorded fact is tied to a file path, line, and commit; unsupported conclusions stay marked as unverified. It also searches related components for historical candidates and records rejected matches and search coverage.
For calibration, the skill freezes the historical-fix denominator I_U, exclusion reasons, and SHA-256 before the coordinator draws calibration and blind sets. Critical assumptions about physical behavior and synchronization are tested on the real system with authorized resources. Source review is manual. The source KB checker is repository-specific and is not bundled.
What it helps with
- map system control, data flow, and boundaries
- identify every writer of mutable state
- record historical bugs and fixes against source revisions
- test assumptions about handoffs and synchronization
- prepare calibration and blind sets
Example prompts for the agent
- Map this pinned source revision into control, data, and boundary views.
- Find every writer of ownership and in-flight state, then trace the producer-to-consumer handoff.
- Build evidence-backed historical anchors and prepare the calibration and blind sets.
How to install vstack-s0-decompose
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-s0-decompose -a claude-code3Manually: put the files in place
~/.claude/skills/vstack-s0-decompose/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/vstack-s0-decompose/
1Skills CLI (Vercel)
npx skills add hao-ai-lab/vstack --skill vstack-s0-decompose -a codex2Manually: put the files in place
.agents/skills/vstack-s0-decompose/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add hao-ai-lab/vstack --skill vstack-s0-decompose -a cursor2Manually: put the files in place
.cursor/skills/vstack-s0-decompose/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install hao-ai-lab/vstack skills/vstack-s0-decompose2Manually: put the files in place
.github/skills/vstack-s0-decompose/SKILL.md1Skills CLI (Vercel)
npx skills add hao-ai-lab/vstack --skill vstack-s0-decompose -a gemini-cli2Platform CLI
gemini skills install https://github.com/hao-ai-lab/vstack --path skills/vstack-s0-decomposeManually: put the files in place
.devin/skills/vstack-s0-decompose/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-s0-decompose
How do I install vstack-s0-decompose 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-s0-decompose do?
It maps state, data flows, and system boundaries, links findings to source evidence, and prepares historical anchors for verification.
What does vstack-s0-decompose need to run?
It needs a pinned source revision and existing anchors for deduplication. Critical physical assumptions are tested on the real system using authorized resources.
Source text
SKILL.md · MIT
--- name: vstack-s0-decompose description: "Map a pinned system into control, data and boundary views and build evidence-backed historical anchors before verification." --- # S0 — Reconstruct and separate the system Read [Layer 0: shared operating rules](../../docs/layer-0.md), this stage and the assigned input bundle. ## Role and write scope Assigned investigators own separate maps and candidate files; a verifier and coordinator check evidence. Target source is read-only. ## 1. Input A fixed source revision and existing anchors for deduplication. ## 2. Procedure 1. Build a control map of mutable state, owners and **all** writers. Search all assignments before saying a field has one writer. 2. Map data and computation consumers and their unchecked preconditions. At each boundary, map the producer, consumer, execution context, overwrite time and synchronization. Classify every in-scope file. 3. Record facts with `path:line@commit` and short source excerpts. Keep unsupported inferences explicitly unverified. 4. Search the target and related systems by component. Record every examined candidate, rejection reason and search coverage. Confirm buggy triggers and fixed behavior on the stated revisions; a closed issue is not evidence that a fix merged. 5. Test critical physical and synchronization assumptions on the real system before treating them as axioms, using authorized resources. 6. For the full [adequacy readout](../../docs/model-adequacy.md#denominator-i_u), freeze each slice's historical-fix denominator `I_U` with its exclusion reason codes and SHA-256. The coordinator then draws the calibration set by a published seed and seals the blind set `H`, removing every trace of `H` from the maps handed downstream. ## 3. Exit checks - Require zero evidence schema errors and a positive checked-item count. The source KB checker is repository-specific and is not bundled. - Have the verifier and coordinator review original source and bind review marks to its content. This review is manual. - Classify every file, label unsupported claims and deduplicate upstream identifiers. These checks have no generic automation. - Keep disproved anchors. Rename an unsupported historical `Bug*` switch to `Mut*`; do not count it as historical calibration. ## 4. Rollback An invalid physical assumption reopens the boundary map. A downstream report of a missing state writer returns here with the pinned source location. Use [a rollback ticket](../../templates/rollback.md). ## Concrete Examples For a PD KV slot, map every writer of ownership and in-flight state, then record the producer-to-consumer handoff. An unsupported historical-bug claim stays a mutation hypothesis until pinned code supports it.
© Hao AI Lab · MIT · hao-ai-lab/vstack