overdesign-detect

tikazyq's avatarfrom tikazyq

检测设计文档中的过度设计（实现细节、技术术语过多），生成过度设计清单和精简建议。当准备CONSTRAINT验收前使用，避免边界合规验收失败。

⭐0stars🔀0forks📁View on GitHub🕐Updated Jan 3, 2026
[Architecture Design]

When & Why to Use This Skill

The overdesign-detect skill is an automated auditing tool designed to maintain the integrity of software architecture documentation. It identifies excessive implementation details—such as embedded code snippets, SQL queries, and low-level technical jargon—that often clutter high-level design artifacts. By generating a comprehensive over-design checklist and actionable simplification suggestions, it ensures that design documents remain focused on business logic and architectural boundaries, helping teams pass constraint acceptance reviews and maintain professional documentation standards.

Use Cases

  • Pre-Compliance Auditing: Use the tool before official architecture reviews to identify boundary violations and implementation leaks, preventing rejection during CONSTRAINT acceptance phases.
  • Documentation Refinement: Automatically scan ARCH or ADR artifacts to extract implementation-specific details (like specific algorithms or CLI commands) that should be moved to implementation guides rather than design docs.
  • Abstraction Governance: Monitor the density of technical terminology across different project levels (L1/L2/L3) to ensure that the documentation remains accessible to PMs, BAs, and other non-developer stakeholders.
nameoverdesign-detect
description检测设计文档中的过度设计（实现细节、技术术语过多），生成过度设计清单和精简建议。当准备CONSTRAINT验收前使用，避免边界合规验收失败。
stageDESIGN
level_supported[L1, L2, L3]

overdesign-detect: 过度设计检测

描述

检测设计文档中的过度设计（实现细节、技术术语过多），生成过度设计清单和精简建议。当准备 CONSTRAINT 验收前使用，避免边界合规验收失败。

适用场景

  • WORKFLOW_STEP_4 Task S4-2 Round 2：生成 ARCH/ADR 后
  • L1/L2 特定：担心设计包含过多实现细节
  • WORKFLOW_STEP_4 Task S4-5 前：准备 CONSTRAINT 验收前

输入

  • design/ 目录（所有 artifacts）
  • 当前级别（L1/L2/L3）

输出

  • 过度设计检测报告（markdown）
  • 过度设计项清单（哪些 artifact 包含实现细节）
  • 精简建议（建议删除或转移到 implementation/）

执行策略

  1. 扫描 design/ 目录所有 artifacts
  2. 检测禁止内容：
    • 代码片段（function/class 定义）
    • SQL 查询
    • 命令行命令
    • 具体算法实现（如"使用快速排序"）
  3. 检测技术术语占比：
    • 统计技术术语（数据库表名、API endpoint、具体库名等）
    • 计算技术占比（应 ≤20% for L1/L2，≤40% for L3）
  4. 生成过度设计清单 + 精简建议

价值

  • SPEC 组织：提前发现边界违规，避免 CONSTRAINT 验收失败
  • PM/BA：确保设��保持业务语言为主
  • Dev：明确设计边界（设计不应包含实现细节）