Dogfood
The kit's own context-v.
The kit is built with the practice it ships. These are its specs, explorations, and decisions, including the parts we changed our minds about. Grouped by folder, newest first.
Want to see the practice at scale? The corpus collects 1,000+ of our docs across 40 projects.
decisions/ 1 doc
explorations/ 2 docs
-
Context-V as a Portable Plugin Any Agent Can Install
A human pastes one line, and their agent does the rest. The last mile of the cv plugin is an install contract written for agents, with Claude Code as the first harness, not the only one.
context-v/explorations/context-v-as-a-portable-plugin-any-agent-can-install.md -
Context-V as a Claude Code Plugin
The conventions are good and the agent still forgets them. A plugin turns context-v's workflows into commands and its frontmatter into queries — so a loop's preconditions get checked instead of remembered.
context-v/explorations/context-v-as-a-claude-code-plugin.md
plans/ 1 doc
specs/ 3 docs
-
Survey: a Scoped Dashboard of context-v
One command turns every context-v/ folder in scope into a dashboard, a task list, and a map, the way graphify turns code into a graph.
context-v/specs/survey-a-scoped-dashboard-of-context-v.md -
MVP: context-v as a Claude Code Plugin
The kit's MVP is not the Chroma memory system the June specs planned — it's a plugin where `/plugin install` is the whole onboarding.
context-v/specs/mvp-to-claude-code-plugin.md -
Commands and Agent Skills for context-v
Catalog of every command, slash command, and agent skill the kit ships — surfaced natively via `.claude/commands/` and `.claude/skills/`.
context-v/specs/commands-and-agent-skills-for-context-v.md