When to use what

Decide between similar concepts.

Note vs Backlog item vs Issue vs Task

• Note - a thought you want to remember but isn't work to do "Note: the API returns 503 sometimes during deploys"
• Backlog item - future work, not committed to yet "Add to the backlog: redesign the settings page"
• Feature Task - concrete work within an in-progress feature "Mark the schema migration task as done"
• Issue - a bug or tech debt discovered, needs tracking "Report an issue: race condition in session cleanup"

Quick rule:

• Thought → Note
• Idea for later → Backlog
• Part of the current feature → Task
• Something broken → Issue

Main session vs Feature session

• Main session - connected to a product or focus area, no feature. For exploration, small fixes, conversations that have not crystalized.
• Feature session - connected to a feature. Writes land on it: notes, plans, diagrams, the log.

Both are just what rememd connect was pointed at. If you find yourself in a main session doing serious work, ask "should we promote this to a feature?"

Two features at once

rememd does not manage branches, worktrees or terminals - that is yours, and several terminals at once is the normal state. What it manages is where the writing goes.

• A second terminal - rememd connect there, on the other feature. The two do not interfere; each has its own binding.
• The same terminal - attach_to_feature. Writes scope to the attached feature without moving what this terminal is connected to, and detach_from_feature parks it.

Focus area vs Feature

• Focus area - strategic theme, lasts months. "Growth". "Developer tools". "Marketing".
• Feature - concrete deliverable, lasts days to weeks. "Onboarding flow v2". "Webhook system".

Focus areas rarely change. Features constantly come and go.

Product-level backlog vs Focus-area backlog

• Product-level - idea doesn't fit a single focus area, or you haven't decided yet
• Focus-area - scoped to strategic area

You can always re-scope later (right-click a backlog item → Move to).