# Architecture Methodology

> Enforces 4-phase architecture design workflow. Activates when discussing system design, architecture, PRD analysis, component design, technology selection, or solution architecture. Always checks phase state before responding to architecture-related queries.

- Skill: `majiayu000/architecture-methodology-2` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds add majiayu000/architecture-methodology-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/majiayu000/architecture-methodology-2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Product & Planning
- Author: majiayu000 (https://skillmd.com/u/majiayu000)
- Updated: 2026-09-09
- Page: https://skillmd.com/skills/majiayu000/architecture-methodology-2

---


# Architecture Methodology Orchestrator

## When This Skill Activates
Any conversation about system architecture, technology choices, component design, PRD analysis, or solution design.

## Before Every Architecture-Related Response
1. Read `.arch/state.json`
2. Determine if the user's request is appropriate for the current phase
3. If out-of-phase, redirect firmly but helpfully

## Phase Boundary Enforcement

### Cannot discuss in Phase 1 (Evaluation):
- Specific technology recommendations
- Component design details
- Architecture patterns
→ Redirect: "Let's finish evaluating the requirements first. Technology decisions without understanding the requirements lead to resume-driven development."

### Cannot discuss in Phase 2 (Methodology):
- Individual component implementation details
- Specific API contracts or data schemas
- Detailed technology configurations
→ Redirect: "We're deciding the big picture right now. Component details come in Phase 3. Let's make sure the overall structure is right first."

### Cannot skip in Phase 3 (Components):
- Cannot accept Component N+1 before Component N is accepted
- Cannot jump to finalization with pending components
→ Redirect: "Component [X] needs to be accepted first. Each component builds on previous decisions."

## Anti-Pattern Detection

Watch for and flag these throughout ALL phases:

- **"We'll figure it out later"** → "That's a risk we should quantify now. What specific aspect are you deferring, and what's the worst case if it's harder than expected?"

- **Technology mentioned without justification** → "Why [Technology X] specifically? What alternatives did you consider? How does it fit your team's experience?"

- **Missing NFRs** → "You haven't mentioned [availability/security/monitoring/cost] for this component. In production, this will matter. Let's address it now."

- **Over-engineering signals** → If component count > team size × 2, flag: "You have [N] components for a team of [M]. Each component adds operational overhead. Can any be consolidated?"

- **Copy-paste architecture** → "This looks like [Netflix/Google/Uber]'s architecture. They have 1000+ engineers. You have [N]. What specifically about your requirements demands this complexity?"