This tutorial walks through the smallest useful path for using this repo.
Goal: create one clean demo agent setup and one curated knowledge note.
Read these first:
You only need two ideas before continuing:
- durable definitions should have a single source of truth
- runtime state should not be confused with role definition
Open:
- examples/demo-agent/AGENTS.md
- examples/demo-agent/SOUL.md
- examples/demo-runtime-spec.md
- examples/demo-sop.md
This shows the relationship between:
- profile
- runtime spec
- SOP
Start from:
- templates/agent-profile/
- templates/runtime-spec/default-runtime-spec.md
- templates/sop/canonical-sop-template.md
Create a new role by duplicating these templates into your own working area.
Open:
Then fill:
The onboarding flow should produce:
- a canonical profile
- a canonical runtime spec
- a canonical SOP location
- a target workspace that only holds runtime state
Review:
The baseline set is intentionally small:
- brainstorming
- canvas-communication
- connect-the-dots
- writing-plans
- verification-before-completion
Do not add company-specific or agent-specific skills until the baseline layer is stable.
Use:
Put raw material into:
Promote durable material into:
Review the example notes:
- knowledge-graph-template/curated/examples/2026-03-12-skill-driven-organization.md
- knowledge-graph-template/curated/examples/2026-03-12-runtime-spec-vs-runtime-state.md
Once the demo makes sense:
- define one clear role
- write one runtime spec
- write one SOP
- onboard one agent
- create one curated note
Do not scale before this small loop feels clean.
Read: