Common conversations

Real examples of flows you'd actually have with the agent.

Starting fresh on a feature

$ cd ~/dev/famnly && rememd connect
✓ Connected to Famnly / Webhook system
  Started session 4F2A1B9C
  Agents started here will pick this up automatically.

You: "What are we building?"

The agent: [calls get_feature_context]
        "Webhook system - 3 of 8 tasks done. The PRD says …"

You open the terminal and the branch; rememd binds the context to it. The agent's first answer already knows the PRD, without you naming the feature.

Promoting a backlog item

You: "What's in the backlog?"

The agent: [calls get_backlog]
        "Here's what's pending for Famnly:

        ## Developer tools
        - [MEDIUM] Connect IDs to avatar images
        - [MEDIUM] Integrate n8n

        ## Unfocused
        - [MEDIUM] Fix more languages"

You: "Let's do the n8n integration - help me scope it"

The agent: "Sure. A few questions:
        1. Self-hosted or n8n Cloud?
        2. Which workflows first - welcome emails, trial reminders?
        3. Where should it live - in the main repo or a sibling?"

You: "Self-hosted, welcome + trial, new sibling repo"

The agent: [calls create_feature with repo_path pointing to a new folder]
        "Created feature 'Integrate n8n' with a new repo at ~/dev/famnly-n8n.
        Open a terminal there and run `rememd connect` to work on it - or say
        the word and I'll attach to it from here."

Capturing discoveries mid-session

You: "While we're here, we should also think about rate limiting - note that"

The agent: [calls add_backlog_item]
        "Added to the Developer tools backlog: 'Add rate limiting to webhook system'."

You: "Oh and there's a bug - retries don't respect Retry-After header"

The agent: [calls report_issue]
        "Reported [HIGH] issue: 'Retries ignore Retry-After header'. Linked to this session."

Ending a session

You: "Let's wrap. Log this session and promote the key learnings."

The agent: [calls log_session, then promote_knowledge]
        "Logged the session. Graduated this key learning to product knowledge:
        'When integrating n8n, always pin the image version - latest breaks webhooks.'"

Starting the next day

You: "Where did we leave off?"

The agent: [calls get_feature_context for the active feature]
        "Last session we set up n8n with Docker and got the welcome flow firing.
        Next steps from the log:
        - Verify the trial-reminder workflow triggers at day 7
        - Add retry-after header parsing (tracked as issue HIGH)
        Tasks remaining: 4 todo, 2 done."

Scaffolding a whole area in one sentence

Focus area, feature, PRD and repo in a single request:

You: "Create a focus area called 'Growth' (description: user acquisition
      experiments). Add a feature 'Referral program' with a PRD about
      giving users credit for invites, in a new folder at ~/dev/growth-referrals."

The agent: [calls create_focus_area]
        → creates "Growth" focus area with description
        [calls create_feature]
        → creates folder, runs git init, creates feature with PRD linked to repo
        "Feature 'Referral program' created in 'Growth', connected to
         ~/dev/growth-referrals."

$ cd ~/dev/growth-referrals && rememd connect

Both tools share the product context, so the agent resolves it once. The last step is yours and is deliberately not automated: rememd does not open terminals, and which one you work in - with which branch checked out - is not something it should be guessing.