Wiki generation

Read a repository, then produce a set of interconnected documentation pages that explain what the code does and how it fits together. The output is a droid-wiki/ directory of markdown files, uploaded to Factory via droid wiki-upload.

1. Survey the repository

Before writing anything, build a mental model of the codebase. The survey has two passes: a structural scan and a deep code scan.

Pass 1: Structural scan

Read these files (when they exist):

• README.md, AGENTS.md, CONTRIBUTING.md — project intent and conventions
• package.json, Cargo.toml, go.mod, pyproject.toml — dependencies and scripts
• docs/ directory — existing documentation
• Entry points (src/index.ts, main.go, app.py, etc.) — how the application starts
• CI/CD config (.github/workflows/, .gitlab-ci.yml, Jenkinsfile, azure-pipelines.yml, etc.)
• Build tool config (webpack.config.*, vite.config.*, Makefile, build/, Gulpfile.*, etc.)
• Lint/quality config (eslint.config.*, custom lint plugins, rustfmt.toml, .golangci.yml, etc.)