Templates · Product & Dev

Dev Project

Issues with a Triage inbox, lightweight sprints, releases with changelogs, and specs.

Without it

Issues arrive from five places, nobody triages them, and the board fills with tickets that have no type, no priority and no owner.

app.storyos.dev

The Dev Project template in StoryOS — its Issue Board view with real records

Dev Project, installed — the Issue Board view with sample records already in it.

What gets installed

4 connected databases, with fields, relations and views pre-wired.

Issues

State · selectPriority · selectLabels · multi_selectAssignee · userDue Date · dateEstimate (pts) · numberEffort spent · numberType · select

Sprints

Status · selectStart Date · dateEnd Date · dateGoal · textVelocity (pts) · number

Releases

Status · selectDate · dateLink · url

Product Docs

Type · selectStatus · selectOwner · user

Ships with 7 saved views: Issue Board (board) · Triage (table) · My Tasks (table) · Due This Week (table) · Bugs (table) · Release Board (board) · Open Specs (table)

How this template works

How this works

The Linear model, self-hosted: Issues with full task DNA (Triage → Backlog → To Do → In Progress → In Review → Done/Canceled, priorities, labels, sub-issues, blockers), Sprints, Releases with changelogs, and Product Docs for specs and ADRs.

The loop

Everything lands in Triage; sweep it daily.
Sprint planning: drag from Backlog into the sprint; the Issue Board is standup.
Ship: link issues to a Release; the release page is the changelog.

Then put an agent on it

A new issue in Triage wakes an agent that proposes its type, priority and labels from the description — you accept or override at the gate.

It runs on your own Claude or ChatGPT over MCP — never metered, never marked up — and every move it makes waits at an approval gate. How agent runs work →

More product & dev templates

Solo Dev

Issues + releases, zero ceremony — for shipping on vibes and a changelog.

Template contents synced from the product registry, 2026-07-26.