architect-first

Enforce architecture documentation and design before code implementation.

Updated May 7, 2026

Search Tags:#documentation #validation #yaml #modularity #risk-mitigation #design-first #architectural

Ready to run

npx skills add https://github.com/Andre-cardia/nivel-ia --skill architect-first-andre-cardia

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architect-first
Source: https://github.com/Andre-cardia/nivel-ia/tree/main/.claude/skills/architect-first
Command: npx skills add https://github.com/Andre-cardia/nivel-ia --skill architect-first-andre-cardia

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 enforces that architecture and documentation precede coding to prevent scope creep, misaligned implementations, and fragile systems.

Core Features & Use Cases

Enforces an "Architect-First" approach before coding, ensuring complete design and documentation.
Provides a framework for multi-agent validation, architecture decision records, and risk mitigation.
Promotes zero coupling through YAML-externalized configuration and modular expansion packs.

Quick Start

Document the architecture and governance steps first, then implement according to the validated plan.

Frequently Asked Questions about architect-first

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

FAQPage Schema

How do I enforce architecture documentation before coding to prevent scope creep?▼

To enforce architecture documentation before coding, you must complete structural design, governance steps, and risk mitigation planning first. This approach prevents scope creep and misaligned implementations by validating the plan before any code is written.

What is a design-first approach for architectural decisions and how does it work?▼

A design-first approach for architectural decisions mandates that complete design and documentation precede implementation. It works by applying multi-agent validation and architecture decision records to guarantee quality and prevent fragile systems.

Can I use YAML configuration to prevent coupling in modular software design?▼

Yes, you can use YAML-externalized configuration to prevent coupling in modular software design. This approach promotes zero coupling by separating configuration from code and enabling modular expansion packs.

Do I need risk mitigation planning for architecture decision records?▼

Yes, risk mitigation planning is a required prerequisite for architecture decision records. It ensures that structural decisions are validated against potential risks before implementation begins, guaranteeing system quality.

What's the best way to validate multi-agent architecture plans before implementation?▼

The best way to validate multi-agent architecture plans is to apply a framework that enforces prerequisites like complete design, architecture documentation, and risk mitigation. This ensures validated plans precede any coding effort.

When should I not use a design-first approach for software architecture?▼

You should not use a design-first approach when rapid prototyping takes priority over structural stability. If a project requires immediate code output without governance or risk mitigation planning, enforcing architecture documentation first will stall delivery.