Architecture Discipline FAQs

Question 1

How does this skill improve my development workflow?

Accepted Answer

It eliminates 'obvious choice' bias by forcing the evaluation of at least three distinct options with concrete metrics. It shifts focus from simple checklists to deep architectural reasoning, preventing expensive technical debt and retrofitting costs.

Question 2

What does the Architecture Discipline skill do?

Accepted Answer

This skill enforces a rigorous, mandatory seven-step reasoning framework for system design. It ensures that Claude evaluates scalability, explores multiple architectural options, maps ripple effects, and plans for failure modes before any implementation begins.

Question 3

What are the mandatory sections in the reasoning framework?

Accepted Answer

The framework requires a 22+ item TodoWrite covering: Scale Analysis (including 10x growth), Architectural Options, Ripple Effect Analysis, Failure Modes, Observability, Documentation (ADRs/Diagrams), and Migration/Compatibility.

Question 4

When should I use the Architecture Discipline skill?

Accepted Answer

Use it for high-stakes decisions like schema changes, service boundaries, infrastructure shifts, or tech stack choices. A good rule of thumb: use this skill if a wrong decision could result in a 3+ month re-architecture project.

Question 5

Can I skip the analysis for simple architecture questions?

Accepted Answer

The skill is designed to prevent 'quick recommendations.' To skip any requirement, you must provide a specific retrofit date, an allocated budget in engineer-weeks, and a formal risk acceptance plan to ensure the 'simple' solution doesn't break at scale.

Architecture Discipline

Architecture Discipline

주요 기능

사용 사례

주요 기능

사용 사례