architect-first

Guide structured architecture and documentation before code implementation.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/magisph/rv-adv --skill architect-first-magisph
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: architect-first
Source: https://github.com/magisph/rv-adv/tree/main/.claude/skills/architect-first
Command: npx skills add https://github.com/magisph/rv-adv --skill architect-first-magisph

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill enforces a disciplined development process, ensuring robust architecture and documentation precede implementation, preventing costly rework and technical debt.

Core Features & Use Cases

  • Architectural Design: Guides through structured design and validation before coding.
  • Zero Coupling: Enforces modularity and independence between components.
  • Quality Gates: Implements non-negotiable checks for architecture, documentation, and capability preservation.
  • Use Case: When starting a new microservice, use this Skill to ensure its design is validated by Product, Architecture, and User representatives before any code is written, guaranteeing alignment and technical soundness.

Quick Start

Use the architect-first skill to design and document the architecture for the new user authentication module.

Frequently Asked Questions about architect-first

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

FAQPage Schema
What is architect-first development and when should I enforce complete architecture before implementation?

Architect-first development is a philosophy enforcing complete architecture and documentation before code implementation. You should use it when starting new microservices to prevent costly rework, mitigate risks, and ensure structural design is validated by Product, Architecture, and User representatives.

How do I enforce zero coupling and modularity between software components during design?

To enforce zero coupling and modularity, you must guide your structured design through validation scripts and detailed checklists. This ensures independence between components and passes non-negotiable quality gates for architecture, documentation, and capability preservation before coding begins.

Does the architect-first process require pytest for quality gate validation scripts?

Yes, the architect-first process requires pytest as a dependency to run its validation scripts. These scripts enforce non-negotiable quality gates and support multi-agent validation for structural decisions, ensuring capability preservation and adherence to the development process.

What is the best way to validate architectural design and mitigate structural risks before coding?

The best way to validate architectural design is using structured design checklists and multi-agent validation. This approach enforces zero coupling and capability preservation through quality gates, ensuring technical soundness and alignment across representatives before any code is written.

Limitations of skipping documentation and architecture validation in the development process?

Skipping documentation and architecture validation leads to costly rework and technical debt. Without enforcing quality gates and zero coupling during the development process, components lose independence, and structural decisions lack the multi-agent validation needed to guarantee technical soundness.