Lossless Changelog
product

MVP direction set — context-v becomes a Claude Code plugin

A new spec inverts the kit's build order: instead of the Chroma-first memory system the June specs planned, the MVP is a plugin — the context-vigilance skill, a scaffolder, and a five-command surface (/cv:init, /cv:new, /cv:kickoff, /cv:prep, /cv:implement) installable in one step. Chroma becomes an upgrade adopters grow into via /cv:init chroma.

Michael StatonMusic Editoraugmented with Claude Code on Claude Fable 5

Why Care?

The kit's June specs planned an ambitious agent surface — session-start hooks, incremental Chroma ingest, nudge policies, a config ceremony — and every item is still marked Planned. Meanwhile the first outside collaborator arrived and couldn't reach the one thing that actually carries the practice: the context-vigilance skill, trapped in the private skills tree. The new spec resolves the tension by re-ordering, not replacing: the MVP is a Claude Code plugin whose value chain has zero infrastructure links, and the June specs become the tier-2 contract behind an explicit /cv:init chroma seam. First-hand justification recorded in the spec: we built the Chroma tier for ourselves and haven't been using it — if the authors aren't using it, it isn't day-one material for anyone.

What's New?

  • context-v/specs/MVP-to-Claude-Code-Plugin.md (Draft, 0.0.0.4) — the plugin-first MVP spec. Key decisions:

    • Plugin shape: harness-neutral plugin/core/ (skills, commands, templates) + plugin/harnesses/claude-code/ adapter, so adding a second agent harness means adding a folder, not restructuring content.

    • Bundled skills: context-vigilance (light portability pass) and pseudomonorepos (heavy pass — adopters won't know the term, their agent should carry the concept).

    • Five tier-0 commands, namespaced per the verified Claude Code convention (/cv:...): init (scaffold, zero Chroma touchpoints), new (templated doc creation), kickoff (dir-scan-backed loading triage), prep (senior-PM role guiding the explore → spec → plan arc), implement (lead-engineer role executing a signed-off doc in a loop until acceptance criteria are satisfied).

    • The role handoff: prep gates sign-off and refuses to code; implement gates on acceptance criteria and bounces criteria-less docs back to prep.

    • Chroma deferral: subcommand over in-init question — a question taxes every adopter at the moment of least commitment; a named subcommand costs nothing until wanted.

    • Distribution rungs (verified against code.claude.com docs): self-published marketplace in this repo (subdirectory sources confirmed supported) → claude-plugins-community → official claude-plugins-official directory via platform.claude.com/plugins/submit.

What's next

Implementation slice step 1 is deliberate: check what the outside collaborator produced in his own plugin-ization exploration before scaffolding plugin/. When the spec is signed off, the two June specs get a status note recording the re-tiering — a decisions/ entry is the natural artifact for that moment.

  • context-v/specs/MVP-to-Claude-Code-Plugin.md — the spec this entry ships.

  • context-v/specs/Commands-and-Agent-Skills-for-Context-V.md — the full surface catalog, now the tier-2 reference.

  • context-v/specs/Systematizing-Chroma-as-Loading-Mechanism-for-Context-v.md — the tier-2 system contract behind /cv:init chroma.