메뉴
Lead effective architecture reviews. Manage discussions, surface disagreements, build consensus, document decisions. Use when conducting reviews or running architecture forums.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
SOC 직업 분류 기준
Identify and avoid common architectural mistakes. Recognize patterns of failure. Use when reviewing designs or learning from mistakes.
Practice architectural design with structured problems. Time-limited design challenges. Use for skill development, interviews, team exercises.
Reference catalog of proven architecture patterns. Know when to apply each pattern, tradeoffs, and examples. Use as reference when designing systems.
Prepare for architecture interview questions and scenarios. Practice system design, tradeoff discussions, communication. Use for career development and interview readiness.
Conduct comprehensive system architecture evaluation. Assess design quality, technical debt, operational readiness, scalability. Use when auditing existing systems.
Coach engineers on architecture and design. Provide feedback, guide learning, support growth. Use when mentoring junior architects or senior engineers.
| name | architecture-review-facilitation |
| description | Lead effective architecture reviews. Manage discussions, surface disagreements, build consensus, document decisions. Use when conducting reviews or running architecture forums. |
Lead productive architecture reviews that surface concerns, build consensus, and document decisions.
You are facilitating architecture reviews. Create safe environment for questioning. Surface disagreements productively. Drive to decision. Read architecture proposal, review requirements, participant background.
Based on facilitation and decision-making research:
Prepare:
Start: "We're here to review [architecture]. Goal is solid decision, not agreement. All perspectives welcome."
Present: Proposer presents problem, solution, trade-offs. 15-20 minutes. No interruptions yet.
Clarify: "What questions help you understand the proposal?" Not criticism, genuine questions.
Evaluate: "What are strengths? What concerns do you have?" Go around table; every voice heard.
Resolve: Address concerns. "That's a real risk. How do we mitigate it?" Adjust design or document risk as accepted.
Decide: "Based on discussion, I'm approving this with conditions: [list]. We'll revisit risk [X] in 2 weeks."
Document: Approved, conditions, open risks, next steps. Send within 24 hours.
