sitrep

Sitrep — Situational Awareness

One command to answer: Where am I? What was I doing? What's left? What's next?

Filters (optional args)

Sitrep accepts optional filter args after the skill name:

Arg	Example	Applies to
--tag <tag>	sitrep --tag harness-engineering	Source 3, Next action
--stream <stream>	sitrep --stream roadmap	Source 3, Next action
--kind <kind>	sitrep --kind feature	Source 3, Next action
--priority <p>	sitrep --priority P0	Source 3, Next action

Multiple filters combine with AND. When any filter is active, show a Filter: line in the output header and scope all backlog queries to the filter. The session handoff (Source 4) and git state (Source 2) are never filtered.

---

When to use

• After context compression (conversation truncated)
• When confused about current progress or state
• Mid-session reorientation ("wait, what was I doing?")
• After returning from a tangent or interruption
• Proactively: anytime you're unsure whether to continue, stop, or switch

ToolSearch("select:mcp__ruflo__memory_search_unified,mcp__brana__session_history")

Process

Gather from 6 sources in parallel, then synthesize into one snapshot. No writes — this is read-only.

1. CC Tasks (active skill flow)

Call TaskList

Look for:

• in_progress tasks → you're mid-step in a skill flow
• pending tasks with completed blockers → next step to execute
• Pattern: subject format /brana:{skill} — {STEP} reveals which skill is active

If CC Tasks exist: the active skill and current step are your primary context. If no CC Tasks: no multi-step skill is running.

2. Git state

git branch --show-current
git status --porcelain | head -10
git log --oneline -5
git stash list 2>/dev/null | head -3
git worktree list
git branch --merged main

Extract:

• Current branch → maps to task convention (feat/t-NNN-*, fix/t-NNN-*, etc.)
• Uncommitted changes → work in progress that needs committing or stashing
• Recent commits → what was just accomplished
• Stashes → forgotten work-in-progress
• Worktrees → parallel work streams from git worktree list; cross-check each worktree's branch against git branch --merged main. If any worktree branch appears in the merged list, surface a warning: ⚠ Worktree <path> is on a merged branch — run \git worktree remove ` to clean up.`