Generates a static HTML site from aiwf planning entities with epic, milestone, and status pages.
npx skills add https://github.com/23min/aiwf --skill aiwf-render-23min
Please help me install this Agent Skill. Skill: aiwf-render Source: https://github.com/23min/aiwf/tree/main/internal/skills/embedded/aiwf-render Command: npx skills add https://github.com/23min/aiwf --skill aiwf-render-23min
aiwf render --format=html to produce a self-contained site with an epic index, per-epic and per-milestone detail pages, and a status page, all sharing one embedded stylesheet with no JavaScript or runtime dependencies. - Area grouping and priority badges: Partitions epics by declared areas in aiwf.yaml and renders priority pill badges for gaps and decisions carrying a priority value. - Deterministic, read-only output: Re-running into the same output directory produces byte-identical files, emits a JSON envelope for CI scripts, and never creates commits. - Use Case: A team lead asks to publish the project status page before a review meeting; the skill renders the full governance site into site/ and the lead opens index.html or deploys it via GitHub Pages. ## Quick Start Ask the assistant to render the governance HTML site with aiwf render and then open the generated index.html in a browser.High-intent search queries and answers about installing and using this skill.
Run `aiwf render --format=html` to generate a static site containing index.html, one page per epic and milestone, status.html, and a shared stylesheet. Use `--out <dir>` to override the default output directory from aiwf.yaml.
The HTML format produces a full static site with per-entity pages and a status view, while `aiwf render roadmap` generates a markdown ROADMAP.md with an epics and milestones table. Both are render subcommands but target different surfaces.
No. The renderer ships a single embedded stylesheet and produces pages with no JavaScript, no runtime, and no external assets. Milestone tab navigation uses `:target`-driven CSS so per-tab URLs remain bookmarkable.
Yes. Set `commit_output: true` under the html block in aiwf.yaml and re-run `aiwf update` to remove the gitignore entry. By default the output directory is gitignored and most projects publish via CI instead.
The renderer is a pure projection of the planning tree, so missing content usually indicates validation findings. Run `aiwf check` first to surface reference, status, or frontmatter problems before investigating the render itself.
gmaiarvianaConsolidate multi-epic milestone outputs into a single review-ready PR body.
Tobbe3108Automate static site deployment to GitHub Pages via gh-pages and CI/CD workflows.
mrgeoffrichMerge reviewed GitHub pull requests and update issue statuses.
huidgeConvert a Markdown directory into a static website with a grouped sidebar.