Linear issue and project brief
Read-only review brief for one Linear issue and project. It reads issue details, project details, issue comments, project updates, active cycle context, and labels through recued-core.linear, then asks the AI summarizer for status, blockers, owners, stale signals, and next actions. It never creates, updates, moves, comments on, labels, archives, deletes, or calls arbitrary Linear GraphQL.
How it works
Inspect the data fetches, transforms, gates, and output this recipe runs.
Process (20 steps)
issue
?
project
?
comments_raw
?
project_updates_raw
?
active_cycles_raw
?
labels_raw
?
comments
default
Apply default
project_updates
default
Apply default
active_cycles
default
Apply default
labels
default
Apply default
comment_rows
slice
Take a subset of
project_update_rows
slice
Take a subset of
comment_count
count
Count items in comments
project_update_count
count
Count items in project updates
cycle_count
count
Count items in active cycles
label_count
count
Count items in labels
summarize
?
comment_table
to_table
Format results as a data table
project_update_table
to_table
Format results as a data table
card
to_summary
Format results as a summary card
Settings
Configurable at install. Defaults shown — change them anytime in Recued.
focus
setting
=
Summarize current issue status, blockers, recent discussion, project health, owner expectations, stale signals, and the next concrete action.
linear
setting
=
issue id
setting
=
row limit
setting
=
25
max length
setting
=
900
project id
setting
=
Trust & control
What installing this recipe would let it do. Recued grants these permissions at install — review them there before approving.