skills.rest
tikazyq
tikazyqCOMMUNITY
Explore all skills by this author →
GitHub

overdesign-detect

Detect over-engineering in design documents and generate simplification reports.

5|1|Updated Jan 3, 2026
Search Tags:#documentation#specification#technical debt#design review#simplification#over-engineering
One-click install
npx skills add https://github.com/tikazyq/agentic-spec-forge --skill overdesign-detect
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: overdesign-detect
Source: https://github.com/tikazyq/agentic-spec-forge/tree/main/AGENTIC_SPEC_FORGE/spec_stage_skill/design/overdesign-detect
Command: npx skills add https://github.com/tikazyq/agentic-spec-forge --skill overdesign-detect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill identifies and helps remove unnecessary complexity and implementation details from design documents, ensuring they remain at the appropriate abstraction level and avoid premature technical decisions.

Core Features & Use Cases

  • Detects Over-Engineering: Flags excessive implementation details, code snippets, or overly technical jargon in design artifacts.
  • Generates Actionable Feedback: Provides a clear list of over-designed elements and suggests moving them to implementation details or removing them.
  • Ensures Design Purity: Helps Product Managers and Business Analysts maintain a business-focused language in design documents, crucial before constraint validation.

Quick Start

Run overdesign-detect on all design documents to identify and suggest simplifications for any overly technical content.

Frequently Asked Questions about overdesign-detect

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect over-engineering in design documents?▼

Detect over-engineering in design documents by scanning artifacts for implementation details and excessive technical jargon. This process flags overly technical content, ensuring design specs remain at the appropriate abstraction level before constraint acceptance.

What is the best way to remove implementation details from a design specification?▼

Remove implementation details from a design specification by generating an actionable report that lists over-designed elements. This report provides recommendations to either simplify the content or relocate it to implementation phases.

Why does my design document contain too much technical jargon?▼

Design documents contain too much technical jargon when abstraction boundaries are crossed during authoring. Scanning for excessive technical terms and code snippets helps maintain a business-focused language suitable for Product Managers.

Can I check L1, L2, and L3 design levels for abstraction boundary violations?▼

Yes, you can check L1, L2, and L3 design levels for abstraction boundary violations. The detection process ensures adherence to these specific abstraction boundaries before constraint acceptance is initiated.

When do I need to scan for over-designed content in technical artifacts?▼

Scan for over-designed content in technical artifacts before constraint validation. This ensures that premature technical decisions and unnecessary complexity are removed, maintaining design purity for business analysts.

Related Skills

Explore More Product & Management Skills→
ollieb89ollieb89

openclaw-orchestrate

Orchestrate multi-tier AI agent interactions with L1/L2/L3 directive routing.

Community
Advanced
AratKruglikAratKruglik
150

ddd-strategic-design

Design DDD strategic artifacts including subdomains, bounded contexts, and ubiquitous language.

Community
Advanced
Euraika-LabsEuraika-Labs
14

team-ui

Orchestrate multi-role UI workflows for game projects from specification to polish.

Official
Advanced
msalganikmsalganik

review-spec

Review multi-file technical specifications for inconsistencies, gaps, and over-engineering.

Community
Basic