/wiki-query answers questions against your compiled wiki. Instead of reading through raw source files, it reads your topic articles — which already synthesize everything known about each subject — and returns a focused answer with citations.
Command
Examples:
/wiki-query what do we know about retention?
/wiki-query what decisions were made about the onboarding flow?
/wiki-query how has our thinking on push notifications evolved?
How it works
- Reads
INDEX.md to see all available topics
- Checks
schema.md for cross-reference rules that might point to related topics
- Identifies 1–3 topic articles most likely to contain the answer
- Reads those articles
- Returns an answer with specific facts, dates, and decisions — cited as
(from: {topic name} > {section})
- If the wiki doesn’t have enough detail, points you to the specific raw source files listed in the article’s Sources section
Answers are kept concise. You get the information you asked for, not a summary of every article that was read.
Filing answers back to the wiki
If your question produces a synthesis that connects information across topics in a useful way — something that isn’t already captured in any single article — the command offers to file it:
“This answer connects information across topics. Want me to file it into the wiki? (y/n)”
If you say yes, the synthesis is appended to the most relevant topic article as a new subsection, marked with the date it was filed. The filing is also logged in compile-log.md.
This means your exploratory questions compound in the knowledge base instead of disappearing when the session ends.
Use /wiki-query for cross-topic synthesis questions — “how do these things relate?”, “what patterns emerge across X and Y?”, “how has our thinking evolved on Z?”. For simple keyword lookups, /wiki-search is faster.
If the wiki hasn’t been compiled yet
Wiki not compiled yet. Run /wiki-compile first, then try your query again.