Synthesizing cc bigpicture
Skill qte77/claude-code-plugins/plugins/cc-meta/skills/synthesizing-cc-bigpicture
A Claude Code plugin marketplace providing skills, rules, and scripts extracted from a production development workflow.
npx -y skills add qte77/claude-code-plugins --skill synthesizing-cc-bigpictureAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Synthesizes a living big-picture meta-plan from Claude Code sessions, plans, tasks, and team communications. Use when orienting across projects, assessing reasoning modes, or creating a plan-to-plan overview.
SKILL.md
5.6 KB, as published. Nobody here has run it
Big-Picture Synthesis
Target: $ARGUMENTS
Synthesizes a plan to plan — an overarching view across all Claude Code artifacts. A reasoning tool that connects sessions, plans, tasks, and memories into a coherent narrative of what you're working on, why, and where you're headed.
Arguments
| Position | Name | Required | Default | Description |
|---|---|---|---|---|
| 1 | project-name | no | all projects | Filter to a single project (substring, case-insensitive). Use all for all. |
| 2 | time-range | no | all time | E.g. 7d, 30d, this-week. |
| 3 | output-path | no | auto | Where to write output. |
Default output path:
project-nameset:<decoded-project-path>/docs/bigpicture.mdallor omitted:~/.claude/bigpicture.md- Explicit
output-path: overrides both.
Project matching: Matched against decoded ~/.claude/projects/<encoded-path>/
directories (- → / in encoding). Substring match on any path segment.
Examples:
/synthesizing-cc-bigpicture # All → ~/.claude/bigpicture.md
/synthesizing-cc-bigpicture Agents-eval # Single → project docs/
/synthesizing-cc-bigpicture Agents-eval 7d # Single, last 7 days
/synthesizing-cc-bigpicture all 30d ./bigpicture.md # All, 30 days, custom path
When to Use
- Starting a work session — orient across projects
- Planning what to work on next — strategic prioritization
- Sprint/week boundary — maintain the meta-plan
- Feeling stuck — surface current reasoning mode and whether a shift is needed
Do Not Use
- Searching a specific past conversation (use
/resumeor/history) - Per-session context (session-memory does this automatically)
- Real-time usage monitoring (use
/insights)
Project Filtering
When project-name is set (not all), ALL data collection and output must
respect the filter. Apply these rules once, consistently:
- Session allowlist: From
history.jsonl, collectsessionIdvalues whoseprojectfield matches (case-insensitive). - Project dirs: Filter
~/.claude/projects/*/to matching decoded paths. - Plans: Content-based — include only plans mentioning the project name.
- Tasks: Match task dir names against session allowlist (UUIDs) or filtered team names.
- Teams: Include only teams whose
config.jsonreferences the project name. - Session .jsonl: Only read files whose UUID is in the session allowlist.
- Output: Every section scoped to filtered data only. Exception: "Cross-Project Connections" may reference other projects as outbound links.
Workflow
-
Parse arguments — Apply defaults per Arguments table. Resolve output path.
-
Check existing — If bigpicture.md exists at output path, load for incremental update (preserve structure, refresh content).
-
Discover & filter projects — Glob
~/.claude/projects/*/. Decode paths. Apply project filter if set. Build session allowlist fromhistory.jsonl. -
Progressive retrieval — Escalate through tiers, stop when every output section has concrete evidence. See
references/progressive-retrieval.mdfor tier definitions, cost estimates, and the escalation rule. Start at Tier 1 (metadata-only). -
Collect signals — Following the progressive retrieval tiers, collect signals starting from Tier 1. See
references/cc-data-sources.mdfor the full data source layout. Walk these in order (sequential, metadata-first, no subagents):stats-cache.json,history.jsonl, project memory, plans, tasks, teams- Session metadata (first+last 5 lines of each
.jsonl) - Session summaries (skip if directory absent)
- Subagent transcripts (first+last 5 lines, cap 10 most recent by mtime)
- Project docs (
CHANGELOG.md,AGENT_REQUESTS.md)
-
Classify reasoning modes per work stream — diverge/converge and strategic/tactical. See
references/reasoning-modes.mdfor axis definitions, signals, and alert conditions. -
Synthesize — Group by project → time clusters. Link plans↔sessions↔tasks. Surface blockers, trajectory, recurring themes, cross-project connections.
-
Output using the template in
references/output-template.md. Write to output path.
Common Pitfalls
- Data dump: If output exceeds ~200 lines, raise abstraction. Interpret, don't list.
- Reading full transcripts: Use
history.jsonl+ first/last lines only. - False mode classification: Reasoning modes are heuristic signals, not verdicts.
- Spawning subagents: Don't. Sequential within fork context is sufficient.
Quality Check
- Correct > Complete > Minimal (ACE-FCA)
- ~100-200 lines output
- Every claim traces to a specific CC artifact
- Incremental update preserves structure, refreshes content
References
references/progressive-retrieval.md— tier escalation rule and cost estimatesreferences/cc-data-sources.md— full~/.claude/directory layoutreferences/cc-entry-types.md— JSONL session entry type taxonomyreferences/reasoning-modes.md— diverge/converge and strategic/tactical axesreferences/output-template.md— standard output format