What problem does it solve? When someone joins a Linear project midway, they cannot reconstruct why decisions were made or where the project currently stands from scattered issues, Slack threads, meeting notes, and PRs. This Skill consolidates those sources into a single chronological document focused on decisions, current status, and next steps rather than raw work logs. ## Core Features & Use Cases - Multi-source aggregation: Pulls context from Linear issues, milestones, and documents plus Slack threads, Notion pages, Google Meet notes, and GitHub PRs via dedicated fetch skills. - Decision-focused timeline: Filters out routine status changes and work logs, keeping only scope changes, key decisions, milestone completions, and blockers, organized by date with linked evidence. - Safe write workflow: Always presents a draft for user approval before creating or updating the Linear project document, and stops on authentication errors instead of falling back to partial writes. - Use Case: A new engineer joins a project. Run this Skill against the Linear project to produce a timeline document covering what was decided, the current milestone position, and links to the key artifacts they need to read. ## Quick Start Use the workflow-update-linear-project-timeline skill to create a chronological decision and status document for this Linear project, covering everything since the project started.
