reflect

Reflect — session reflection

Analyze current session and propose additions to the project backlog.

1. Find backlog target

Check memory for saved preference:

node "$MEM" --dir="$MEM_DIR" search "backlog_target"

If no saved preference — detect automatically:

1. Check common locations: backlog.md, TODO.md, TODO, docs/backlog.md
2. Check if project uses GitHub Issues: gh issue list --limit 1 2>/dev/null
3. If nothing found — ask:

Where do you track backlog?
  1. backlog.md (will create)
  2. TODO.md
  3. GitHub Issues (gh issue create)
  4. Other — specify path or tool

Save preference:

node "$MEM" --dir="$MEM_DIR" note "CONFIG: backlog_target=<chosen path or github-issues>"

Read current backlog to avoid duplicates.

1b. Collect watcher auto-findings

The session watcher captures decisions, plans, corrections, and phase changes in real time. Review them before analyzing manually — many candidates for backlog / DOC notes are already surfaced:

node "$MEM" --dir="$MEM_DIR" findings

Output groups entries by type (decision, plan, correction, phase). Treat them as candidates, not authoritative:

• correction — strong candidate for feedback/ memory
• decision — candidate for decisions/ or backlog
• plan — candidate for backlog entry
• phase — context only, usually skip

User confirms which findings promote to backlog / memory in step 3.

2. Analyze session

Review what happened and find:

• Workarounds — bugs/problems worked around, not fixed
• Repetitions — pattern that appeared >1 time, asks for automation
• Gaps — skill/rule that was missing, had to do manually
• Insights — decisions worth scaling to other areas
• Done — what from backlog was completed this session

DOC classification check

For each insight, ask: "Should any contributor to this project know this?" If yes — it's a DOC, not just a backlog item or feedback. Save it immediately:

node "$MEM" --dir="$MEM_DIR" note "DOC: <domain> — <insight>"