Read-only review brief for one Jira issue. It reads issue details, comments, worklogs, and available transitions through recued-core.jira, then asks the AI summarizer for status, blockers, owners, and next actions. It never comments, transitions, assigns, edits, deletes, attaches files, or calls arbitrary Jira endpoints.

How it works 16 steps

Inspect the data fetches, transforms, gates, and output this recipe runs.

Process (16 steps)

■ issue ?

■ comments_raw ?

■ worklogs_raw ?

■ transitions_raw ?

■ comments default

Apply default

■ worklogs default

Apply default

■ transitions default

Apply default

■ comment_rows slice

Take a subset of

■ worklog_rows slice

Take a subset of

■ comment_count count

Count items in comments

■ worklog_count count

Count items in worklogs

■ transition_count count

Count items in transitions

■ summarize ?

■ comment_table to_table

Format results as a data table

■ worklog_table to_table

Format results as a data table

■ card to_summary

Format results as a summary card

Settings 6 configurable

Configurable at install. Defaults shown — change them anytime in Recued.

focus setting = Summarize current status, blockers, recent discussion, owner expectations, available next transitions, and the next concrete action.

cloud id setting =

atlassian setting =

row limit setting = 25

max length setting = 900

issue id or key setting =