Inspect a real repository and generate or refresh a managed project docs bundle from actual files. Use when users ask to create, rebuild, or update `docs/project-docs` documentation such as `README.md`, `PLAN.md`, `LAYOUT.md`, `ARCHITECTURE.md`, `CHANGELOG.md`, or `GUIDE.md`, and also during ongoing work on the current project in the same session when the repo changes and the docs need to be refreshed in parallel from real scripts, manifests, layout, commands, and current state rather than guesses. Requires subagent support for its intended parallel workflow.
Generate and refresh a 6-file managed documentation set under <project-root>/docs/project-docs.
Base every claim on actual inspection of the repository. Do not invent architecture, commands, status, or history.
During ongoing work on the current project in the same session, treat the active repository as the default target unless the user redirects to another repo.
docs/project-docs.Default execution mode is 3 parallel lanes plus one final integration pass.
<project-root>/docs/project-docs.README.md, GUIDE.mdPLAN.md, CHANGELOG.mdLAYOUT.md, ARCHITECTURE.md--targets so each lane only writes its owned files.docs/project-docs.--targets subset.python scripts/project_snapshot.py <project-root> --output <project-root>/docs/project-docs/project_snapshot.json
python scripts/scaffold_docs.py <project-root> --snapshot-file <snapshot.json> --targets README.md,GUIDE.md
python scripts/patch_docs.py <project-root> --snapshot-file <snapshot.json> --targets PLAN.md,CHANGELOG.md
python scripts/patch_docs.py <project-root> --snapshot-file <snapshot.json>
--allow-overwrite-unmanaged only after explicit user approval in the conversation.--allow-delete only after explicit user approval in the conversation.README.mdPLAN.mdLAYOUT.mdARCHITECTURE.mdCHANGELOG.mdGUIDE.mdAll files are managed and include a preserved manual section. Refreshes rewrite managed content and keep the preserved section intact.