What problem does it solve?
Architect-First prevents costly redesigns by forcing complete architecture and documentation before implementation, while ensuring zero coupling and capability preservation through validation and tests.
Core Features & Use Cases
- Architecture and documentation gate: Stop and design fully before writing code, including diagrams, data flows, integration points, and configuration schema.
- Multi-agent validation: Validate structural decisions with PO/Architect/User perspectives and document rationale before proceeding.
- Quality escape hatch with tests: Allow pragmatic or imperfect code only when backed by a defined test plan and observation/logging points.
- Capability preservation & zero coupling: Maintain all prior capabilities (gold standard baseline) and enforce independent expansion-pack/module boundaries, using coupling checks.
Use this skill when you are starting new features, refactoring systems, or making architectural decisions that affect module boundaries, integrations, or long-term maintainability.
Quick Start
Use the architect-first skill when you begin a structural change by writing a complete design and validation package first, then only proceed to implementation after multi-agent sign-off and zero-coupling validation.
