vivantel
OrganizationGive your AI coding agent durable, checkable knowledge — decisions, facts, and guardrails it won't forget, contradict, or re-litigate. Claude Code / Codex / Kilo plugin marketplace.
Categories
Indexed Skills (14)
bootstrap
One-time setup of a fact/decision/guardrail/skill knowledge system in a project that has none yet, or a gap-fill pass over one that's incomplete — extract intents from git history, extract facts from existing docs, audit guardrails for missing derivation, and inventory fitness functions. Use when the user wants to set up knowledge management for a project, e.g. "bootstrap the knowledge system here", "set up facts/decisions/guardrails for this repo".
capture
Turn what a work session produced into durable knowledge — draft new decisions, update changed facts, flag contradictions, catch human-doc drift. Use after a work session that touched decisions, facts, or documented behavior, e.g. "run the knowledge check", "did anything here need capturing as a decision or fact".
lint
Full-repo validation pass over a project's fact/decision/guardrail/skill knowledge system — dangling references, stale prose cross-references, missing required fields, numbering collisions, expired decisions, redundant guardrails, audit-log-style facts, verbosity, and stale derived artifacts — independent of what changed this session. Use when the user wants the whole knowledge base checked for health, e.g. "lint the knowledge base", "check the whole docs/ tree for problems".
onboard
Creates a role-specific onboarding plan from a project's existing knowledge artifacts, without writing anything. Use when the user wants a ramp-up plan for a specific role, e.g. "onboard me as a frontend developer for this project", "what should a new QA hire read first here".
roadmap
Interview the user about a plan or decision, then capture the outcome as durable knowledge-management artifacts (facts, intents/decisions, guardrails, procedures) plus a self-sufficient standalone roadmap. Use when the user wants a decision captured as project knowledge — not just discussed — e.g. "interview me and save this as knowledge", "capture this as an ADR", "turn this into a roadmap".
uninstall
Finds everything bootstrap/capture added to this project and offers to detach or remove it, before you actually uninstall the kms plugin. Use when a team is winding down use of kms, e.g. "we're uninstalling kms, clean up what it added", "remove kms's guardrails from this repo".
attribute
Write commit messages and PR descriptions that lead with intent (why, not what), using Conventional Commits type prefixes and Refs: trailers linking to docs/{facts,decisions,guardrails,skills}/ artifacts. Use when the user wants to commit changes with attribution, or generate a PR description, e.g. "commit this with attribution", "write a PR description for this branch".
brainstorm
Generative ideation partner that explores multiple approaches to a problem or feature without writing anything or consulting the knowledge base. Use when the user wants options generated before any decision exists, e.g. "brainstorm approaches for implementing websocket reconnection logic", "what are some ways to solve X".
changelog
Generate a CHANGELOG.md entry from git commit history (since the last tag, or full history if none exists), grouped Keep a Changelog style from Conventional Commit type prefixes and Why-bodies. Use when the user wants a changelog produced or updated, e.g. "generate a changelog", "update the changelog for this release".
clarify
Interview the user relentlessly about a plan, decision, or idea until reaching shared understanding. Use when the user wants their thinking stress-tested, or asks to be "grilled" or "interviewed".
conform
Checks whether a pending changeset conforms to existing decisions and guardrails before it lands. Use before committing or merging, e.g. "does this diff conform to our guardrails", "check this PR against what we've decided", "conform check the last 3 PRs".
query
Answer a question from a project's fact/decision/guardrail/skill knowledge base, with citations to the artifacts the answer is drawn from — never from memory or inference when the knowledge base already has the answer. Use when the user asks what was decided, why a rule exists, or what's currently true about the project, e.g. "what did we decide about X", "why does this guardrail exist".
quickstart
Sets up a project's knowledge system and captures one real decision live, in the same sitting, so the value is felt immediately rather than left for later. Use when a user is trying this plugin for the first time, e.g. "get me started with this", "set this up and show me how it works".
refactor-plan
Produces a safe, phased refactoring plan that respects existing decisions and guardrails, without writing anything. Use when the user wants a refactor planned against what the project has already committed to, e.g. "plan a refactor of the payment module to use Stripe instead of Braintree", "plan migrating from REST to GraphQL".
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.