roadmap-timeline
Skill0 starsChanged 13 days agoMITView on GitHub
Draw a roadmap, timeline, release plan, project schedule, quarterly plan or history of events on an editable Igly canvas. Use when the user lists work over time, milestones, phases, sprints or dates.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- pnp/sharepoint-skillstheir own version, first seen Aug 24, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- pnp/sharepoint-skills★ 142same name
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.
In this repository8 other files it gives its agents.
- animationSkill
- flowchartSkill
- kanban-retroSkill
- mind-mapSkill
- moodboardSkill
- storyboardSkill
- template-designSkill
- wireframeSkill
The file
Files
Roadmap and timeline
1. Plan
- Choose the time unit from the input: quarters, months, weeks, sprints or dated events.
- Group items into 2 to 5 lanes (teams, themes or workstreams) when there are more than 8 items.
2. Create
create_canvas with a title such as "2027 product roadmap". Keep canvas_id.
3. Layout (one add_elements call)
- Title text at (0, -140),
font_size: 48, bold. - Time columns: one header per period,
type: "shape", rectangle 300 x 70 at x = 200 + i * 320, y = -40, fill#1E1E1E,text_color: "#FFFFFF", bold,font_family: "Inter". - Lane labels:
type: "text"at x = 0, y = 60 + lane * 260, bold,font_size: 26. - Items:
type: "sticky", 280 x 180, placed in their period column and lane, x = 210 + i * 320, y = 50 + lane * 260 (stack a second item in the same cell 200 lower and grow the lane). - One sticky
colorper lane:#BFDBFE,#FBCFE8,#BBF7D0,#FDE68A,#DDD6FE. - Milestones:
shape: "star"90 x 90 at the column edge, with a shorttype: "text"caption below. - Optional "today" marker:
type: "line"from (x, -60) to (x, bottom),stroke: "#E03131",stroke_width: 4,dashed: true. - Tentative or stretch items:
dashed: trueon the bar so they read as not committed. - Dependencies between bars in different lanes:
type: "arrow"withfrom_id/to_idandcurvetoward the side with space so it clears other bars. - For a single-track timeline of events, use one horizontal
type: "arrow"from (0, 0) to (end, 0), smallellipsedots on it and alternating sticky notes above and below.
4. Check
get_canvas_summary, thenarrangewithalign_topper row ordistribute_horizontalper lane if spacing drifted.- Offer edits: move an item to another quarter (
update_elementswithdx: 320), add a lane, export a PNG.
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.

