rai-epic-docs

Generate and publish epic documentation sections to Confluence.

71|8|Updated Feb 13, 2026
One-click install
npx skills add https://github.com/humansys/raise --skill rai-epic-docs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rai-epic-docs
Source: https://github.com/humansys/raise/tree/main/packages/raise-cli/src/raise_cli/skills_base/rai-epic-docs
Command: npx skills add https://github.com/humansys/raise --skill rai-epic-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill addresses the lack of centralized, governance-driven developer documentation for completed epics, ensuring future teams can understand decisions, architecture, and recovery steps without wading through code.

Core Features & Use Cases

  • Automatically generate Worked Example, Extension Guide, Data Flow, Invariants & Contracts, and Failure Mode Catalog sections from epic artifacts.
  • Publish to Confluence for stakeholder visibility and HITL review before epic close.
  • Provide a repeatable, audit-friendly pattern that helps teams establish documentation gates and traceability.

Quick Start

Install RaiSE's epic documentation workflow and run it on a completed epic to produce and publish Confluence pages.

Frequently Asked Questions about rai-epic-docs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate epic documentation for Confluence?

Automating epic documentation for Confluence requires extracting epic artifacts to generate structured sections like Worked Example and Failure Mode Catalog, then publishing them directly to Confluence for stakeholder visibility and human-in-the-loop review.

What sections are needed for governance-ready developer documentation?

Governance-ready developer documentation requires a Worked Example, Extension Guide, Data Flow, Invariants & Contracts, and a Failure Mode Catalog to capture decisions, architecture, and recovery steps for future teams.

How does a human-in-the-loop review workflow work for epic close?

A human-in-the-loop review workflow for epic close publishes generated documentation to Confluence, allowing stakeholders to review the structured sections and approve governance gating before the epic is officially closed.

Can I use Confluence to enforce documentation gates for completed epics?

Yes, you can use Confluence to enforce documentation gates by automating the collection of epic artifacts into structured pages, establishing a repeatable, audit-friendly pattern for traceability and review before epic close.

What is the best way to capture failure modes and data flow for completed epics?

The best way to capture failure modes and data flow is to automate the extraction of epic artifacts into a standardized Failure Mode Catalog and Data Flow section, publishing the results to Confluence for governance gating.

Do I need completed RaiSE epics to generate governance documentation?

Yes, you need completed RaiSE epics, as the documentation generation applies to finished epics to capture architectural decisions, invariants, and recovery steps for review and governance gating.