timeline

Builds event storming timelines on a board by placing EVENT nodes via API calls during live conversation.

Updated Aug 10, 2026
One-click install
npx skills add https://github.com/Powerworks/Underwriting --skill timeline-powerworks
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: timeline
Source: https://github.com/Powerworks/Underwriting/tree/main/agentic-modeling/.claude/skills/timeline
Command: npx skills add https://github.com/Powerworks/Underwriting --skill timeline-powerworks

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Mapping a business process into an event storming timeline normally requires manual board editing after a workshop. This Skill acts as a live facilitator that discovers domain events from conversation or pasted documents and places them on the board in real time as they emerge. ## Core Features & Use Cases - Live event discovery: Extracts domain events from any input (prose, notes, requirements docs) and immediately creates EVENT nodes on the board via API calls. - Timeline maintenance: Renames, inserts, reorders, and removes events as understanding evolves, reusing empty columns to keep the timeline contiguous. - Session continuity: Resumes existing timelines by resolving chapter IDs and loading current event state from the board. - Use Case: Paste a requirements document for an order fulfillment process and watch the timeline populate with events like "Order Placed", "Payment Received", and "Shipment Dispatched" as the conversation progresses. ## Quick Start Start a live event storming session by describing your business process and let the facilitator build the timeline on the board in real time.

Frequently Asked Questions about timeline

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

FAQPage Schema
How do I build an event storming timeline from a conversation?▼

Describe your business process in any form—prose, bullet points, or pasted documents—and the facilitator extracts domain events and places them on the board immediately. Each turn updates the timeline before summarizing what changed and asking one follow-up question.

How do I continue an existing event storming timeline?▼

Provide a chapter UUID or chapter name as the timelineId argument. The skill resolves names to UUIDs, fetches the chapter's timelineData grid structure, loads existing EVENT nodes ordered by column position, and resumes from that state.

What makes a good domain event name in event storming?▼

Domain events use past tense business language in two to four words, such as "Order Placed" or "Payment Received". Avoid technical terms like "record inserted" or "API called", and prefer specific names like "Invoice Sent" over generic ones like "Status Changed".

Can the timeline skill place commands or read models on the board?▼

No, the skill places EVENT nodes only, always in the swimlane lane. Commands, read models, and screens are explicitly out of scope and must be handled by other skills such as place-element with different element types.

What happens to empty columns when events are removed from a timeline?▼

Before placing new events, the skill identifies empty columns and reuses them first to keep the timeline contiguous. After all placements, any remaining empty columns are deleted via the timeline columns API so no gaps remain.