bs-architect

Define MVP technical architecture, data schema, API contracts, and ADRs.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/MaxGiu67/plugin-MUCC --skill bs-architect
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bs-architect
Source: https://github.com/MaxGiu67/plugin-MUCC/tree/main/brainstorming/skills/bs-architect
Command: npx skills add https://github.com/MaxGiu67/plugin-MUCC --skill bs-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Converts high-level MVP scope and UX flows into a concrete, implementable technical architecture to avoid ad-hoc decisions and reduce rework during development.

Core Features & Use Cases

  • Defines a recommended technology stack for frontend, backend, database, auth, hosting, and storage with motivations and tradeoffs.
  • Produces a textual architecture diagram, initial data model (entities and relations), API contract (endpoints, methods, auth, request/response shapes), and ADRs documenting key decisions.
  • Use case: take brainstorm/04-mvp-scope.md and brainstorm/05-ux-flows.md and generate brainstorm/06-architecture.md suitable for handoff to engineering and integration into the dev-methodology pipeline.

Quick Start

Generate an MVP technical architecture including stack choices, a textual architecture diagram, an initial data schema, API contracts, and ADR notes using the brainstorm/04-mvp-scope.md and brainstorm/05-ux-flows.md files.

Frequently Asked Questions about bs-architect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I define an MVP-friendly technical architecture from product scope and UX flows?

Defining an MVP-friendly technical architecture requires converting MVP scope and UX flows into stack recommendations, a textual architecture diagram, an initial data schema, API contracts, and ADRs documenting key tradeoffs to ensure production-aware system design.

What should be included in MVP architecture documentation for engineering handoff?

MVP architecture documentation for engineering handoff should include recommended technology stacks with tradeoffs, a textual architecture diagram, entity relationship data mappings, API endpoints with request and response shapes, and ADR entries documenting alternatives.

Can I generate API contracts and ADRs for an MVP without an existing data model?

Generating API contracts and ADRs alongside an initial data model is achieved by processing high-level MVP scope and UX flows, which produces entity relationship mappings and documented architectural decisions simultaneously to prevent ad-hoc design choices.

What is the best way to document technology stack tradeoffs and alternatives for an early-stage product?

Documenting technology stack tradeoffs for an early-stage product is best handled by creating Architecture Decision Records that capture alternatives and motivations for frontend, backend, database, auth, hosting, and storage choices to reduce development rework.

When do I need to create ADRs and an initial data schema for an MVP?

Creating ADRs and an initial data schema for an MVP is needed during early-stage product brainstorming to convert high-level scope into concrete, implementable technical architecture, avoiding ad-hoc decisions before engineering handoff.

Does this approach to system design work for defining both database schemas and API endpoints?

This system design approach works for defining both database schemas and API endpoints by taking MVP scope and UX flows as input to generate entity relationship mappings alongside API endpoints with methods, auth requirements, and request and response shapes.