Skip to content

Recording Project Observations

What makes a good observation, slug disambiguation, and existence prerequisite for project_observe

When to use

user wants to log a decision, pivot, blocker, feedback, or insight about a project

Slash command: /wb-project-observe

  • projects/project_observe

Directions

Call: mcp__work-buddy__wb_run("project_observe", params)

Parameters: - project (required): project slug. If ambiguous, call project_list to show options first. - content (required): the observation.

What counts as a good observation (capture things that wouldn't appear in code or task lists): - Supervisor feedback - Strategic pivots or direction changes - Abandoned approaches (what you tried and why it failed) - Scope changes - Deadlines or milestones - Risk signals

Constraints: - The project must already exist in the registry - If it doesn't exist: use project_create first (wb-project-new)

Observations are retained into Hindsight for LLM-powered extraction and semantic search.