generate-site-overview

Generate project handoff documentation by mapping a defined strategy blueprint to your current codebase, producing a concise site overview that cites source docs, code references, and deployment status for clear team transitions.

The best way to keep site overview docs updated is to regenerate the overview after milestones, reconciling the latest strategy and codebase state to output a structured YAML frontmatter file with a maintenance plan.

No, this site overview generation process requires a marketing-site project with a defined strategy blueprint and a real codebase to map strategy to implementation and document project status accurately.

Yes, the generated site overview includes component and page documentation, mapping the current build state while detailing project status and outlining next steps for the development team.

Strategy-to-implementation mapping for codebase handoff documentation works by reconciling high-level strategy docs with the actual build, producing a structured overview with YAML frontmatter that cites source documents and code references.

Limitations when regenerating site overview docs include the reliance on an existing strategy blueprint and real codebase; without these inputs, the skill cannot produce an accurate handoff summary or maintenance plan.