Acceptance Criteria Doc Generator

Produce three things for a given Jira epic:

1. A live Confluence page titled <EPIC-KEY> - ACs in the TL1 space, inside the Assets - Acceptance Criteria folder (parentId: 401775165477), on cloud consensyssoftware.atlassian.net.
2. A Jira comment on the epic linking the doc.
3. The AC doc link appended to every child issue's description (stories, tasks, spikes — all children).

Example outputs: ASSETS-3647 - ACs (Market Insights), ASSETS-3645 - ACs (CTA Optimisation).

Inputs

Required: the epic (key or URL). Everything else is optional and should be mined rather than requested:

• Epic description & remote links — often contain the feature flag name, Definition of Done link, PRD, ADR/tech-spec, Figma/Replit links, and a "source epic" (e.g. the Mobile epic a parity feature is ported from). Extract all of these.
• Repositories — if the user names repos, investigate them; if the feature is a port/parity of an existing implementation, the source repo is the primary investigation area even if unnamed.
• PRD / Figma / Replit / ADR — link them in the Documentation table when available. Don't block on missing ones; note the gap to the user in your final summary instead of padding the doc.

Workflow