Wiki

Scope: memory, retrieval, verification, research filing, drift. For active implementation threads, load /forge.

The wiki is compiled memory. Sources of truth live outside it — code, filed research, and primary documents. Agents keep the markdown honest as those sources change.

Protocol Start Checklist

Shared with /forge. See the forge skill for the full checklist.

Quick reference:

Check repo AGENTS.md / CLAUDE.md managed block.
Run wiki resume <project> --repo <path> --base <rev> when resuming.
When delegating, explicitly load /wiki in the sub-agent prompt.

Skip for pure read-only retrieval.

Behavioral Guardrails

Defined in the forge skill. Apply to all wiki sessions. Load /forge for the full text.

Use Wiki For

maintenance, drift, freshness, verification
retrieval and project Q&A
research filing and audit
onboarding and knowledge scaffolding
protocol sync / audit
navigation/index refresh

Escalate to /forge for non-trivial implementation, active slice work, or anything that is really “do the next slice”.

Main Commands

Use the smallest fitting surface.

Need	Command
Default maintenance entry point	`wiki maintain <project> --base <rev>`
Report-first reconciliation	`wiki sync <project> [--write]`
Git-independent freshness check	`wiki checkpoint <project> --repo <path>`
Re-verify changed pages	`wiki verify-page <project> <page> <level>`
Compact review surface	`wiki closeout <project> --repo <path> --base <rev>`
Pass/fail completion gate	`wiki gate <project> --repo <path> --base <rev>`
Refresh navigation	`wiki update-index <project> --write`
Sync repo protocol files	`wiki protocol sync <project> --repo <path>`
Audit repo protocol files	`wiki protocol audit <project> --repo <path>`
File project research	`wiki research file <project> <title>`
Project Q&A	`wiki ask <project> [--verbose] <question>`
Resume session	`wiki resume <project> --repo <path> --base <rev>`
User-invoked handover	`wiki handover <project> --repo <path> --base <rev>`

SDLC scaffolds remain on the wiki CLI but are part of the forge workflow layer and are documented in the forge skill, not here. Use wiki help for the raw command list.

Verification levels (ascending): scaffold → inferred → code-verified → runtime-verified → test-verified. Demotion state: stale.

Refresh-Only Flow

Use this when implementation decisions are already made and you are just refreshing the knowledge layer.

1. wiki maintain <project> --base <rev>
2. wiki checkpoint <project> --repo <path>
3. update impacted pages from code / source material
4. wiki verify-page <project> <page> <level>
5. wiki update-index <project> --write   (if navigation changed)
6. wiki closeout <project> --repo <path> --base <rev>
7. wiki gate <project> --repo <path> --base <rev>

If this turns into active slice work, switch to /forge.

Retrieval

Quick lookup        -> read the file directly
Broad search        -> wiki search "..."
Hybrid retrieval    -> wiki query "..."
Project Q&A         -> wiki ask <project> "..."
Save an answer      -> wiki file-answer <project> "..."
Resume context      -> wiki resume <project> --repo <path> --base <rev>

Research Filing

Use /research for the investigation itself. Use wiki research ... to file and audit the results.

Core commands:

wiki research file <project> <title>
wiki research scaffold <topic>
wiki research ingest <topic> <source>
wiki source ingest <path-or-url>
wiki research lint [topic]
wiki research audit [topic]

Operating Guidelines

Never create extra wiki-style .md docs inside project repos beyond the allowed set.
Use wiki protocol sync <project> --repo <path> for managed repo instruction blocks.
wiki protocol sync updates protocol files only; it does not refresh installed skills.
After editing skills/*/SKILL.md, run bun run sync:local and restart the agent session. Use bun run sync:local -- --audit when you want to check whether installed repo-skill copies have drifted.
Prefer Obsidian-flavored markdown when editing vault pages.
Bind source paths early so drift detection can see the page.
Set repo: in _summary.md for code projects or pass --repo <path>.
Use wiki maintain as the default maintenance entry point.
Verify after updating.
wiki handover is user-invoked only.
Do not invent CLI features or ad hoc document layouts.

Data Planes

The CLI mainly operates on:

frontmatter
markdown body
git history
filesystem/globs

Think in those planes when deciding whether a task is about authored truth, derived truth, or repo state.

wiki