PKC Init
Create a knowledge root ready for capture and materialization.
Process
- Confirm target directory (default
knowledge/; accept.okf/or existing OKF bundle). - Scaffold:
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/pkc_common.py" init-bundle \ --repo . \ --bundle knowledge \ --title "Project Knowledge" - Optionally write
.pkc/config.yml:pkc: enabled: true knowledge_root: knowledge okf_bundle: true materialize: from_worklog: true from_docs: true include: [features, decisions, designs, releases, tickets, specs] capture: auto_create_ticketlinks: true bridge: wikiticket: true worklog_bin: bin/worklog - If the repo has WikiTicket data, offer pkc-materialize.
- Point the user at sample chain in this plugin’s
sample-knowledge/for demos. - Run pkc-setup --check. If ripgrep is missing, offer
/pkc-setup(consent-gated). Do not install packages during init unless the user asks.
Directory layout
knowledge/
├── index.md
├── log.md
├── meetings/
├── experiments/
├── discoveries/
├── decisions/
├── features/
├── requirements/
├── specs/
├── designs/
├── releases/
├── code/
├── packages/
└── tickets/
Done when
- Root
index.mdhasokf_versionand catalog links - All catalog dirs have
index.md log.mdinitialized