How do I install the Pkc Materialize skill?

Run npx skillmds@latest add spillwavesolutions/pkc-materialize in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Pkc Materialize safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Pkc Materialize?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Pkc Materialize free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Pkc Materialize?

spillwavesolutions (@spillwavesolutions) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Pkc Materialize by spillwavesolutions

Name: Pkc Materialize
Author: spillwavesolutions

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.

File contents

PKC Materialize (WikiTicket → OKF)

Batch-emit OKF concepts from WikiTicket without making PKC the system of record for status.

When to use

Project uses WikiTicket SDD (.work/todo.jsonl, bin/worklog)
User asks to “sync tickets into knowledge”, “materialize the worklog”, “import ADRs/designs”

Mapping (normative)

WikiTicket source	OKF type(s)
Work item epic/story	`Feature` + `TicketLink`
Work item task/subtask	`TicketLink` (+ parent Feature link when possible)
Plan (`docs/plans/*.md`)	`Specification`
Design / walkthrough	`Design`
ADR	`DecisionRecord`
Release notes	`Release`
Significant PR page	`CodeChange`

Process

Confirm knowledge root and ensure bundle:

python3 "${CLAUDE_PLUGIN_ROOT}/scripts/pkc_common.py" init-bundle --repo . --bundle knowledge

Obtain worklog fold (repo-local CLI — not part of this plugin):

bin/worklog fold > /tmp/fold.json
# or pipe:
bin/worklog fold | python3 "${CLAUDE_PLUGIN_ROOT}/scripts/pkc_materialize.py" \
  --repo . --bundle knowledge --from-docs

Or from a saved fold / fixture:

python3 "${CLAUDE_PLUGIN_ROOT}/scripts/pkc_materialize.py" \
  --repo . \
  --fold /tmp/fold.json \
  --include features,decisions,designs,releases,tickets,specs \
  --from-docs

Respect truth_state
- Do not overwrite snapshot / superseded / archived with current data unless --force or user requests.
Idempotency
- Re-run updates in place; report created / updated / skipped.
Preserve wiki_key, worklog_id, external_id, external_system when present.
Present the materialize report to the user. Offer okf validation if available.

Config (optional)

.pkc/config.yml or under pkc: in .work/config.yml:

pkc:
  enabled: true
  knowledge_root: knowledge
  materialize:
    from_worklog: true
    from_docs: true
    include: [features, decisions, designs, releases, tickets, specs]

Rules

Never hand-edit .work/todo.jsonl — use bin/worklog only.
PKC does not publish to wiki (WikiTicket wiki-publish remains the publishing plane).
Generated concepts set generated: true.

Done when

Report lists created/updated/skipped counts
TicketLinks exist for open work items
Features exist for epic/story items
Catalogs refreshed

---name: pkc-materializedescription: 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 Materialize (WikiTicket → OKF)Batch-emit OKF concepts from WikiTicket without making PKC the system of record for status.## When to use- Project uses WikiTicket SDD (`.work/todo.jsonl`, `bin/worklog`)- User asks to “sync tickets into knowledge”, “materialize the worklog”, “import ADRs/designs”## Mapping (normative)| WikiTicket source | OKF type(s) ||-------------------|-------------|| Work item epic/story | `Feature` + `TicketLink` || Work item task/subtask | `TicketLink` (+ parent Feature link when possible) || Plan (`docs/plans/*.md`) | `Specification` || Design / walkthrough | `Design` || ADR | `DecisionRecord` || Release notes | `Release` || Significant PR page | `CodeChange` |## Process1. Confirm knowledge root and ensure bundle: ```bash python3 "${CLAUDE_PLUGIN_ROOT}/scripts/pkc_common.py" init-bundle --repo . --bundle knowledge ```2. Obtain worklog fold (repo-local CLI — not part of this plugin): ```bash bin/worklog fold > /tmp/fold.json # or pipe: bin/worklog fold | python3 "${CLAUDE_PLUGIN_ROOT}/scripts/pkc_materialize.py" \ --repo . --bundle knowledge --from-docs ```3. Or from a saved fold / fixture: ```bash python3 "${CLAUDE_PLUGIN_ROOT}/scripts/pkc_materialize.py" \ --repo . \ --fold /tmp/fold.json \ --include features,decisions,designs,releases,tickets,specs \ --from-docs ```4. **Respect truth_state** - Do not overwrite `snapshot` / `superseded` / `archived` with current data unless `--force` or user requests.5. **Idempotency** - Re-run updates in place; report `created` / `updated` / `skipped`.6. Preserve `wiki_key`, `worklog_id`, `external_id`, `external_system` when present.7. Present the materialize report to the user. Offer okf validation if available.## Config (optional)`.pkc/config.yml` or under `pkc:` in `.work/config.yml`:```yamlpkc: enabled: true knowledge_root: knowledge materialize: from_worklog: true from_docs: true include: [features, decisions, designs, releases, tickets, specs]```## Rules- Never hand-edit `.work/todo.jsonl` — use `bin/worklog` only.- PKC does not publish to wiki (WikiTicket wiki-publish remains the publishing plane).- Generated concepts set `generated: true`.## Done when- Report lists created/updated/skipped counts- TicketLinks exist for open work items- Features exist for epic/story items- Catalogs refreshed

Frequently asked questions