{"kind":"AgentDefinition","metadata":{"namespace":"community","name":"multi-agent-workflow-startup-mvp","version":"0.1.0"},"spec":{"agents_md":"# Multi-Agent Workflow: Startup MVP\n\n\u003e A step-by-step example of how to coordinate multiple agents to go from idea to shipped MVP.\n\n## The Scenario\n\nYou're building a SaaS MVP — a team retrospective tool for remote teams. You have 4 weeks to ship a working product with user signups, a core feature, and a landing page.\n\n## Agent Team\n\n| Agent | Role in this workflow |\n|-------|---------------------|\n| Sprint Prioritizer | Break the project into weekly sprints |\n| UX Researcher | Validate the idea with quick user interviews |\n| Backend Architect | Design the API and data model |\n| Frontend Developer | Build the React app |\n| Rapid Prototyper | Get the first version running fast |\n| Growth Hacker | Plan launch strategy while building |\n| Reality Checker | Gate each milestone before moving on |\n\n## The Workflow\n\n### Week 1: Discovery + Architecture\n\n**Step 1 — Activate Sprint Prioritizer**\n\n```\nActivate Sprint Prioritizer.\n\nProject: RetroBoard — a real-time team retrospective tool for remote teams.\nTimeline: 4 weeks to MVP launch.\nCore features: user auth, create retro boards, add cards, vote, action items.\nConstraints: solo developer, React + Node.js stack, deploy to Vercel + Railway.\n\nBreak this into 4 weekly sprints with clear deliverables and acceptance criteria.\n```\n\n**Step 2 — Activate UX Researcher (in parallel)**\n\n```\nActivate UX Researcher.\n\nI'm building a team retrospective tool for remote teams (5-20 people).\nCompetitors: EasyRetro, Retrium, Parabol.\n\nRun a quick competitive analysis and identify:\n1. What features are table stakes\n2. Where competitors fall short\n3. One differentiator we could own\n\nOutput a 1-page research brief.\n```\n\n**Step 3 — Hand off to Backend Architect**\n\n```\nActivate Backend Architect.\n\nHere's our sprint plan: [paste Sprint Prioritizer output]\nHere's our research brief: [paste UX Researcher output]\n\nDesign the API and database schema for RetroBoard.\nStack: Node.js, Express, PostgreSQL, Socket.io for real-time.\n\nDeliver:\n1. Database schema (SQL)\n2. REST API endpoints list\n3. WebSocket events for real-time board updates\n4. Auth strategy recommendation\n```\n\n### Week 2: Build Core Features\n\n**Step 4 — Activate Frontend Developer + Rapid Prototyper**\n\n```\nActivate Frontend Developer.\n\nHere's the API spec: [paste Backend Architect output]\n\nBuild the RetroBoard React app:\n- Stack: React, TypeScript, Tailwind, Socket.io-client\n- Pages: Login, Dashboard, Board view\n- Components: RetroCard, VoteButton, ActionItem, BoardColumn\n\nStart with the Board view — it's the core experience.\nFocus on real-time: when one user adds a card, everyone sees it.\n```\n\n**Step 5 — Reality Check at midpoint**\n\n```\nActivate Reality Checker.\n\nWe're at week 2 of a 4-week MVP build for RetroBoard.\n\nHere's what we have so far:\n- Database schema: [paste]\n- API endpoints: [paste]\n- Frontend components: [paste]\n\nEvaluate:\n1. Can we realistically ship in 2 more weeks?\n2. What should we cut to make the deadline?\n3. Any technical debt that will bite us at launch?\n```\n\n### Week 3: Polish + Landing Page\n\n**Step 6 — Frontend Developer continues, Growth Hacker starts**\n\n```\nActivate Growth Hacker.\n\nProduct: RetroBoard — team retrospective tool, launching in 1 week.\nTarget: Engineering managers and scrum masters at remote-first companies.\nBudget: $0 (organic launch only).\n\nCreate a launch plan:\n1. Landing page copy (hero, features, CTA)\n2. Launch channels (Product Hunt, Reddit, Hacker News, Twitter)\n3. Day-by-day launch sequence\n4. Metrics to track in week 1\n```\n\n### Week 4: Launch\n\n**Step 7 — Final Reality Check**\n\n```\nActivate Reality Checker.\n\nRetroBoard is ready to launch. Evaluate production readiness:\n\n- Live URL: [url]\n- Test accounts created: yes\n- Error monitoring: Sentry configured\n- Database backups: daily automated\n\nRun through the launch checklist and give a GO / NO-GO decision.\nRequire evidence for each criterion.\n```\n\n## Key Patterns\n\n1. **Sequential handoffs**: Each agent's output becomes the next agent's input\n2. **Parallel work**: UX Researcher and Sprint Prioritizer can run simultaneously in Week 1\n3. **Quality gates**: Reality Checker at midpoint and before launch prevents shipping broken code\n4. **Context passing**: Always paste previous agent outputs into the next prompt — agents don't share memory\n\n## Tips\n\n- Copy-paste agent outputs between steps — don't summarize, use the full output\n- If a Reality Checker flags an issue, loop back to the relevant specialist to fix it\n- Keep the Orchestrator agent in mind for automating this flow once you're comfortable with the manual version\n","description":"A step-by-step example of how to coordinate multiple agents to go from idea to shipped MVP.","import":{"commit_sha":"783f6a72bfd7f3135700ac273c619d92821b419a","imported_at":"2026-05-18T20:06:30Z","license_text":"","owner":"msitarzewski","repo":"msitarzewski/agency-agents","source_url":"https://github.com/msitarzewski/agency-agents/blob/783f6a72bfd7f3135700ac273c619d92821b419a/examples/workflow-startup-mvp.md"},"manifest":{}},"content_hash":[150,221,150,158,155,237,77,76,71,178,84,64,85,125,61,129,64,78,125,72,100,60,120,177,123,156,239,1,63,103,36,172],"trust_level":"unsigned","yanked":false}