What problem does it solve?
This Skill solves the problem of architectural drift and fragile implementations by requiring complete design and documentation before any code is written, while using tests as a safety net for pragmatic execution.
Core Features & Use Cases
- Architectural design gates: Forces architecture and documentation to be created before implementation, especially for structural/refactoring decisions.
- Capability preservation: Prevents regressions by ensuring the new design maintains all prior capabilities and granularity (“gold standard baseline”).
- Zero coupling enforcement: Keeps expansion packs/modules independent through explicit coupling validation and configuration-driven integration.
- Multi-agent validation: Requires validation from Product Owner, Architect, and User/stakeholders with documented rationale before structural decisions.
- Use cases: Starting new features, performing large refactors, and making architectural changes that affect module boundaries, data flow, or integrations.
Quick Start
Tell the AI: “For this new feature request, run the Architect-First flow—map the current state, propose A/B/C architectural options with trade-offs, get multi-agent validation, externalize mutable configuration to YAML, define tests and logging, then only proceed to implementation if stop rules are not triggered.”
