Placeholder deploy

Volat

A roadmapping tool built for design teams โ€” planning views on top of Jira, strategic goals, weekly notes, and a Jira-safe way to write changes back.

This is a placeholder page. The real app is under active development โ€” see claude.md in the repo.

What this is

Jira is the system of record for engineering, but it doesn't give design leads the planning views they need: roadmaps organized by designer, by product area, or by strategic goal. Volat sits on top of Jira as a planning and visibility layer โ€” it pulls in epics, issues, and people, lets managers lay out roadmaps and timelines, attach weekly progress notes, and stage every change as plain text that can be pasted straight into Claude Code to update Jira. No login required for v1.

Core capabilities

๐Ÿ—‚๏ธ Jira import

Connects to Jira to pull in epics, issues, and people, so roadmap data starts from what's actually in Jira instead of a second spreadsheet.

๐ŸŽฏ Strategic goals

Managers define larger goals per workstream and assign projects to them, so tactical Jira work is visibly tied to strategic priorities.

๐Ÿ—“๏ธ Roadmaps & timelines

Drag-to-adjust timelines, editable descriptions and assignments โ€” grouped by designer, product area, goal, or Jira parent.

๐Ÿ“ Weekly notes

Each project gets a running log of weekly progress notes plus attached reference files, so history isn't lost between check-ins.

๐Ÿ” Change log โ†’ Claude Code

Every edit made in the app โ€” timelines, descriptions, assignments, weekly updates โ€” is also written to a plaintext change log. Copy it, paste it into Claude Code (connected to Jira), and the changes land back in Jira.

๐Ÿ“ฃ Weekly update generator

Combines this week's notes across every project into one document, prepends a fixed prompt, and produces text ready to paste in to generate a weekly update in a specific, predefined format.

How data flows

  1. Jira in: epics, issues, and people are pulled from Jira into the app.
  2. Plan in-app: managers build roadmaps, adjust timelines, edit descriptions/assignments, and log weekly notes per project.
  3. Everything is a JSON file: the app has no traditional database โ€” all state (roadmap, goals, notes, change log) lives in a single JSON file that the app reads and writes.
  4. Changes become text: every change made in-app is simultaneously reflected in the UI and appended to a plaintext change log.
  5. Push back via Claude Code: the manager copies that text and pastes it into a Claude Code session connected to Jira, which applies the updates on the Jira side.
  6. Weekly rollup: weekly notes from every project can be combined into a single document with a prompt prepended, ready to paste in to produce a formatted weekly update.

Status

No login (v1) JSON as database Jira read via import/API Write-back via Claude Code Static hosting โ€” Cloudflare Pages