Generate a Hugo documentation site from dew workflow artifacts and code.
npx skills add https://github.com/jkerdels/dew-plugin --skill dew-document
Please help me install this Agent Skill. Skill: dew-document Source: https://github.com/jkerdels/dew-plugin/tree/main/skills/dew-document Command: npx skills add https://github.com/jkerdels/dew-plugin --skill dew-document
It converts the output of the dew engineering workflow into a coherent, developer-facing documentation site so external contributors can understand architecture, data flows, and design intent without reading every source file.
Ask for documentation generation for the completed Develop stage, targeting the Hugo site output from the current dew artifacts and repository code.
High-intent search queries and answers about installing and using this skill.
You can generate developer documentation by synthesizing upstream engineering artifacts and implemented code into a Hugo-based site, creating architecture maps and data flow diagrams for external contributors.
Creating Mermaid diagrams for complex data flows is handled automatically during documentation generation, mapping component interactions and interface contracts directly from the synthesized source artifacts.
Documenting architecture boundaries for onboarding is best achieved by generating a Hugo site that explicitly distinguishes between sourced facts and code-inferred details, clarifying component responsibilities and failure modes.
Yes, you can use Hugo to document architecture by processing completed project artifacts and repository code, producing a sectioned site that explains system design philosophy, internal algorithms, and invariants.
Yes, developer documentation generation provides an auditable distinction between sourced facts from design artifacts and code-inferred details extracted from the implemented repository.
You should generate developer documentation when a project has completed implementation and external developers need to understand architecture, data flows, and design intent without reading every source file.
jkerdelsFacilitate structured retrospectives across six dew development workflow stages.
ousiassConvert Markdown specifications into Hugo documentation sites with Hextra theme.
KrystianYCSilvaCreate Markdown documentation with Mermaid diagrams and GFM tables.
plastikawebGenerate Markdown documentation, API references, and architecture guides from codebases.
