メニュー
Generate a project timeline from stakeholder intelligence — meetings, logs, events, decisions, and what comes next. Two modes: summary (one-liner per event) and detailed (expanded with quotes, decisions, shifts).
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Point at a folder of markdown and write one reconciled, provenance-tagged, staleness-aware current-state.md sidecar — the summary-of-summaries that updates and self-corrects across runs. Works on any markdown corpus (call summaries, transcripts, notes, PRDs); imposes no folder structure and edits nothing but its own output file. Use when the user runs /synthesise, asks for a current state / synthesis / "what do we know now" over a folder, or wants a folder's scattered markdown reconciled into one living state file.
Add a new item to any portfolio project. Reads the portfolio's CLAUDE.md for item name and template path. Creates the item folder from templates/item/, updates TRACKER.md. Works for any portfolio type (opportunities, ideas, articles, etc.).
Load project context and start a session with a compact briefing of recent work and next steps
Add context to the active project. Triages the input as a meeting transcript, document, personal note, or chat thread — then routes to the right writer. Replaces the four `/ctx-*` entry points.
Capture a WhatsApp, Slack, or DM thread into project context. Handles multi-party threads with deduplication — import the same thread repeatedly and only new messages get processed.
Add a document to the project and update synthesised context. Run this whenever new source material arrives — calls, transcripts, documents, briefs. Walks through adding frontmatter, updating context files, and syncing people records.
| name | ctx-timeline |
| description | Generate a project timeline from stakeholder intelligence — meetings, logs, events, decisions, and what comes next. Two modes: summary (one-liner per event) and detailed (expanded with quotes, decisions, shifts). |
Two phases:
Step 1 — Print:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
TIMELINE
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Step 2 — Project. Read root CLAUDE.md for **Active project:**. Show the project name. Confirm with user (Y/N or just Enter).
Step 3 — Mode. Ask:
Mode?
1. Summary — one line per event (fast read, shareable)
2. Detailed — expanded with key quotes, decisions, and shifts
(Enter 1 or 2)
Wait for response.
Step 4 — Scope. Ask:
Time range?
1. Full history (all meetings and logs)
2. From a date (enter YYYY-MM-DD)
(Enter 1 or date)
Wait for response.
Step 5 — Hand off.
Say: Got it. Building timeline in the background — you can keep working.
Spawn background agent (run_in_background: true). Pass:
PROJECT_ROOT — e.g. projects/acme-corp-launch/PROJECT_NAME — from CLAUDE.mdMODE — summary or detailedFROM_DATE — YYYY-MM-DD or null (full history)SI_DIR — [PROJECT_ROOT]/intelligence/EVENTS_DIR — [PROJECT_ROOT]/events/ (may not exist)MEMORY_DIR — [PROJECT_ROOT]/memory/OUTPUT_PATH — [PROJECT_ROOT]/intelligence/timeline.mdTell the agent: Read .claude/skills/ctx-timeline/BACKGROUND.md for full instructions. Do not ask questions — proceed through all steps.