brigade

Brigade (packaged as b2c-app-builder) is a framework that gives AI agents a shared foundation for building complete consumer-app businesses, not just applications. It models a business as a restaurant kitchen with six stations — Prep & Design, Menu Planning, The Hot Line, Front of House, The Pass, and The Office — each representing a stable business responsibility. Core primitives include: - **Capabilities**: Business responsibilities with operation semantics and acceptance criteria (the equipment at a station) - **Providers**: Implementations of specific operations with declared support and limits (the purveyor) - **Recipes**: Configurable creation or operating loops (how you run service) - **Knowledge**: Sourced guidance loaded in bounded amounts (mise en place) - **Evidence**: Observations tied to claims, artifacts, and environments (the plate check at the pass) The system covers six business areas: Opportunity (research users, competitors, demand), Product (define promise, first value, core loop), Experience (identity, onboarding, interaction, accessibility), Engineering (build/release native and web with contracts and verification), Revenue & Growth (subscriptions, acquisition, funnels, attribution), and Learning & Operations (evidence inspection, improvement planning, support, coordination). Usage modes: 1. **Focused task skills** for research, onboarding review, or monetization questions without creating a workspace 2. **Main business skill** for coordinated, durable creation/operation through status, planning, bounded execution, and evidence The CLI (`b2c`) provides commands for workspace creation (`business-create`), status (`business-status`), planning (`business-plan`), catalog discovery (`catalog`), and composition preview (`compose`). An MCP server enables integration with Claude Code, Cursor, and Codex. Mobile app operation is a built-in capability using simulator tooling or alternative providers. The project is MIT licensed, not yet published to npm (install via source checkout), and includes a complete extension system where first-party and community extensions pass the same conformance suite. The Tuck example demonstrates real app/web captures with provenance. Current status: source-backed knowledge, workflow catalog, CLI, local MCP, workspace creation, planning, bounded execution, review, evidence, composition preview, and local package import are implemented; a benchmark-quality consumer business and comparable market reports remain milestones.