Feature Briefing Page Generator

Problem

When product and engineering teams explain a feature, context is often scattered across Markdown, tables, and chat notes, making feature boundaries, state transitions, and external-system interactions hard to align quickly.

How It Works

• Input: an existing feature-design Markdown document.
• Output: a single-file HTML briefing page that opens directly in a browser.
• Content: five sections — feature boundary, workflow diagram, state transition diagram, external system interactions, and key rules.
• Diagrams: Mermaid.js charts with fullscreen, zoom, and drag, suitable for meeting presentations.
  It reads diagram conventions before generation and checks Mermaid syntax, node references, and business-scope boundaries before writing the file.

Boundaries

It depends on a reasonably complete design document; if the source lacks role permissions, state transitions, or external interface notes, the output may be incomplete. It is aimed at business explanation, not a replacement for API docs, database design, or acceptance test cases.