Roadmap update
Write a short roadmap update from what actually shipped and what is next: done, in progress, next, and what moved and why.
In Lobstack: Skills › Library › Add
What your agent will do.
A team, investors or customers need to know where the product is going, and the last update is out of date.
- 01
Start from evidence: releases, merged changes, closed issues and the board, for the period since the last update. Read the last update too.
- 02
Write four short sections:
- Shipped: each with its date and who it is for.
- In progress: with an honest expected date, or none.
- Next: the few things chosen, and the one reason for each.
- Moved: anything that slipped or was dropped, and why.
- 03
Put the customer's benefit first in each line; the feature name second.
- 04
Link every shipped item to its release note or change.
No dates you cannot defend. A roadmap that keeps its promises is worth more than a long one.
The whole SKILL.md: 28 lines of Markdown.
Add it in the app from Skills › Library, or copy it and paste it into Skills › Add a skill.
---name: roadmap-updatedescription: "Write a short roadmap update from what actually shipped and what is next: done, in progress, next, and what moved and why."metadata: title: "Roadmap update" category: product tags: [product, planning]--- ## When to use this A team, investors or customers need to know where the product is going, andthe last update is out of date. ## How 1. Start from evidence: releases, merged changes, closed issues and the board, for the period since the last update. Read the last update too.2. Write four short sections: - Shipped: each with its date and who it is for. - In progress: with an honest expected date, or none. - Next: the few things chosen, and the one reason for each. - Moved: anything that slipped or was dropped, and why.3. Put the customer's benefit first in each line; the feature name second.4. Link every shipped item to its release note or change. No dates you cannot defend. A roadmap that keeps its promises is worth morethan a long one.
- Product
Themes from customer feedback
Group customer feedback (tickets, reviews, survey answers, call notes) into themes, each with a count, a word-for-word quote and the decision it bears on.
SKILL.md · App - Product
Break a spec into tickets
Split a spec, plan or thread into small tickets that each ship on their own, with order, dependencies and a check for done. Shown before anything is filed.
SKILL.md · App - Product
Feature spec
Turn a request, thread or idea into a one-to-two page feature spec: the problem, who it is for, scope, non-goals, acceptance checks and open questions.
SKILL.md · App - Engineering
Commit message from a diff
Write a commit message from a diff: a subject line that states what was found, then prose explaining why the change was made.
SKILL.md · App - Engineering
Triage a failing build
Triage a red CI run: find the first real failure, attribute it to a change, and say whether the code is wrong or the runner was.
SKILL.md · App - Engineering
Review what a linter cannot
Review a change for what a linter cannot see: whether it is correct, what it breaks elsewhere, and which parallel list it forgot to update.
SKILL.md · App