Skip to Content
Canonical topic map (one primary doc each)

Canonical topic map (one primary doc each)

Use this table to find the single user-facing home for a topic. docs/phases/** may repeat planning context; product docs should link here instead of duplicating long specs.

TopicCanonical doc
CLI entry, global flagscli/README.md
JSON / --json envelopejson/README.md
Issue codes (issues[])json/issue-codes.md
Programmatic API vs CLI JSONjson/programmatic.md
--json + long-running commandsbehavior/json-long.md
Exports / @zamdevio/i18nprune/coreexports/README.md · exports/core.md
Command orchestration (vs core)commands/orchestration/README.md
CLI prompts (core/ask, per-command)cli/prompts/README.md
Translator pipelinetranslator/README.md
Live progress (stderr)progress/README.md
User loader & config (future)patching/loader.md
Opt-in patchingpatching/README.md
Repo / package layoutarchitecture/tree/README.md
Architecture overviewarchitecture/README.md
ADRsarchitecture/decisions/
Edge cases (solved)edge-cases/README.md
Maintainer phasesphases/README.md
Agent onboardingagents/README.md
Why the project exists (backstory)origin/README.md
Cursor / how the repo was builtcursor/README.md
Launch & adoption (positioning, checklist)launch/README.md
Pre-release doc sweeptemp/final.md
Session scratch (gitignored)agents/temp-notes.mddocs/phases/temp/

When you add a major topic, either extend an existing row or add one row and link it from docs/README.md.