synthesize
Skill0 starsChanged 3 months agoMITView on GitHub
Synthesize accumulated project artifacts into refined documents
13 other projects use a version of this.
Adopted by
Most recently taken up by
- markusbegerow/board-of-directorstheir own version, first seen Oct 13, 2026
- allemaar/open-skillstheir own version, first seen Oct 13, 2026
- Seanathon/vault-startertheir own version, first seen Sep 28, 2026
- dkpapadopoulos/auto-claude-skillstheir own version, first seen Sep 22, 2026
- iopsystems/skills-mcptheir own version, first seen Aug 24, 2026
- Kastalien-Research/thoughtboxtheir own version, first seen Jul 3, 2026
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- Kastalien-Research/thoughtbox★ 64same name
- tuan3w/obsidian-vault-agent★ 39same name
- allemaar/open-skills★ 15same name
- sparkline-ventures/product-eval★ 15same name
- dkpapadopoulos/auto-claude-skills★ 6same name
- iopsystems/skills-mcp★ 6same name
- markusbegerow/board-of-directors★ 5same name
- jasonmichaelbell78-creator/sonash-v0★ 2same name
- corygabrielsen/skills★ 1same name
- breethomas/bette-os★ 0same name
3 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
Show its rules and text
We split this skill into the rules it gives an agent
37 rules. 0 are common, 4 are distinctive, and 33 are very specific to this project.
0
Common
Most of the 11 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
33
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
If $ARGUMENTS is ? or help: Print a usage block with the following information then stop — do not execute any further steps:
- Distinctive: line 40
If no mode flag is present, print the help text above and stop.
- Very specific: line 41
If --postmortem: set MODE=postmortem.
- Very specific: line 42
If --topic: set MODE=topic.
- Very specific: line 43
If --decisions: set MODE=decisions.
- Very specific: line 44
If --architecture: set MODE=architecture.
- Very specific: line 45
If --all: set MODE=all. No additional arguments required.
- Very specific: line 55
If docs/synthesis/ does not exist, create it.
- Very specific: line 63
Read all .md files in docs/sessions/ excluding _template.md, signals.md, error-log.md, insights-log.md, scratchpad.md, context-snapshot.md, …
- Very specific: line 79
Read docs/sessions/error-log.md.
- Very specific: line 80
If file does not exist: skip silently.
- Very specific: line 81
Add to SOURCES if read.
- Very specific: line 85
Read docs/sessions/signals.md.
- Very specific: line 91
Write a structured postmortem document to OUTPUT_FILE with these sections:
- Very specific: line 110
Search the following directories for files containing QUERY (case-insensitive):
- Very specific: line 124
If no matches found: write a brief note to OUTPUT_FILE stating "No artifacts found matching the query." and stop.
- Distinctive: line 128
Read the matching sections from each file (read the relevant portions, not entire files when they are large).
- Very specific: line 130
Write a structured topic summary document to OUTPUT_FILE with these sections:
- Very specific: line 149
If --since YYYY-MM-DD is set: only include files whose date prefix >= that date.
- Very specific: line 159
Read all .md files in docs/decisions/ (if the directory exists).
- Very specific: line 161
If directory does not exist or is empty: skip silently.
- Very specific: line 162
Add each file to SOURCES if read.
- Very specific: line 166
Write a structured decision log document to OUTPUT_FILE with these sections:
- Very specific: line 182
If directory does not exist or is empty: note "No ADRs found" and continue.
- Very specific: line 187
Read docs/specs/README.md to identify closed specs.
- Very specific: line 189
If no closed specs exist: note "No closed specs found" and continue.
- Very specific: line 194
Read AGENTS.md if it exists.
- Very specific: line 200
Read CLAUDE.md. Extract the "Architecture quick-ref" section and any structural information.
- Very specific: line 205
Write a structured architecture overview document to OUTPUT_FILE with these sections:
- Very specific: line 225
Read the 3 most recent session logs from docs/sessions/ (sorted by filename descending).
- Very specific: line 227
If a single spec ID or concept appears 3+× more than any other, set QUERY=<that-token>.
- Distinctive: line 241
After all four modes have been attempted, print a single summary block:
- Distinctive: line 256
After writing the output file, print:
- Very specific: line 267
If postmortem: "Next: review the postmortem and share with your team.
- Very specific: line 268
If topic: "Next: review the topic summary.
- Very specific: line 269
If decisions: "Next: review the decision log for consistency.
- Very specific: line 270
If architecture: "Next: review the architecture overview for accuracy.
“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<!-- forge:paths-note (Spec 575): process-state paths in this command (docs/specs,
docs/sessions, docs/decisions, docs/research, docs/process-kit, docs/backlog.md) are the
CLASSIC-DEFAULT spellings, not fixed locations. When the project configures forge.paths
(e.g. the `contained` layout), resolve each key before use — bash: `forge_path <key>`
(source ${CLAUDE_PLUGIN_ROOT:-.}/.forge/lib/config.sh, forge_config_load AGENTS.md);
python: `${CLAUDE_PLUGIN_ROOT:-.}/.forge/bin/forge-py .../runtime_config.py path <key>`. -->Framework: FORGE
Model-Tier: sonnet
Synthesize accumulated FORGE artifacts into a refined, actionable document.
Timing guidance: see session-synthesize-evolve-guide for the canonical comparison of
/sessionvs/synthesizevs/evolve— triggers, cadence, automation class.
If $ARGUMENTS is ? or help:
Print a usage block with the following information then stop — do not execute any further steps:
- Command: /synthesize — Knowledge synthesis command (FORGE Spec 106).
- Usage: /synthesize
<mode>[options] - Modes (exactly one required):
- --postmortem: Generate narrative sprint retrospective from recent session logs (use /evolve for process gate reviews)
- --topic
<query>: Summarize all artifacts related to a topic - --decisions [--since YYYY-MM-DD]: Compile decision log from session logs
- --architecture: Draft architecture overview from ADRs, specs, and agent config
- --all: Run all four modes sequentially. For --topic, uses the dominant theme inferred from recent sessions, or falls back to a generic "recent-activity" topic if no theme dominates. Continue-on-error: if any mode fails, the remaining modes still run; the final summary lists per-mode pass/fail and output paths. (Spec 328)
- Options:
- --sessions N: Number of recent sessions to include (postmortem only, default 5)
- --since YYYY-MM-DD: Limit to artifacts on or after this date (decisions mode)
- Output: docs/synthesis/YYYY-MM-DD-
<mode>.md (one file per mode; --all writes four) - Each output includes a Sources section listing every artifact that contributed.
- Reference: docs/specs/106-knowledge-synthesis-command.md
Parse $ARGUMENTS:
- Detect the mode flag:
--postmortem,--topic,--decisions,--architecture,--all. - If no mode flag is present, print the help text above and stop.
- If
--postmortem: setMODE=postmortem. Parse optional--sessions N(default 5). - If
--topic: setMODE=topic. The next argument isQUERY(required — if missing, print help and stop). - If
--decisions: setMODE=decisions. Parse optional--since YYYY-MM-DD. - If
--architecture: setMODE=architecture. - If
--all: setMODE=all. No additional arguments required. Skip directly to Mode E — All modes below.
Set TODAY = current date in YYYY-MM-DD format.
Set OUTPUT_DIR = docs/synthesis.
Set OUTPUT_FILE = docs/synthesis/{TODAY}-{MODE}.md (for topic mode: docs/synthesis/{TODAY}-topic-{QUERY}.md with spaces replaced by hyphens).
[mechanical] Step 1 — Ensure output directory
If docs/synthesis/ does not exist, create it.
Mode A — Postmortem (--postmortem)
[mechanical] Step A1 — Gather session logs
Read all .md files in docs/sessions/ excluding _template.md, signals.md, error-log.md, insights-log.md, scratchpad.md, context-snapshot.md, and registry.md.
Sort by filename date prefix (newest first). Take the most recent N files (where N = --sessions value, default 5).
From each session log, extract:
- Session ID: from the filename
- Summary: the objective or summary section
- Pain points / blockers: lines under "Pain points", "Blockers", or "Process improvement items"
- Decisions made: items in any "Decisions" section
- Error autopsies referenced: any EA-NNN references
- Specs worked on: any spec IDs mentioned
Track each file path in SOURCES list.
[mechanical] Step A2 — Read error-log.md
Read docs/sessions/error-log.md. Extract EA-NNN entries referenced in the gathered session logs.
If file does not exist: skip silently.
Add to SOURCES if read.
[mechanical] Step A3 — Read signals.md
Read docs/sessions/signals.md. Extract SIG-NNN entries from the date range covered by the gathered sessions.
If file does not exist: skip silently.
Add to SOURCES if read.
[decision] Step A4 — Generate postmortem
Write a structured postmortem document to OUTPUT_FILE with these sections:
- Title: "Postmortem — {TODAY}" with a generated-by note showing N sessions analyzed
- Period Covered: date of oldest session to date of newest session
- Executive Summary: 2-3 sentence summary of key accomplishments, recurring problems, and overall trajectory
- Key Accomplishments: bulleted list of specs completed, features delivered, process improvements made
- Recurring Problems: bulleted list of pain points or blockers appearing in 2+ sessions, with session references
- Error Patterns: summary of error autopsies grouped by root cause; if none, state "No error autopsies recorded in this period."
- Decisions Made: chronological list with date and context for each
- Signals & Observations: notable signals grouped by type
- Recommendations: 3-5 actionable recommendations based on patterns observed
- Sources: bulleted list of every file path that contributed
Mode B — Topic Summary (--topic <query>)
[mechanical] Step B1 — Search artifacts
Search the following directories for files containing QUERY (case-insensitive):
docs/specs/— spec filesdocs/sessions/— session logsdocs/decisions/— ADR filesdocs/sessions/signals.md— signal entriesdocs/sessions/error-log.md— error autopsiesdocs/sessions/insights-log.md— chat insightsdocs/sessions/scratchpad.md— open notesAGENTS.md— agent configuration
For each match, record the file path and the matching section/context (the paragraph or list item containing the match, plus surrounding context).
Track each file path in SOURCES list.
If no matches found: write a brief note to OUTPUT_FILE stating "No artifacts found matching the query." and stop.
[decision] Step B2 — Generate topic summary
Read the matching sections from each file (read the relevant portions, not entire files when they are large).
Write a structured topic summary document to OUTPUT_FILE with these sections:
- Title: "Topic Summary: {QUERY}" with a generated-by note and list of artifact types searched
- Overview: 2-3 sentence synthesis of what the project artifacts say about this topic
- Spec Coverage: list of specs referencing this topic, with status and one-line relevance summary
- Decisions & Rationale: decisions from session logs and ADRs in chronological order
- Signals & Observations: relevant signals, error autopsies, and insights
- Open Items: scratchpad notes, unresolved questions, or draft specs related to this topic
- Synthesis: coherent narrative connecting findings — what has been decided, what remains open, trajectory
- Sources: bulleted list of every file path that contributed
Mode C — Decision Log (--decisions)
[mechanical] Step C1 — Gather session logs
Read all .md files in docs/sessions/ excluding _template.md, signals.md, error-log.md, insights-log.md, scratchpad.md, context-snapshot.md, and registry.md.
If --since YYYY-MM-DD is set: only include files whose date prefix >= that date.
Sort by filename date prefix (oldest first — chronological order).
From each session log, extract content under "Decisions made" or "Decisions" sections.
Track each file path in SOURCES list.
[mechanical] Step C2 — Read ADRs
Read all .md files in docs/decisions/ (if the directory exists).
Extract the decision title, status, date, and context from each ADR.
If directory does not exist or is empty: skip silently.
Add each file to SOURCES if read.
[decision] Step C3 — Generate decision log
Write a structured decision log document to OUTPUT_FILE with these sections:
- Title: "Decision Log" with a generated-by note and period covered
- Summary: count of decisions extracted from N session logs and M ADRs
- Chronological Decision Log: for each session date, list each decision with its text, surrounding context, and spec ID if referenced
- ADR Decisions: list each ADR with title, status, date, and one-line summary; if none, state "No ADRs found."
- Decision Themes: group decisions by theme/area (e.g., Architecture, Process, Tooling) and summarize trajectory
- Sources: bulleted list of every file path that contributed
Mode D — Architecture Overview (--architecture)
[mechanical] Step D1 — Read ADRs
Read all .md files in docs/decisions/ (if the directory exists).
If directory does not exist or is empty: note "No ADRs found" and continue.
Add each file to SOURCES if read.
[mechanical] Step D2 — Read closed specs
Read docs/specs/README.md to identify closed specs.
For each closed spec, read its "Implementation Summary" section (the ## Implementation Summary block).
If no closed specs exist: note "No closed specs found" and continue.
Add each file to SOURCES if read.
[mechanical] Step D3 — Read agent config
Read AGENTS.md if it exists. Extract the architecture-relevant sections (capabilities, tools, coordination patterns).
If file does not exist: skip silently.
Add to SOURCES if read.
[mechanical] Step D4 — Read CLAUDE.md
Read CLAUDE.md. Extract the "Architecture quick-ref" section and any structural information.
Add to SOURCES.
[decision] Step D5 — Generate architecture overview
Write a structured architecture overview document to OUTPUT_FILE with these sections:
- Title: "Architecture Overview" with a generated-by note and a disclaimer to verify against source artifacts
- System Overview: high-level description based on CLAUDE.md, AGENTS.md, and closed specs
- Key Components: list of major components/modules with one-line descriptions
- Architectural Decisions: summary of ADRs and rationale; if none, state "No ADRs recorded. Architectural decisions are embedded in spec files and session logs."
- Evolution History: how architecture evolved based on closed specs, chronologically ordered
- Current State: what the architecture looks like now based on most recent closed specs and AGENTS.md
- Known Gaps & Open Questions: gaps from draft/in-progress specs, scratchpad notes, or missing ADRs
- Sources: bulleted list of every file path that contributed
Mode E — All modes (--all) (Spec 328)
When MODE=all, run all four single-mode bodies sequentially in this order: postmortem → decisions → architecture → topic. Each mode writes its standard output file using the existing naming convention. Continue-on-error: if any mode fails (missing input artifacts, write error, etc.), record the failure and proceed to the next mode — do NOT abort the run.
[mechanical] Step E1 — Resolve --topic query for the topic mode
For the --topic portion of --all, no QUERY was supplied at invocation. Infer one:
- Read the 3 most recent session logs from
docs/sessions/(sorted by filename descending). - Count mentions of each spec ID and significant concept (e.g., recurring multi-word phrases) across those logs.
- If a single spec ID or concept appears 3+× more than any other, set
QUERY=<that-token>. - Otherwise, set
QUERY=recent-activityand run the topic mode against general recent-session content. - Record the inferred query in the run summary (Step E3) so the operator can override on the next manual invocation.
[mechanical] Step E2 — Run each mode
For each mode in the order [postmortem, decisions, architecture, topic]:
- Set
CURRENT_MODEandOUTPUT_FILEper the mode's standard naming convention. - Execute the mode's existing Step body (Mode A, C, D, B respectively above).
- On success: record
<mode>: PASS — <path>. - On failure (e.g., insufficient artifacts, write error): record
<mode>: FAIL — <reason>and continue to the next mode. Do NOT propagate the failure or abort.
[mechanical] Step E3 — Write run summary
After all four modes have been attempted, print a single summary block:
Synthesis (--all) complete:
- postmortem: <PASS|FAIL> — <path or reason>
- decisions: <PASS|FAIL> — <path or reason>
- architecture: <PASS|FAIL> — <path or reason>
- topic ({QUERY}): <PASS|FAIL> — <path or reason>
Total: <N>/4 modes succeeded.Then proceed to Step 3 — Next action below (the next-action recommendations apply to whichever modes succeeded).
[mechanical] Step 2 — Confirm output
After writing the output file, print:
Synthesis complete: {OUTPUT_FILE}
Mode: {MODE}
Sources: {count} artifacts consultedSkip this step if MODE=all — the run summary in Step E3 replaces this single-mode confirmation.
[mechanical] Step 3 — Next action
Present a context-aware next action:
- If postmortem: "Next: review the postmortem and share with your team. Run
/noteto capture any follow-up items." - If topic: "Next: review the topic summary. Run
/specif any open items need formal tracking." - If decisions: "Next: review the decision log for consistency. Run
/evolveif decision patterns suggest process improvements." - If architecture: "Next: review the architecture overview for accuracy. Run
/noteto flag any corrections needed."
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

