SpillwaveSolutions/project-knowledge-capture

cursor-project-knowledge-capture

Bind a Cursor agent (including Grok Bot cloud sessions) to the project-knowledge-capture ContentPack.

pkc-context

Build a progressive-disclosure context pack for a Feature (or any concept). Supports --tiny (1 hop / 8 nodes) for chat focus and mermaid graphs. Auto-run when starting work on a Feature.

project-knowledge-capture-deep-agents

Bind Project Knowledge Capture for LangChain Deep Agents / Deep Agents Code.

grok-bot-project-knowledge-capture

Bind a Grok Bot agent to Project Knowledge Capture. Isolation, identity, deterministic capture.

pkc-session

Open or close an isolated second-brain write session (worktree + PR). Use before capturing or materializing when multiple agents share one knowledge remote.

pkc-capture-thread

Capture Slack/Discord/chat thread paste as Meeting or Discovery. Scrubs secrets/PII. Use when user pastes a conversation.

pkc-digest

Weekly/daily knowledge digest — recent captures, decisions, open questions, unvalidated assumptions, needs-verification queue, doctor highlights.

Source text: Undetermined

pkc-federate

Multi-repo federated knowledge roots — list remotes, search across them, write shadow federation index. Remotes are read-only; link with maps_to.

pkc-import-adr

Import MADR or adr-tools Architecture Decision Record directories into OKF DecisionRecords.

pkc-release-notes

Generate release notes from Release concepts and Feature/CodeChange edges (released_in, lands_in, implements).

pkc-search

Full-text search over the knowledge bundle (AND terms, type filters). Use when finding decisions, meetings, or features by keyword.

pkc-capture-assumption

Capture an Assumption (weaker than a Decision) linked to Features. Promote to DecisionRecord when validated. Use for working hypotheses and unproven beliefs.

pkc-capture-pr

Capture a GitHub PR as an OKF CodeChange concept via gh pr view (or JSON fixture). Use when documenting significant merges.

pkc-capture-question

Capture an open Question that may block a Feature until answered. Use for unresolved design questions and research gaps.

pkc-capture-transcript

Ingest Fireflies, Otter, Granola, or plain speaker-labeled transcripts into a Meeting concept. Always scrubs secrets/PII. Use when user pastes or provides a transcript export.

pkc-doctor

Run a one-screen health check on a PKC knowledge bundle — broken links, orphans, thin Features, decision conflicts, open Questions, stale Discoveries/Assumptions. Use when auditing knowledge quality or before a release.

pkc-capture-decision

Capture a short decision statement as an OKF DecisionRecord (ADR-style) linked to Features, Designs, Requirements, Meetings, or Experiments. Use for ADRs, architecture choices, and lightweight decision logging.

pkc-capture-discovery

Capture research, competitive scans, user findings, and discovery notes as OKF Discovery concepts with source, confidence, and informs links. Use for research dumps, market scans, and exploratory findings.

pkc-capture-experiment

Capture experiment or spike results into an OKF Experiment concept with hypothesis, method, results, conclusion, and typed informs links. Use for spikes, A/B tests, POC write-ups, and engineering experiments.

pkc-capture-meeting

Capture meeting notes into OKF Meeting concepts, extract DecisionRecords, and optionally create WikiTicket action items + TicketLinks. Use when the user pastes meeting notes, transcripts, or asks to record a meeting decision trail.

pkc-init

Scaffold a Project Knowledge Capture OKF bundle with all PKC catalogs (meetings, experiments, discoveries, decisions, features, …), root index.md, and log.md. Use when starting knowledge capture in a repo or creating knowledge/ / .okf for PKC.

pkc-link

Add a typed edge between two OKF concepts (satisfies, implements, designed_by, decides, informs, originates_from, tracks, maps_to, etc.). Use when connecting meetings to decisions, features to requirements, or tickets to work concepts.

pkc-materialize

Materialize WikiTicket worklog fold and docs/ artifacts into OKF concepts (Features, TicketLinks, Designs, DecisionRecords, Releases, Specs). Use when syncing work items into the knowledge graph or after major planning/docs updates.

pkc-promote

Promote a Discovery, Experiment, or Meeting into a formal Requirement, Feature, Specification, Design, or DecisionRecord while preserving originates_from / informs provenance. Use when informal knowledge is ready to become durable product structure.