vibe-architect-os

What it does

The strategic design pass that runs before the PRD on any new build. Surfaces where the app should act automatically, not just what a user clicks, so the agentic layer gets designed in from day one instead of bolted on after the fact.

How it works

Five phases, one question at a time.

Capture the Idea: one sentence: what it is, who it's for, what problem it solves.

Identify Agentic Opportunities: the core phase: where should something happen without you triggering it, does it need to react to an external event, should anything run on a schedule, what external tools does it need to reach. Each answer gets labeled with a pattern: webhook, cron, mcp, automation, claude-api.

Design the Agentic Architecture: each confirmed opportunity becomes a TRIGGER → HANDLER → ACTION → OUTPUT map.

Stack Recommendation: a default stack (Next.js, Vercel, Supabase or Neon, Clerk, Make/Zapier, MCP, Claude API) with a one-sentence reason per choice, flagging anywhere the agentic layer forces a specific pick.

The Brief: everything compiles into a single copy-paste-ready document that hands directly to prd-assistant.

Try it

I want to build [app idea, one sentence] for [who it's for] to solve [what problem].
Before we write a PRD, walk through where this app should act automatically without me
triggering it? Does it need to react to external events, run on a schedule, or reach
external tools? Map each one as trigger → handler → action → output, then recommend a
stack, and compile it all into one Agentic Architecture Brief.

When to reach for it

The very first step of any new build, before the PRD, before Claude Code, before anything else.