update-wiki

Wiki Update

After every substantial step, update the wiki to keep it accurate. The wiki is documentation — update freely, no human sign-off needed for prose.

Prerequisites

Wiki/ must exist. If it doesn't, invoke the init-wiki skill first.

What counts as "substantial"

• New code written or existing code changed
• A work item created, updated, or completed
• A resource added or analyzed
• A bug found and fixed
• A design decision made
• An experiment run and results obtained
• Any task completed from a work item

Update procedure

1. Read current state

Read Wiki/Index.md to understand what articles exist and the wiki structure. Skim Wiki/Status.md for current project state. You do NOT need to read every article — only read the ones you'll modify.

2. Create or update articles

For each entity affected by the change:

• New entity: create Wiki/<Folder>/<Name>.md using the article format below
• Changed entity: update the relevant article's content to match current reality
• Removed entity: delete the article and remove its index entry

Article format (every new article carries a [ LLM Generated ] marker under its title):

# Title

*[ LLM Generated ]*

One-paragraph summary.

## Details

Body. Use subsections as needed.

## See also

- [Other Article](../Folder/OtherArticle.md) — why it's related

Keep articles concise and factual. Write like an encyclopedia, not a journal.

When CLAUDE.md has Semantic line breaks: on (the default — see its Source formatting rule), write the article source one sentence per line. This changes only the source; the rendered article is unchanged.

3. Update Wiki/Index.md

Add one-line entries for new articles. Remove entries for deleted articles. Update summaries if they've changed. Entry format:

- [Title](Folder/Name.md) — one-line summary

4. Update Wiki/Status.md

If the knowledge base changed (new results, articles, or open questions), update the relevant sections. Execution state — active work and blockers — lives in Work/README.md, not here:

# Status

## Current state

Brief summary of where the project stands.

## Recent changes

- What changed recently in the knowledge base

## Open questions

- Unresolved questions worth surfacing

5. Add cross-links

In every article mentioned by or related to the changed articles, add a relative markdown link in the "See also" section if not already present. Links are bidirectional — if A references B, B should reference A.

Use standard markdown links with relative paths:

- [Article Title](../Folder/Article.md) — why it's related

6. Record provenance (optional)

If the project has prompt tracking on (a Prompt tracking: **on** line in CLAUDE.md — see the provenance skill), then for each article you newly generated this step:

• Append a ## Provenance section to the article (Intent / Generated / Ledger), mirroring the ## Recover convention.
• Append an entry to the Wiki/Prompts.md ledger.

When tracking is off (default), skip this entirely.

7. Record to the scientific journal (optional)

If the project's scientific journal is on (a Scientific journal: **on** line in CLAUDE.md — see the journal skill), also append the newly established definition/theorem/claim to Journal/ as a dated def/thm/rem/claim entry, citing any resource used. The Wiki gets the deduplicated, timeless article; the journal gets the dated, cited record of learning it. When off, skip.

What NOT to do

• Do not ask the user for permission to update wiki prose
• Do not create articles for trivial changes (typo fixes, formatting)
• Do not duplicate information across articles — cross-reference instead
• Do not add status headers to articles (that's what Status.md is for)
• Do not write in first person — write in neutral encyclopedic tone