Verify Jira and Confluence credentials and show the resolved configuration (base URLs, deployment flavour, discovered story points field, defaults). Run this first on a new instance.

List sprints on a board so you can pick sprint ids. state is one of active, closed, future (comma-separate for several).

Issues in a sprint, optionally filtered by status name (e.g. 'Needs Refinement') or status category (new/indeterminate/done). Returns key, summary, assignee, story points and status. Set publish=true to write the result to Confluence.

Multi-sprint rollup grouped by developer (2-5 sprints is the useful range). Uses the Jira changelog, so time-in-status, cycle time and lead time are real, not inferred from current status. One flat table with developer as a column, so it can be sorted and filtered.

Weekly refinement readiness report: stories missing an estimate or missing DOR/DOD labels, plus a suggested attendee list for the refinement meeting. scope is 'backlog' (board backlog) or 'sprint'. checks defaults to estimate,dor,dod — add 'description' to also flag stories with no description.

Create or overwrite a Confluence page. body must be Confluence storage format (XHTML) — pass the confluence value from a report, or your own markup. Matching an existing page by title updates it.

Report what this Confluence instance supports for interactive tables: deployment flavour and whether the Table Filter, Charts & Spreadsheet app is installed. Use before choosing table_style.