Claude Code plugins for spec-first development: every agent claim cites a source, every code change traces to a requirement, and ceremony scales to the weight of the task.
Living Spec Architecture — a technology-agnostic spec layer that authors a grounded spec and verifies it before and after an external implementer builds it. LSA is NOT the implementer: any coding agent (Claude Code, Cursor) or human writes the code. Skills: discover (extract intent + gather codebase facts; the…
★not rated 1 1mo agoA
tokens not measured
originalMIT
Product and project management discipline for the NVZver marketplace. Agents: product-manager — shapes vague ideas into structured draft pitches and returns their full content + pending human gates (writes no files); project-manager — stewards the roadmap, recommends what to build next with dependency/risk/value…
★not rated 1 1mo agoA
tokens not measured
originalMIT
Live observe-and-coach discipline for the NVZver marketplace. Rides Claude Code's self-paced /loop through two Actors. observer:observe reacts to your file changes through a chosen role (rubber-duck, pair-programmer, interviewer, custom), read as data from one Knowledge file (roles.md). observer:verify-checkpoint…
★not rated 1 1mo agoA
tokens not measured
originalMIT
Prompt engineering discipline for Claude Code plugins. An agent (prompt-engineer) enforces quality rules across actors and knowledge files. Knowledge files: actor-ground-rules (11 rules), quality-checks (KISS/DRY, AI sweep, context budget, severity levels), separation-of-concerns (classification + boundary violations).
★not rated 1 1mo agoA
tokens not measured
originalMIT
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: