document

Invoke the document skill on the package root; it classifies the archetype, builds an evidence map from exports and source modules, then writes docs/architecture/<slug>.md with module topology, data flow, and invariants sections. Every claim is verified against the actual code before drafting.

Run the document skill against the package; it re-derives the evidence map from current metadata, exports, scripts, and tests, then integrates updates into the existing README sections while preserving the document's voice. Unsupported or stale claims are removed during the audit pass.

No. The skill explicitly rejects product specifications and Notion documentation, routing those to specification skills instead. It owns only package readme.md content and durable docs/architecture/*.md artifacts.

An architecture doc is created when explicitly requested or when the package has multiple entry points, cross-process data flow, meaningful dependency layering, or at least three cooperating components unclear from the README. Simple packages skip it via --no-architecture or --readme-only.

Yes. It resolves the target package from the working directory, an explicit --project flag, or the nearest manifest, and documents only the selected package unless the selector is the workspace root. Monorepo architecture can be split into per-subsystem documents.

It never invents API behavior: every documented export, command, path, and dependency must trace to package metadata, source, or tests. If evidence is missing or the source is unreadable, it reports the gap instead of fabricating content.