What problem does it solve? Project knowledge accumulates across PM artefacts — context files, epics, features, stories, and ADRs — but there is no coherent, shareable documentation set synthesised from it. This Skill reads those accumulated sources and authors a default five-document markdown set into the documentation/ folder, eliminating a separate manual doc-writing pass. ## Core Features & Use Cases - Five-document authoring: Writes overview.md, getting-started.md, architecture.md, decisions.md, and features.md into documentation/, each with a dedicated authoring guide. - Source-grounded content: Reads PROJECT-CONTEXT.md, epics, features, stories, ADRs, and the codebase, marking gaps as "not yet documented" instead of inventing facts. - Machine-checkable source anchors: Appends a mandatory anchor block (files, scripts, ADRs, commands) to each document and stamps generated_at via the wiki-anchor-stamp.js script so a board can verify document freshness. - Use Case: After several sprints of PM artefacts have accumulated, invoke /tandem:document to produce a complete project wiki — overview, setup guide, architecture, ADR digest, and feature reference — then render it with npm run pm:docs. ## Quick Start Ask the assistant to generate the project documentation set from the existing PM artefacts using the document skill.