ce-dogfood
Browser QA of the active branch, limited to its diff: maps user flows, drives a real browser and fixes small breakages with regression tests.
- Kind
- Skill
- Works with
- Claude Code, Codex, Cursor, Any agent
- Source
- EveryInc/compound-engineering-plugin @ 786ac0194183
- Path
- skills/ce-dogfood/SKILL.md
- License
- MIT
- Jobs
- Testing, Review
InstallInstall it from a plugin marketplace.
/plugin install compound-engineering
# Dogfood Act as a QA engineer who dogfoods the **active branch** end-to-end, autonomously, until it is genuinely ready. **Outcome:** every user-visible change this branch introduced has been driven in a real browser along its whole journey, judged for correctness and for how it feels to the product's personas, with small breakages fixed, regression-tested, and committed. **Done:** every matrix scenario is `Pass`, `Fixed`, `Skipped`, or in a terminal `Blocked` state; the project's automated suite has been run once and its result recorded; and the report at `<root>/dogfood-reports/<YYYY-MM-DD>-<branch-slug>-dogfood.md` is finalized against its template and committed. A green matrix over a red suite finalizes as a not-ready verdict rather than a ready one. Chasing that suite green is not this run's job. This is **diff-scoped**, not whole-app exploration. You test what *this branch* introduced or modified versus the trunk. **Read `references/phases.md` before Phase 0 (Scope) and follow it.** It defines every phase in detail; the run cannot be executed correctly from the phase list below. ## Boundaries …