Skip to content

v0.2.0: The First Release

Latest

Choose a tag to compare

@mpstaton mpstaton released this 08 Oct 17:38
· 33 commits to master since this release

Why Care?

Coding agents forget everything between sessions, and the fixes on offer are heavy: spec frameworks with their own CLIs, memory services, rules about what the agent must load. Context Vigilance is a lighter bet. You add one folder, context-v/, to every repo, and keep specs, plans, explorations, decisions, issues and handoffs in it as plain Markdown with frontmatter. People and agents read and write the same docs.

We've run this across 40+ repos, and for us it has worked better than Spec Kit or OpenSpec. v0.2.0 is the first version packaged for anyone else: a Claude Code plugin you install in two commands, plus context-v.dev, which explains the patterns and the reasons behind them.

What's New?

Highlights

  • Install the practice as a plugin. The cv plugin brings the context-vigilance skill, a workflow skill for every step of the cycle, nine templates, and starters for a new repo.
  • A workflow from first idea to shipped change. /cv:prep plays product manager, /cv:implement lead engineer, /cv:loop VP of Engineering running subagents, and /cv:reflect closes the cycle with an as-built record, a changelog entry and a handoff.
  • Docs that other tools can read. Every context-v/ folder is an Open Knowledge Format bundle: each doc has a type (its folder's name), and each folder has an index.
  • A check on the basics. A hook runs before every write to context-v/ and blocks only on mistakes that have one right answer: YAML that won't parse, a missing title, bad dates, a malformed or changed ID, a wrong type.
  • A site of its own. context-v.dev has Getting Started, twenty patterns, the recommended flow drawn as one diagram, and a FAQ.

Added

  • Workflow skills: /cv:init, /cv:new, /cv:kickoff, /cv:prep, /cv:implement, /cv:loop, /cv:reflect, /cv:decide, /cv:upgrade, plus shortcuts for single doc types (/cv:explore, /cv:spec, /cv:plan, /cv:prompt, /cv:blueprint, /cv:remind, /cv:issue, /cv:handoff).
  • Templates for spec, plan, prompt, blueprint, reminder, exploration, issue, loop, handoff and decision. Each one ends with a "Done when" list.
  • Starters: context-v/index.md, an AGENTS.md snippet, an optional changelog/, a commented config.md that maps roles (tracker, chat, docs, memory) to tools, and an .env.example block.
  • A links: section in config.md that declares a repo's link style. The default is Obsidian's path-and-alias wikilink: [[specs/Payment-Retry-Policy.md|Payment Retry Policy]].
  • The first decision record: context-v is a profile of OKF v0.2.
  • context-v.dev, with Pagefind search, light, dark and vibrant themes, LFM rendering, llms.txt, a sitemap, and OG images. It deploys to Vercel from main and to GitHub Pages from master.

Changed

  • The kit has its own repo. It used to live inside the corpus repo, and installing it would have cloned 55 MB of private history. The corpus is now context-v-corpus.

Install

In Claude Code:

claude plugin marketplace add lossless-group/context-vigilance-kit
claude plugin install cv@context-vigilance-kit

Then run /cv:init in any repo. If your agent isn't Claude Code, copy agent-skills/ into its skills directory, or paste starters/AGENTS.snippet.md into your AGENTS.md. Once installed, /cv:upgrade pulls later versions however you installed.

The Story Behind This Release

This release took one week. It started with a problem: the plugin couldn't ship from the repo it lived in, because that repo also held our whole private corpus. So the kit got a fresh repo with fresh history. Next came the port. Our in-house skills referred to Lossless paths, project names and internal numbers, and each one had to be rewritten for a stranger's repo. Then the format question: should context-v invent its own spec or adopt one? We adopted OKF, which asks for very little, and kept our own lifecycle, versions and IDs on top. The site went up alongside, so each pattern could say why it exists, not only what it is.

The full trail is in the changelog: 2026-10-01_01, 2026-10-05_01, 2026-10-05_02, 2026-10-05_03, 2026-10-05_04, 2026-10-06_01, 2026-10-06_02, 2026-10-06_03, 2026-10-07_01.

What's Next?

  • A first live install on a fresh repo, to confirm it conforms from its first doc.
  • The mirrors/ experiment: a folder that records the current state of the code.
  • MPL-2.0 covers the kit. Whatever you write with it belongs to you.