Existing Codebase

You don't need a greenfield project to use SDTK. This workflow builds a docs baseline and a local knowledge graph from code you already have — so agents (and humans) stop rediscovering the same architecture every session.

Prerequisite: npm install -g sdtk-kit and an initialized project (Installation).

1. Build the knowledge graph

sdtk-wiki init
sdtk-wiki ingest
sdtk-wiki compile --mode safe          # inspect the proposal first
sdtk-wiki compile --mode safe --apply  # then apply it

ingest reads your repository into the graph; compile proposes wiki pages under wiki/ — safe mode shows you what it would write before --apply commits anything.

2. Explore it

sdtk-wiki atlas build   # native Node, no Python
sdtk-wiki atlas open    # browser viewer — stays alive until Ctrl+C

The Atlas viewer gives you the graph view, docs view, and detail panels. Search and query from the CLI too:

sdtk-wiki search "payment retry"
sdtk-wiki query "<graph query>"

With Pro, ask grounded questions that cite graph nodes:

sdtk-wiki ask "How does the payment flow handle retries?"

3. Docs baseline with Project Intelligence Pro

Where the wiki builds a graph, sdtk-spec project builds and maintains a docs baseline:

sdtk-spec project ingest    # generate the baseline from the code
sdtk-spec project audit     # find gaps and drift
sdtk-spec project refresh   # keep it current as the code evolves

4. Keep it alive

Memory is only useful if it stays current:

sdtk-wiki maintain --mode safe    # propose maintenance actions
sdtk-wiki discover --plan         # propose what to document next
sdtk-wiki lint                    # check wiki health

Re-run ingest + compile --apply + atlas build after significant changes, or leave sdtk-wiki atlas watch running during a work session.

5. Then work normally

With memory in place, every other SDTK workflow gets sharper: discovery sessions reference real architecture, /arch reads actual constraints, and reviews check against documented intent. From here:

• New feature in this codebase → Idea to Ship
• Bounded multi-step maintenance → Durable Agent Runs

Boundaries

• The graph is built from your local repo — no web fetch in this release.
• sdtk-wiki ask needs a Pro entitlement and a built graph, and invokes a model (an explicit external call).
• Nothing destructive runs without an explicit apply.

Where to go next

SDTK-WIKI guideThe memory layer in full.

sdtk-wiki referenceEvery command and mode.

Pro activationUnlock Project Intelligence and Ask.