project-wiki

Ingest documents to synthesize and update wiki pages in docs/src/wiki.

Updated Mar 31, 2026

Search Tags:#documentation #collaboration #memory #ingestion #knowledge #wiki #overview

Ready to run

npx skills add https://github.com/GGEdu/claude-god-mode-template --skill project-wiki-ggedu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: project-wiki
Source: https://github.com/GGEdu/claude-god-mode-template/tree/main/skills/project-wiki
Command: npx skills add https://github.com/GGEdu/claude-god-mode-template --skill project-wiki-ggedu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The project knowledge about the codebase, decisions, and processes is scattered across conversations and documents. This skill preserves a persistent, team-visible wiki in docs/src/wiki that grows with ingested documents and session decisions, ensuring long-term accessibility beyond ephemeral memory.

Core Features & Use Cases

Create and maintain a persistent wiki under docs/src/wiki that captures sources, concepts, decisions, entities, and analyses.
Ingest documents to automatically synthesize and update wiki pages, glossaries, and overviews.
Serve as a central reference during project work, enabling quick retrieval of architectural decisions and domain terms.

Quick Start

Initialize the wiki and start ingesting documents to build a persistent project knowledge base.

Frequently Asked Questions about project-wiki

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I create a persistent project wiki for my team's codebase documentation?▼

You can create a persistent project wiki by initializing a docs/src/wiki directory to capture sources, concepts, decisions, and analyses. This establishes a team-visible knowledge base that grows with ingested documents and session decisions.

How do I automatically synthesize glossaries and overview pages from ingested documents?▼

Automatically synthesizing glossaries and overviews works by ingesting documents into the wiki system, which then updates pages with domain terms and architectural decisions. This ensures long-term accessibility beyond ephemeral memory.

What is the best way to preserve architectural decisions and domain terms for long-term retrieval?▼

Preserving architectural decisions and domain terms is best achieved by maintaining a persistent wiki that integrates glossary and overview updates. It serves as a central reference during project work, enabling quick retrieval for collaborators.

Can I use a wiki to ingest and organize scattered codebase conversations and documents?▼

Yes, you can ingest scattered codebase conversations and documents into a wiki to organize project knowledge. The system applies during active project work to synthesize pages for sources, concepts, decisions, and analyses automatically.

Does the wiki support workflow-driven page creation and editing during active development?▼

Yes, the wiki supports workflow-driven page creation and editing during active development. It ensures a consistent docs/src/wiki structure and provides fast retrieval of synthesized project knowledge for all collaborators.

Why should I maintain a project wiki instead of relying on ephemeral memory from chat sessions?▼

Maintaining a project wiki prevents knowledge loss because it preserves a team-visible record in docs/src/wiki that grows with ingested documents. Ephemeral memory from chat sessions lacks long-term accessibility for future collaborators.