@verifiedstate/gstack

Verified memory for gstack parallel sprints.

Running 10 sprints at once? Sprint 3 doesn't know what sprint 7 decided. Files get changed in two places. Decisions get made twice. Bugs get fixed and reintroduced.

This package gives all your gstack sprints shared verified state — every decision, every finding, every change tracked with signed receipts and conflict detection.

Quick start

npm install -g @verifiedstate/gstack

Copy the SKILL.md to your gstack skills:

cp node_modules/@verifiedstate/gstack/SKILL.md ~/.claude/skills/gstack/skills/vs-sync/

That's it. Run /vs-sync in any sprint to see what other sprints are doing.

Programmatic usage

import { GstackMemory, ConflictGuard } from '@verifiedstate/gstack';

const memory = new GstackMemory(process.env.VERIFIEDSTATE_API_KEY!, 'my-project');

// Record a skill result
await memory.recordSkillResult({
  skill: 'review',
  output: 'Found 3 issues in auth.ts: missing null check, unused import, wrong return type',
  files_changed: ['src/auth.ts'],
  branch: 'feature/auth-refactor',
});

// Query what other sprints have done
const context = await memory.getSprintContext('feature/auth-refactor');
console.log(context);

// Check for file conflicts before making changes
const guard = new ConflictGuard(process.env.VERIFIEDSTATE_API_KEY!, 'my-project');
const conflicts = await guard.checkForConflicts('feature/auth-refactor', ['src/auth.ts', 'src/middleware.ts']);
console.log(guard.formatConflicts(conflicts));

What gets tracked

| gstack skill | What's recorded | |---|---| | /office-hours | Product decisions, scope choices | | /review | Code findings, auto-fixes applied | | /qa | Bugs found, regression tests added | | /cso | Security findings, threat model results | | /ship | What was deployed, test coverage delta | | /retro | Process learnings, improvement items |

Cross-sprint conflict detection

Before changing files, check if another sprint is working on the same code:

/vs-sync conflicts

Returns warnings like: "WARNING: src/auth.ts was modified by branch "feature/login" at 2025-04-05T14:30:00Z — coordinate before changing."

How it works

1. Each gstack skill output is ingested into VerifiedState as a structured artifact
2. LLM extraction creates subject-predicate-object assertions from the output
3. All sprints share the same namespace (gstack:<project-name>)
4. Queries return verified assertions with confidence scores and signed receipts
5. Conflict detection checks if files you're about to change have recent assertions from other branches

Links

• VerifiedState Docs
• Get API Key — free tier: 25,000 assertions/month
• gstack — Garry Tan's Claude Code toolkit
• SDK Reference