refresh-human-docs

You can generate human-readable documentation by reading ops/goals.md, notes/index.md, topic maps, ROADMAP*.md, and IMPLEMENTATION_PROGRESS.md to synthesize up-to-date docs/human/PROJECTS.md and docs/human/DECISIONS.md with timestamps.

Regenerate project dashboards and decision logs by synthesizing ROADMAP*.md and IMPLEMENTATION_PROGRESS.md files, overwriting docs/human/PROJECTS.md and docs/human/DECISIONS.md with current timestamps to reflect the latest knowledge graph state.

Yes, regenerating decision documentation respects legacy ADR numbering when mapping decisions to docs/human/DECISIONS.md, ensuring existing architecture decision records maintain their original identifiers during the overwrite process.

Automate docs generation by reading active goals from ops/goals.md and all topic maps listed in notes/index.md, then synthesizing these inputs into structured human-readable project and decision documents with generated timestamps.

No external dependencies are required. The regeneration process reads existing project files including ops/goals.md, notes/index.md, topic maps, ROADMAP*.md, and IMPLEMENTATION_PROGRESS.md and overwrites target docs in docs/human/ directly.

You need to regenerate human docs when project goals, roadmap entries, or implementation progress change, ensuring docs/human/PROJECTS.md and docs/human/DECISIONS.md accurately reflect the current knowledge graph and operational state.