Generate wiki documentation from spec files and publish to ADO Wiki or Confluence.
npx skills add https://github.com/easingthemes/dx-aem-flow --skill dx-doc-gen
Please help me install this Agent Skill. Skill: dx-doc-gen Source: https://github.com/easingthemes/dx-aem-flow/tree/main/plugins/dx-core/skills/dx-doc-gen Command: npx skills add https://github.com/easingthemes/dx-aem-flow --skill dx-doc-gen
Generate wiki-style documentation from completed spec files and publish it to the correct wiki (ADO Wiki or Confluence) depending on provider config. This is intended to be used as the final step after implementation and can be invoked automatically by workflow triggers.
Run the skill with your work item ID to generate the wiki page from completed spec files and publish it to the configured wiki.
High-intent search queries and answers about installing and using this skill.
Automate wiki documentation by reading completed spec artifacts like raw-story.md and implement.md, then publishing the assembled content to ADO Wiki or Confluence. This config-driven process aligns pages with sprint structure and links back to original work items.
Yes, you can publish spec documentation to Confluence or ADO Wiki. The target wiki is determined automatically by your tracker.provider configuration, allowing multi-provider posting with per-page creation aligned to sprint structures.
Generate traceable sprint documentation by assembling cohesive wiki pages from completed spec files including research.md, explain.md, and share-plan.md. This captures decisions, design, and usage across sprint-based pages for up-to-date project tracking.
Required spec artifacts include raw-story.md, explain.md, share-plan.md, implement.md, and research.md. These sprint artifacts are read and assembled into a cohesive wiki page that captures project decisions, design, and usage information.
Yes, the documentation automation supports QA integration and authoring-demo templates for AEM projects. It meets requirements for config-driven publishing, sprint handling, and linking generated wiki content back to the original work item.
Generate wiki documentation as the final step after implementation is complete. It can be invoked automatically by workflow triggers using your work item ID to publish finalized spec content to the configured wiki.
easingthemesResolve plan validation risks by researching codebase patterns and updating implement.md with fixes.
easingthemesGenerate wiki-ready documentation from ADO work items, PRs, and code changes.
easingthemesAutomates categorized PR review reports and posts them to ADO Wiki or Confluence.
co-cddoGenerate sprint-status.yaml from Markdown epic files and story data.
