ctx-timeline

Generate chronological project timelines from stakeholder intelligence into structured markdown.

4|Updated Apr 26, 2026
One-click install
npx skills add https://github.com/simonconway1979/os-intelligence --skill ctx-timeline
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ctx-timeline
Source: https://github.com/simonconway1979/os-intelligence/tree/main/.claude/skills/ctx-timeline
Command: npx skills add https://github.com/simonconway1979/os-intelligence --skill ctx-timeline

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It turns scattered stakeholder intelligence—meetings, logs, events, and key decisions—into a single chronological timeline, so you can quickly understand what happened and what still needs attention.

Core Features & Use Cases

  • Timeline generation from SI sources: Reads project intelligence files (meetings synthesis, logs synthesis, optional events, and memory decisions) and compiles them into past and upcoming sections.
  • Two output modes: Produces a fast summary timeline or a detailed timeline with expanded context such as key quotes, shifts, and significance.
  • Next-step extraction: Identifies open commitments and synthesizes a capped list of “what comes next” actions based on commitments and urgent flags.

Quick Start

Run ctx-timeline to generate a project timeline at intelligence/timeline.md by selecting the active project, choosing summary or detailed mode, and setting the time range.

Frequently Asked Questions about ctx-timeline

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a project timeline from scattered meeting notes and stakeholder intelligence?

To generate a project timeline from stakeholder intelligence, the Skill reads inputs from intelligence and events subfolders, applies date-aware ordering, and writes a structured chronological timeline to intelligence/timeline.md.

What is the best way to track unresolved commitments across multiple project meetings?

Tracking unresolved commitments is handled by synthesizing meeting logs and memory-based decisions to detect open commitments, generating a capped list of upcoming next-step actions based on urgent flags.

Can I create a quick summary timeline instead of a detailed chronological project log?

Yes, you can create a quick summary timeline by selecting summary mode, which compiles stakeholder intelligence into a fast overview, or choose detailed mode for expanded context including key quotes and shifts.

Do I need YAML frontmatter in my stakeholder intelligence files to build a chronological timeline?

Yes, YAML frontmatter parsing is required to classify and apply date-aware ordering to stakeholder intelligence files, ensuring meetings, logs, and events are structured correctly into past and upcoming sections.

How to extract next-step actions from memory-based key decisions and stakeholder logs?

Extracting next-step actions involves detecting unresolved commitments within memory-based key decisions and stakeholder logs, synthesizing them into a capped list of what comes next based on urgency.