You are a senior automation engineer. Build the following optimized workflow.

# Write the weekly status round-up

Spion recorded this as a manual browser process (8 steps, ~20 min, weekly) and redesigned it as a consolidated automation (4 steps). Build the OPTIMIZED workflow below, not a replay of the manual clicks.

Overview: Pull this week's items from Jira, Asana, and Linear, write the what-moved and what's-blocked summary, and post it.
Tools: Jira, Asana, Linear, Claude
Trigger: Weekly schedule (Every Friday 16:00).
Efficiency target: 8 manual steps down to 4 (50% fewer), saving ~20 min per run, about 17 hours a year.

## Optimized workflow steps

1. [Jira] Pull this week
   What: Items closed, in-progress, and blocked this week (repeat for Asana and Linear).
2. [Claude] Write the summary (added by Spion: net-new value)
   What: Group by team and status, de-duplicate cross-tool items, and write what shipped, what's at risk, and what's blocked and on whom.
   Why: the synthesis is the value; the raw lists are not.
3. [Claude] Flag stale blockers
   What: Call out every blocked item older than five days as needing escalation.
4. [Slack] Post round-up
   What: Post to #weekly-status with a one-line headline per team above the detail.

## Original manual process (reference only, do not replicate)
1. Open Jira, Asana, Linear
2. Note what closed
3. Note what's in progress
4. Note what's blocked
5. Write the summary
6. Post it

## What I need from you
1. Build the optimized workflow exactly as designed above: production-ready code (Python or JavaScript) or a platform recipe (Workato, Make, Zapier, or n8n), whichever fits these tools best.
2. Preserve the consolidation. Do not expand it back into the manual click-by-click process.
3. Recommend the right trigger and cadence (schedule, webhook, or event). If it recurs, state the exact schedule.
4. Define the data contract for each step: the exact input fields it reads, the output fields it produces, and how fields map between tools.
5. Specify every authentication requirement: which services need OAuth, API keys, or service accounts, and the exact scopes.
6. Add robust error handling (missing data, auth failures, empty results, rate limits with retries) and make the workflow idempotent so it is safe to re-run.
7. Include a short test plan: a sample input and the expected result, so I can verify it before going live.
8. Finish with exact, copy-and-paste setup instructions so I can run it today.