bmild-arch

What problem does it solve?

Unstructured or skipped upfront system design leads to unexamined technical trade-offs, schema/API contract drift, and costly rework when implementation reveals missing constraints or misalignment with product requirements. This Skill provides a structured, spec-driven workflow to elicit, document, and validate system architecture decisions, ensuring all technical contracts are implementable and aligned with project constraints.

Core Features & Use Cases

• Multi-Mode Architecture Workflow: Supports three core workflows: greenfield system design for new initiatives, refinement of existing system design documents, and resolution of architecture-owned governance items raised by other cross-functional team personas.
• Trade-Off Enforced Decision Making: Requires all technical decisions to document considered alternatives, explicit trade-offs, and observable implementation consequences, eliminating vague "just use X" technology choices.
• Drift-Protection & Semantic Consistency: Automatically extracts high-impact architecture decisions into ADRs for long-term drift protection, and maintains cross-initiative semantic context to avoid conflicting terminology and assumptions.
• Use Case: For example, when building a new user authentication feature, use this Skill to define the database schema for user credentials, API contracts for login/registration endpoints, service layer methods for authentication logic, and document key trade-offs (e.g., OAuth vs JWT for session management) with clear rationale.

Quick Start

Use the bmild-arch skill to design the backend structure, database schema, API contracts, and technology stack for a new feature or platform, or to resolve open architecture decisions raised by other team personas.