Backlog to feature

The primary way work moves through rememd.

1. Capture (Backlog)

Ideas live in the backlog before they become features. You can add items:

• UI: the field at the top of a product's Backlog in the panel
• Natural language to the agent: "Add to backlog: redesign settings page"

Items belong to a focus area (or are "unfocused" at product level). They have a priority and stay pending until promoted.

2. Promote to Feature

When ready to actually work on something, say "Let's do [item] - scope it with me". The agent will:

1. Ask clarifying questions
2. Write a PRD based on the discussion
3. Call create_feature_from_backlog - creates feature, saves PRD, keeps the backlog link

The backlog item gets a promotedToFeatureId - it stays in the record but is no longer pending.

3. Break Down into Tasks

Say "Break this into tasks". your agent reads the PRD and generates structured tasks with dependencies.

Tasks have:

• Priority and status (todo/in-progress/done)
• blockedBy dependencies - which tasks must finish first
• Optional assignee (for multi-agent or team use)

4. Connect a terminal to it

Open a terminal wherever the code is, on whatever branch you want, and run rememd connect. Pick the feature from the panel.

rememd creates no branch, no folder and no terminal - those are yours. What it does is bind this terminal to that feature, so the agent's context and every write it makes land there without being told.

5. Work and Log

As you go:

• "What's next?" → the agent highlights the NEXT unblocked task
• "Mark X done" → update_task
• "Bug: [description]" → report_issue
• "Add note: [thought]" → add_note

At session end:

• "Log this session" → log_session writes the structured markdown

Deletion behavior

If you delete a feature that a backlog item was promoted to, the backlog item's promotedToFeatureId resets to nil - it returns to the pending backlog, available for re-promotion.