Vstack – AI for Management and Leadership Vstack released an open-source tool that turns recurring management writing tasks — weekly leadership updates, daily program status reports, talent cards, work summaries and promotion documents — into JSON "workflow" files run on existing coding agents including Claude Code, Codex, Kiro CLI and Kiro Crew. The engine is a single dependency-free Python file at bin/vstack that renders a workflow into a prompt, executes it on the chosen harness, verifies the run directory, keeps a ledger and prints schedules and agent templates, and it refuses to mark a job done until the artifacts prove it. Company-specific facts live in a separate private "instance" repository that vstack reads at run time but never contains, with a check that fails if that boundary is crossed. Run a manager's recurring writing work on any coding agent, with proof it was done right. A weekly leadership update, a daily program status, a talent card, a work summary, a promotion document: each is the same job. Gather evidence from the systems that hold it, write in a fixed voice, check the draft against a checklist, put it where a human presses send, record what happened. vstack turns that job into a file a workflow , runs it on the coding agent you already have Claude Code, Codex, Kiro CLI or Kiro Crew , and refuses to call it done until the artifacts prove it. Everything that names your company lives in a second, private repository called the instance . vstack reads it at run time and never contains it, and a check fails if the line is crossed. | Word | Means | |---|---| | workflow | one recurring document as one JSON file: trigger, sources, writer, gate, sink, ledger. workflows/weekly-update.json is a workflow. Everything vstack does, it does to a workflow | | instance | the private folder and repository that holds your company's facts: which tools, which documents, which channels, which people. vstack reads it, never contains it | | connector | a capability name a workflow asks for chat.search , docs.read . The instance's connectors.json binds each connector to a real MCP server and tool, so workflows never name tools | | harness | the coding agent that runs the prompt: Claude Code, Codex, Kiro CLI or Kiro Crew | | run | one execution of one workflow: a directory of artifacts under ~/.local/state/vstack/runs/ and one ledger line | Three more words appear once you are inside: a glossary is your company's vocabulary the writers substitute, context is the standing inputs a workflow reads every time template contracts, rules, rubrics , and a brief is the three lines you read instead of the draft. example/ is a complete instance for a made-up company. Copy it to start yours; the checks also use it as the proof that the invariants hold on a real layout. Everything in vstack is one of three kinds of thing, and the sections below follow that order: Define what should happen every time, in the instance , Run what happened this time, on disk , Check what refuses a bad definition or a bad run, in the engine . | Piece | What it does | Where | |---|---|---| | engine | one Python file, no dependencies. Renders a workflow into a prompt, runs it on a harness, verifies the run directory, keeps a ledger, prints schedules and agent templates | bin/vstack | | skills | the writers executive update, talent card, work summary, promotion doc , the critic validate-writing , the rewriters, and two plumbing skills. Plain markdown in the open Agent Skills https://agentskills.io/specification format | skills/ | | harness adapters | how each of the four agents is invoked non-interactively and where it reads skills from | harness/README.md , harness cmd in the engine | | example instance | a complete instance for a made-up company: connectors, glossary, one workflow with its sample evidence. Copy it to start yours | example/ | | evals and checks | a nine-group check script, a routing eval for the skills, sample evidence with expected outcomes | scripts/ , evals/ | your private instance vstack this repository your harness ───────────────────── ──────────────────────── ──────────── workflows/weekly-update.json ─┐ connectors.json ├─▶ vstack run