founder-os

Plugin founder-os from marketplace lab-launchpad-ai-sdk in rahlplx/Lab-LaunchPad-AI-SDK. Commands read from the repo's manifest — 1 month ago.

Skills (16)

• audit-summary

  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

• debug-seb

  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

• founding-prompt

  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.

• git-save-points

  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.

• handoff

  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-de

• hire-agent

  Decide which engineering role (PM/Design/Frontend/Backend/DevOps/QA) the agent should act as for a given task, using the HIRE framework (Hire the right agent, Instruct clearly, Review output, Evolve with feedback). Use before instructing the agent on any non-trivial task, and whenever work switches

• integrate-service

  Connect a third-party service (payments, email, storage, analytics) using the PLUG framework (Pick/Look/Use AI/Guard the keys), preferring the MCP servers already configured in .mcp.json over ad hoc API wiring. Use whenever /map-architecture identifies an integration, or the founder asks to "add" a

• map-architecture

  Map a product into Pages/Database/Auth/API/Integrations blocks using the LEGO framework, then write the results into PRD.md's Data model and Integrations sections. Use after /founding-prompt and before first prototyping, and again whenever a major feature changes the data model.

• multi-model-review

  Run the 3-Layer Review (you: visual/functional check, a second AI: code quality, a security-focused AI: vulnerabilities), and be explicit about the limits of same-model-family review. Use after any major feature; for anything security-critical, pair with /security-audit.

• refactor-safely

  Diagnose whether an area of code has real technical debt using the smell-test warning signs, then refactor it safely without changing user-facing behavior. This is the fuller diagnostic version of /refactor-cleanup — use this when it's unclear whether or where to refactor, not just to run the cleanu

• security-audit

  Audit the product against the LOCK checklist (Login secure, Only authorized access, Clean inputs, Keys hidden), cross-checked against policy.json's actually-enforced rules, not just the abstract framework. Run before any deploy (pair with /ship-checklist), monthly, and whenever /multi-model-review f

• ship-checklist

  Run the SHIP checklist (Stable, Hidden secrets, Inputs validated, Performance) immediately before every deploy, using the agent's own tools directly. Use right before any git push to a branch that auto-deploys, after /verify-path and /security-audit have already passed.

• show-reference

  Calibrate the agent's output using founder-provided visual references (screenshots, competitor flows, brand examples) via the SHOW method (Sample, Highlight, Omit, Want), rather than describing desired output in words alone. Use whenever a founder has or can get a reference, before /add-page or othe

• validate-demand

  Sanity-check whether a product idea has real demand before any prompting or building starts, using the Jobs-to-be-Done framing and lightweight market-research techniques. Use this first, before /founding-prompt.

• verify-path

  Gate any "this is done" claim behind actual evidence using the PATH walkthrough method (Primary flow, Alternate paths, Transitions, Happy+Hostile testing), since the founder cannot read the code to verify it themselves. Run this before presenting any feature as complete, and before /ship-checklist.

• weekly-plan

  Turn an unstructured backlog into a weekly plan of 3 features to build, 3 bugs to fix, and 3 users to talk to, using the 3-3-3 method. Use at the start of each work week, especially when the founder has more ideas than a week can hold.

Slash commands (5)

• /founder-os:add-page

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

• /founder-os:build-feature

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

• /founder-os:fix-bug

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

• /founder-os:refactor-cleanup

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

• /founder-os:review-code

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

Subagents (3)

• code-critic

  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.

• qa-tester

  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.

• security-reviewer

  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.

MCP servers (8)

• supabase

  connects to: https://mcp.supabase.com/mcp?read_only=true

• stripe

  connects to: https://mcp.stripe.com

• vercel

  connects to: https://mcp.vercel.com

• sentry

  connects to: https://mcp.sentry.dev/mcp

• posthog

  connects to: https://mcp.posthog.com/mcp

• playwright

  runs: npx -y @playwright/[email protected]

• github

  connects to: https://api.githubcopilot.com/mcp/

• context7

  runs: npx -y @upstash/[email protected]

Hooks (4)

• PreToolUse

  node ${CLAUDE_PLUGIN_ROOT}/bin/policy-check.js

• PreToolUse

  node ${CLAUDE_PLUGIN_ROOT}/bin/policy-check.js

• PostToolUse

  ${CLAUDE_PLUGIN_ROOT}/bin/doc-sync.sh

• Stop

  ${CLAUDE_PLUGIN_ROOT}/bin/verify-gate.sh

Similar plugins