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.
In Lobstack: Skills › Library › Add
What your agent will do.
Someone has asked for a feature, or a conversation has settled on building one, and it needs writing down before anyone plans or builds it.
- 01
Find the problem behind the request. "Add a CSV export" often means "I need these numbers in my spreadsheet every Monday". Ask when it is not clear who hits the problem and how often.
- 02
Write these sections:
- Problem: two or three sentences, with evidence — a quote, a ticket, a number.
- Who it is for, and what they do today instead.
- What it does, from the user's side, step by step.
- Non-goals: what it deliberately does not do. This is the section that stops the scope growing.
- Acceptance checks: statements that are either true or false.
- Open questions, each with who can answer it.
- 03
Leave out how to build it unless a constraint forces the choice.
- 04
Mark anything you assumed rather than read "(assumed)".
- 05
Two pages at most. Detail that changes no decision goes in a link.
- 06
Post it as a document. Ask before copying it into Notion, Linear or any other shared tool.
If the problem will not fit in two sentences, say so: it is not ready for a spec yet.
The whole SKILL.md: 36 lines of Markdown.
Add it in the app from Skills › Library, or copy it and paste it into Skills › Add a skill.
---name: feature-specdescription: "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."metadata: title: "Feature spec" category: product tags: [product, planning]--- ## When to use this Someone has asked for a feature, or a conversation has settled on building one,and it needs writing down before anyone plans or builds it. ## How 1. Find the problem behind the request. "Add a CSV export" often means "I need these numbers in my spreadsheet every Monday". Ask when it is not clear who hits the problem and how often.2. Write these sections: - Problem: two or three sentences, with evidence -- a quote, a ticket, a number. - Who it is for, and what they do today instead. - What it does, from the user's side, step by step. - Non-goals: what it deliberately does not do. This is the section that stops the scope growing. - Acceptance checks: statements that are either true or false. - Open questions, each with who can answer it.3. Leave out how to build it unless a constraint forces the choice.4. Mark anything you assumed rather than read "(assumed)".5. Two pages at most. Detail that changes no decision goes in a link.6. Post it as a document. Ask before copying it into Notion, Linear or any other shared tool. If the problem will not fit in two sentences, say so: it is not ready for aspec yet.
- 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
Roadmap update
Write a short roadmap update from what actually shipped and what is next: done, in progress, next, and what moved and why.
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