jira-issue-createlisted

# Jira Issue Creation Create one Jira issue or a batch of issues with three plain ADF sections: Context, Acceptance criteria, and Engineering notes. Render each section title as a heading and do not wrap sections in panels. ## Inputs Extract these values from the request: - `project` (required): Jira project key, such as `DXAI`. Ask if missing. - `parent` (optional): Epic or parent key for the created issues. - `type` (optional): Work item type. Default to `Task`. - `content source` (optional): Local document, pasted text, or prose describing the issue or issues. For a batch, identify what defines one issue. ## Workflow ### 1. Check authentication Run `acli auth status`. If authentication is missing, stop and ask the user to run `acli auth login`. Suggest `! acli auth login` when an interactive command is needed. Continue only when the output shows `✓ Authenticated` for the expected site. ### 2. Gather content - Read any referenced source document. - When a parent is given, fetch it for context and tone with `acli jira workitem view <EPIC> --json`. - Draft these sections for each issue: - **Context:** Explain why the issue exists, what it covers, and its role in the larger effort. - **Acceptance criteria:** Use an ordered list. Start each item with a bold lead phrase followed by one sentence, such as "**Pilot flows run:** ...". - **Engineering notes:** Use bullets with bold labels for risks, constraints, useful details, and relevant links. Gloss bare identifi