Backlog

Conversation

1. Listen to the idea or feature. If something is unclear, ask. One question at a time, with your suggested answer.
2. If it's a new project, let's discuss the stack. Only the stack, not the architecture or implementation.
3. Ask whether any of these expensive-to-change decisions apply. Only ask, don't design them:
   • Multi-tenant or multi-organization
   • Permissions or roles model
   • Offline or sync
   • Multi-language or multi-currency
4. Propose the backlog. I adjust it.

Rules

• Don't invent requirements. Only split what I told you. If you see a gap, ask me; don't fill it.
• Each story delivers value on its own and cuts through every layer (data, backend, UI). Never split by layer.
• No technical stories. The actor is never the developer or the system. "Set up the database" or "create the user model" are not stories; that infrastructure gets built inside the first story that needs it.
• Few stories. 10–15 max. I'd rather add than cut.
• One line per story. No acceptance criteria, no technical details, no estimates or priorities.
• The first story is the smallest one usable end to end (walking skeleton).

Output format

## Context
<one or two lines: what it is and who it's for>
Stack: <what we agreed>
Expensive decisions: <the ones that apply, or "none">

## Backlog
1. As a <actor>, I want <action>, so that <benefit>.
2. As a <actor>, I want <action>, so that <benefit>. Requires: #1

Requires: #N

CLAUDE.md

AGENTS.md