Read-only incident command brief for one Rootly incident. It reads the incident, timeline events, action items, services, teams, and users through recued-core.rootly, then asks the AI summarizer for current state, impact, ownership, timeline signal, open work, risks, and next steps. It never creates or edits incidents, action items, alerts, schedules, escalation policies, users, API keys, or arbitrary Rootly API routes.

How it works 20 steps

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

Process (20 steps)

■ incident_key trim

Trim whitespace from setting incident id

■ incident ?

■ timeline_raw ?

■ action_items_raw ?

■ services_raw ?

■ teams_raw ?

■ users_raw ?

■ timeline default

Apply default

■ action_items default

Apply default

■ services default

Apply default

■ teams default

Apply default

■ users default

Apply default

■ timeline_count count

Count items in timeline

■ action_item_count count

Count items in action items

■ summarize ?

■ timeline_rows slice

Take a subset of

■ action_item_rows slice

Take a subset of

■ timeline_table to_table

Format results as a data table

■ action_item_table to_table

Format results as a data table

■ card to_summary

Format results as a summary card

Settings 5 configurable

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

focus setting = Summarize the Rootly incident for current status, severity, impact, ownership, recent timeline signal, open action items, escalation risk, and concrete next steps. Do not invent facts outside the Rootly data.

rootly setting =

row limit setting = 12

max length setting = 900

incident id setting =