architect-first

Enforce complete design and documentation before coding with multi-agent validation.

Updated Aug 27, 2026

Search Tags:#architecture #documentation #validation #risk-mitigation #design-first #zero-coupling

Ready to run

npx skills add https://github.com/fabioaap/Prototipacao-Adsmagic --skill architect-first-fabioaap

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architect-first
Source: https://github.com/fabioaap/Prototipacao-Adsmagic/tree/main/.claude/skills/architect-first
Command: npx skills add https://github.com/fabioaap/Prototipacao-Adsmagic --skill architect-first-fabioaap

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires yaml, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Architect-first governance ensures that system design and documentation precede any coding, reducing rework and misalignment across teams.

Core Features & Use Cases

Complete design before implementation and externalize configuration
Multi-agent validation with Product Owner, Architect, and User perspectives
Architecture templates (ADR, architecture diagrams) and risk-mitigation guidance
Use Case: Starting a new feature, map architecture, document decisions, then implement

Quick Start

Map the current architecture and create an Architecture Decision Record before writing any code.

Frequently Asked Questions about architect-first

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

FAQPage Schema

How do I enforce design before code in my software development workflow?▼

To enforce design before code, an architect-first approach requires complete documentation and multi-agent validation before implementation. This reduces rework by ensuring system design is mapped and approved prior to writing any code.

What is the best way to document architecture decisions for new features?▼

The best way to document architecture decisions is by creating an Architecture Decision Record (ADR). This captures the rationale and design choices before implementation, ensuring alignment across teams during feature inception or refactoring.

How does multi-agent validation work for architecture design?▼

Multi-agent validation assesses architecture design from Product Owner, Architect, and User perspectives. This process checks zero-coupling and risk mitigation before coding, ensuring the design meets diverse stakeholder requirements.

Can I use architecture templates for refactoring efforts and major system changes?▼

Yes, you can use architecture templates for refactoring efforts and major system changes. The process applies architecture diagrams, risk assessment, and ADRs to guide the safe evolution of systems and externalize configuration.

Do I need YAML to externalize configuration for architecture documentation?▼

YAML is required as a dependency to support the externalization of configuration. This ensures system configuration is separated from the codebase, aligning with the zero-coupling checks needed for safe architectural evolution.