AI Agent Workflow Collection

Transfers a completed tech breakdown document into Jira tickets. Reads the breakdown's implementation tasks and AI Context section, checks for existing child tickets on the Epic, fills them in or creates new ones. Produces concrete, actionable descriptions from the breakdown: affected files, real function names, code patterns. Wires dependencies as Jira Blocks links rather than description prose. Use after finishing a breakdown with /tech-breakdown. Invoke with a Confluence page link (e.g. /breakdown-to-tickets https://...).

Edit a Confluence page while preserving inline-comment anchors, layouts, and other ADF features that the regular MCP updateConfluencePage tool would strip via markdown round-trip. Use this skill when (a) the page has open inline comments that need to stay attached after the edit, (b) the edit is small and you want to avoid passing a huge ADF body as a tool argument, or (c) the user explicitly mentions preserving anchors. Wraps a local CLI tool confluence-edit (in ~/.local/bin).

Turns a spike or tech breakdown ticket into a complete, actionable breakdown document. Gathers context from Confluence, Jira, and code, resolves open design questions one-by-one with the user, then writes a practical implementation guide with numbered tasks and code examples. Use when you have rough notes, a PoC, and unanswered design questions that need to become concrete tasks. Also handles resumption: invoke with a Confluence page link (e.g. /tech-breakdown https://...) to resume work on an existing breakdown.