from qmd-team-intent-kb8
Capture, validate, and share team decisions, patterns, and conventions with a governance pipeline that turns session insights into curated team memory.
This skill provides governed team knowledge management: it captures session insights (decisions, patterns, conventions, architectures, troubleshooting notes, onboarding steps), validates them via deterministic governance policies, and surfaces them as curated team memory. It includes tooling to propose single insights, bulk-import documents, check knowledge health, and transition memory lifecycle states. The workflow is designed to avoid noise by spooling proposals and passing them through curator and conflict-checker subagents before promotion.
Use TeamKB when you want to preserve team-relevant knowledge from meetings or sessions: for recording architectural decisions, documenting recurring patterns, noting agreed conventions, or importing onboarding/setup docs. Avoid using it for ephemeral debugging steps, personal preferences, or secret-bearing content. Typical triggers: end-of-session capture, importing docs directory, or deliberate review of recent proposals.
teamkb_propose), bulk import (teamkb_import), status checks (teamkb_status), lifecycle transitions (teamkb_transition), and sync operations (teamkb_sync). The SKILL.md outlines governance subagents (@teamkb-curator, @teamkb-classifier, @teamkb-conflict-checker) and quality checks to avoid low-value captures.Best suited for conversational/agent environments that support tool invocation and background subagents (Claude Code-style agents, MCP servers). It assumes an MCP server provides the teamkb_* tools and a curator pipeline for promotion.
This skill has not been reviewed by our automated audit pipeline yet.
