← ClaudeAtlas

summarize-ideaslisted

Use when the user asks for a recap, status readout, or check-in across Ideate ideas (a logical work item; "session" is one facet of an idea, not the unit). Scope is the local Ideate workspace exposed by the ideate MCP. Use `work-idea` instead when the user wants to focus on or switch into a single idea.
paultyng/ideate · ★ 7 · AI & Automation · score 68
Install: claude install-skill paultyng/ideate
# summarize-ideas Workflow for producing a terse, idea-centric readout of every in-flight idea in the workspace, then a consolidated `## Next` block of high-impact actions for juggling multiple ideas at once. The unit of work is the **idea**. Sessions are one facet ("what's running on this idea"); backlog state is the other primary signal ("what's queued / blocked / mid-flight"). The recap reads by idea. ## Steps 1. **One batched call.** `ideate:list_ideas` with `include_output_lines: 40`. That single call returns every non-archived idea's `summary`, `backlog` counts + in-progress titles, `sessions.running` and `sessions.dormant` lists, `last_activity_at`, AND the most-recent running session's last 40 lines of screen — every signal this skill needs. Do **not** loop over the result calling `list_backlog_by_slug` / `get_session_output` / `get_idea_by_slug` per idea. One batched call covers it. 2. **Filter and sort.** Default: keep ideas with any signal — running session, dormant session, or non-zero `backlog.open + in_progress`. Drop ideas with neither (they're parked; the user hasn't asked for them). Sort by `last_activity_at` descending so the most-touched idea leads. If the user named a filter (`s:paused`, etc.), honor it. 3. **Pick 1–3 high-impact next actions across the whole readout.** After the per-idea sections, surface a consolidated `## Next` block. High impact, in priority order: - **Awaiting input.** Sessions i