founder-os

Review recent code for bugs, security issues, and performance problems, reported in plain English with a Red/Yellow/Green rating.

Add a new page/screen to the app, using visual references if available.

Build a new feature into the existing app without breaking what's already working.

Fix a bug using the SEB method (Screenshot, Error message, Before/After) instead of a vague description.

Safely clean up an area of the codebase that's grown messy, without changing behavior.

Code-quality reviewer for founder-os, standing in for /multi-model-review's Layer 2 (bugs, performance, maintainability). Invoked after a feature is built, before /security-audit's dedicated security pass.

PATH-walkthrough test executor for founder-os. Invoked by /verify-path and /ship-checklist to produce PASS/FAIL evidence for a "done" claim, since the founder cannot read code and needs a verdict they can act on, not a description of what should work.

LOCK-checklist security auditor for founder-os. Invoked by /security-audit (and by /multi-model-review as its Layer 3) whenever code touching auth, payment, or user data needs a dedicated security pass rather than a general code review.

Answer "what has the safety layer actually blocked or asked about?" by reading and summarizing the audit log in plain English. Use whenever the founder asks what's been happening, after a stretch of active work, or periodically as a trust check — since the founder can't read policy.json or the hook code themselves.

Diagnose and fix a bug using the SEB method (Screenshot, Error message, Before/After) plus the bisect trick for unknown regressions, gathering real evidence before guessing at a fix. This is the fuller version of /fix-bug — use directly for trickier bugs or when the quick pass doesn't find the cause.

Turn a rough product idea into a structured Founding Prompt using the BRIEF framework, then generate PRD.md, AGENTS.md, and llms.txt from it. Use this once demand is validated (after /validate-demand) and before any prototyping begins.

Commit in small, atomic "save points" (roughly one logical change each) during any non-trivial task, so a broken step is one git revert/reset away from a known-good state instead of losing a whole session's progress. Use during any multi-step build/fix/refactor, not just at the end.

Produce a structured handoff summary before a session ends with unfinished work, right before /compact or /clear, or whenever /hire-agent hands a task to a different role — so in-progress state, what's actually been verified, and what's still open survive the boundary instead of being silently re-derived or dropped.

4 hooks across 3 events