Run a dogfooding mission

Run a Brief dogfooding mission for <user journey>. Use the product the way the target user would, with the normal entry point, permissions, and realistic safe data. Record the expected outcome, each meaningful step, friction, surprises, missing feedback, and where the product or documentation forces hidden knowledge. Capture evidence without exposing private data.

Use Brief to trace each important dogfooding finding into the repo, rules, design system, instrumentation, and docs. Separate product defects, confusing content, missing states, setup friction, and operator error. Rank findings by user impact and confidence, and avoid fixing symptoms when a shared foundation is responsible.

Turn the top dogfooding finding into a bounded mission. Fix the smallest coherent slice, add the missing product or documentation feedback, verify the journey from the user's entry point, review the diff, and save larger findings as clear follow-ups rather than expanding this mission.

Review how Brief performed during this mission. Did context arrive before it was needed? Was the mission bounded correctly? Did fanout, verification, or handoff add signal? Save one proven improvement to the Brief workflow and leave speculative ideas as observations.