What’s inside

One SKILL.md (the playbook) + one starter template. A preview:

Project Knowledge Graph

When to use

• A new joiner asks "how does this project fit together?" and the honest answer is a tour of five folders and three chat histories
• Decisions live in people's heads or scattered threads, and the same question gets re-decided every few months
• Your project has more than a dozen documents and nobody can say which ones are current
• You need to find the blast radius of a change: what breaks if this requirement, vendor, or person changes
• Handover is coming and the knowledge can't walk out the door with one person

Workflow

1. Set the boundary (input: project → output: scope statement)
   Name the project and draw its boundary in one paragraph: what's in (the product, the team, the docs, the decisions) and what's out (adjacent projects, company-wide policies). A graph without a boundary becomes a map of everything, which is a map of nothing. List the sources you'll draw from: the docs folder, the decision log or meeting notes, the task tracker, the repo, the chat channels. If a source is off-limits, say so now — a graph that silently omits the place where decisions actually happen teaches false confidence.
2. Define the entity types (input: scope → output: entity schema)
   Fix a small set of node types — five to seven, no more: Person, Decision, Document, Task, Component (a part of the product), Requirement, and External (a vendor, client, or dependency). Every node gets the same fields: name, one-line description, owner, date last verified, and source link. Every node also gets a status: current, superseded, or draft. Define the relationship types too: decides, depends on, documents, owns, blocks, supersedes. A small fixed vocabulary beats a free-for-all — if two people can describe the same link differently, the graph can't be queried or trusted.
3. Extract the nodes (input: sources → output: node list)
   Go through the sources and list every entity that matters: every decision with its date and decider, every document with its status, every component with its owner, every person with their role on this project. Prefer extraction from real sources over recall — quote the doc, link the thread, cite the meeting date. Mark anything uncertain as draft and note what's missing ("decision date unknown — confirm with {name}"). A graph with honest gaps is useful; a graph that presents guesses as facts is a trap. Expect the first pass to surface duplicates and contradictions — two docs describing the same decision differently is a finding, not a failure.

Template preview

Project Knowledge Graph — Build Template

A map of how the project fits together. Scope first, sources always, honest gaps.

Scope statement

• Project: {name}
• In: {product, team, docs, decisions — what the graph covers}
• Out: {adjacent projects, company-wide policies — what it does not cover}
• Sources used: {docs folder / decision log / meeting notes / task tracker / repo / chat channels}
• Sources excluded: {off-limits sources — named, not silently omitted}

Entity schema (fixed — 5–7 node types)

Relationship vocabulary (fixed — add types deliberately, with a definition):

Node list (extract from real sources — quote the doc, link the thread)

Buy the full skill pack — $4.99 Pro — all 471 skills