AgentSkillsCN

explain-approach

在实施前阐明架构设计思路，并充分权衡利弊、探讨多种备选方案。

SKILL.md
--- frontmatter
name: explain-approach
description: Explain architectural approach before implementation with trade-offs and alternatives
argument-hint: [PR number | file/component | issue number | "current work"]

Before we proceed with $ARGUMENTS, explain the architectural approach:

Step 1: UNDERSTAND THE CONTEXT

  • •If $ARGUMENTS is a PR number, fetch and analyze the changes
  • •If $ARGUMENTS is a file/component, examine the current implementation
  • •If $ARGUMENTS is an issue/ticket number, understand the requirements
  • •If $ARGUMENTS is "current work", look at recent changes

Step 2: ARCHITECTURAL EXPLANATION

  1. •What architectural patterns does this use/suggest?
  2. •Three different ways we could solve it (simple, scalable, elegant)
  3. •Trade-offs of each approach
  4. •Why the current/proposed approach makes sense
  5. •What could go wrong with this approach
  6. •How this fits into the broader system

Format as a Sandy Metz-style explanation with clear principles.