Support for Repo Wiki (i.e. Spec-Driven Development)

[wheelo]

Hi, these days Spec First(or Spec driven) development workflows are becoming increasingly popular. Since graph code indexing has been proposed this week, Repo Wiki could thus be a nice feature. Tools like VibeCoding and spec-generation agents demonstrate that AI and code need a persistent middle layer—a structured knowledge layer that lives between prompts and source code.

Roo Code generates specs as part of the coding loop, but these specs are ephemeral: they are created, used, and discarded. What’s missing is a persistent, code-aware knowledge base inside the repository — Repo Wiki.

Proposed Feature: Roo Code Repo Wiki

A Repo Wiki would act as a structured engineering knowledge layer automatically generated from the codebase. This mirrors solutions like:

• Qoder Repo Wiki — https://qoder.com/blog/repo-wiki-surfacing-implicit-knowledge
• Deep Wiki — https://deepwiki.com/
• Windsurf DeepWiki — https://docs.windsurf.com/windsurf/deepwiki
• Cursor Notebooks / Specs

These systems surface implicit knowledge hidden inside the repository and turn it into explicit documentation that AI agents—and humans—can continuously rely on.

Why This Matters

Currently, AI coding produces “throwaway” specs. But we need a long-lived, evolving knowledge layer that acts like:

• documentation
• an architecture map
• a dependency graph
• implicit engineering knowledge
• a shared source of truth for all agents and contributors

This is similar to how assembly sits between high-level code and machine instructions:
Repo Wiki becomes the intermediate representation of software for AI coding.

What a Repo Wiki Could Provide

1. Automatically-generated engineering knowledge base

• project structure & architecture
• dependency diagrams / call graphs
• module descriptions
• API documentation
• cross-file relationships
• change-aware updates

2. Better agent collaboration

A clear, structured engineering Wiki helps multi-agent systems understand the codebase and produce more accurate answers and edits.

3. Faster onboarding

Developers can quickly understand the project through an auto-generated wiki, instead of starting from scratch.

4. Continuous synchronization

As the code changes, the wiki updates—keeping documentation always aligned with the repository.

Technical Direction (Proposal)

The Repo Wiki could be built using the some Agent SDK, leveraging Roo Code’s existing multi-agent system as its runtime, producing a main Spec folder which includes Wikis' markdown, something like ARCHITECTURE.md or DEVELOPMENT_GUIDE.md.

most importantly, Wiki should be servered as a universal environment context throughout lifecycle(some kind of long memory). If possible, I'd be happy to help provide a code implementation via a pull request.

Code Graph Integration

Roo Code recently added (or proposed) Code Graph support.
This makes the Repo Wiki especially timely:

• Code Graph already extracts structural relationships.
• Repo Wiki can build on top of this to generate Wiki pages.

Example Flow

• Index code repository
• Multi-agent system analyzes structure
• Toolbox (read file, analyze code, list directory…) builds graph
• Agents generate wiki documentation
• Wiki stored in repo (local branch → remote branch with wiki)
• Multiple users sync via git push/pull

How is Repo Wiki generated：