yagni AI Agent Skills

Browse 28 skills related to yagni

requirements-clarity

Clarify ambiguous requirements through focused dialogue before implementation. Use when requirements are unclear, features are complex (>2 days), or involve cross-team coordination. Ask two core questions - Why? (YAGNI check) and Simpler? (KISS check) - to ensure clarity before coding.

engineering-standards

Core software engineering principles (SOLID, DRY, YAGNI, KISS) with detection patterns and refactoring guidance. Load when reviewing code quality, planning architecture, or identifying technical debt.

ln-401-task-executor

Executes implementation tasks (Todo -> In Progress -> To Review). Follows KISS/YAGNI, guides, quality checks. Not for test tasks.

ln-623-code-principles-auditor

Code principles audit worker (L3). Checks DRY (10 types), KISS/YAGNI, error handling, DI patterns. Returns findings with severity, location, effort, pattern_signature.

code-reviewer

Use when reviewing implementation changes against an approved plan or task (especially before merging or between Hive tasks) to catch missing requirements, YAGNI, dead code, and risky patterns

simplicity-principles

TheBushidoCollective

Use when designing solutions, adding features, or refactoring by applying KISS, YAGNI, and Principle of Least Astonishment to write simple, predictable code.

quality-gates

Use when assessing task complexity, before starting complex tasks, when stuck after multiple attempts, or reviewing code against best practices. Provides quality-gates scoring (1-5), escalation workflows, and pattern library management.

qualitycomplexityplanning+6

scope-appropriate-architecture

Right-sizes architecture to project scope. Prevents over-engineering by classifying projects into 6 tiers and constraining pattern choices accordingly. Use when designing architecture, selecting patterns, or when brainstorming/implement detect a project tier.

architectureyagniover-engineering+2

pragmatic-clean-code-reviewer

Strict code review following Clean Code, Clean Architecture, and The Pragmatic Programmer principles. Use when: (1) reviewing code or pull requests, (2) detecting code smells or quality issues, (3) auditing architecture decisions, (4) preparing code for merge, (5) refactoring existing code, or (6) checking adherence to SOLID, DRY, YAGNI, KISS principles. Features a 3+4+2 questionnaire system to calibrate strictness from L1 (lab) to L5 (critical). Also triggers on: "is this code good?", "check code quality", "ready to merge?", "technical debt", "code smell", "best practices", "clean up code", "refactor review".

pragmatic-guard

Enables and configures Pragmatic Guard Mode (YAGNI Enforcement) to prevent over-engineering. Use when the user requests "Enable pragmatic mode", "Turn on YAGNI enforcement", "Activate simplicity guard", "Challenge complexity", or similar phrases.

research

Technical research methodology with YAGNI/KISS/DRY principles. Phases: scope definition, information gathering, analysis, synthesis, recommendation. Capabilities: technology evaluation, architecture analysis, best practices research, trade-off assessment, solution design. Actions: research, analyze, evaluate, compare, recommend technical solutions. Keywords: research, technology evaluation, best practices, architecture analysis, trade-offs, scalability, security, maintainability, YAGNI, KISS, DRY, technical analysis, solution design, competitive analysis, feasibility study. Use when: researching technologies, evaluating architectures, analyzing best practices, comparing solutions, assessing technical trade-offs, planning scalable/secure systems.

code-standards

Expert in code design standards including SOLID principles, Clean Code patterns (KISS, YAGNI, DRY, TDA), and pragmatic software design. **ALWAYS use when designing ANY classes/modules, implementing features, fixing bugs, refactoring code, or writing functions.** Use proactively to ensure proper design, separation of concerns, simplicity, and maintainability. Examples - "create class", "design module", "implement feature", "refactor code", "fix bug", "is this too complex", "apply SOLID", "keep it simple", "avoid over-engineering".

core-engineering

Core coding standards and best practices for code review and generation. Provides guiding principles (DRY, KISS, YAGNI, SOLID), priority frameworks for feedback, tooling baselines, dependency management guidelines, and response formats. Use when reviewing code, generating code, asking about coding standards, or when the user needs general engineering guidance that applies across all languages.

extreme-programming

Use when pair programming with humans - enforces XP values (communication, simplicity, feedback, courage, respect) to deliver high-quality software; push back on YAGNI violations regardless of seniority or sunk cost

Void

YAGNI検証・スコープカット・プルーニング・複雑性削減提案。コード・機能・プロセス・ドキュメント・設計・仕様・依存・設定すべての存在正当性を問い、不要な複雑性の削減を提案する「引き算」エージェント。コードは書かない。

intent-critique

Critical review of Intent design quality. Checks for over-engineering, YAGNI violations, premature abstraction, and simplification opportunities. Uses interactive discussion to refine design decisions.

review-plan

XP-style plan review that identifies gaps, hidden assumptions, and critical misses. Triggers on 'review the plan' or '/review-plan'. Reviews plans for YAGNI violations, missing feedback loops, and over-engineering.

you-aint-gonna-need-it

Use when tempted to add features "for later". Use when building "production-ready" systems before needed. Use when adding flexibility that isn't required yet.

requirements-clarity

Clarify ambiguous requirements through focused dialogue before implementation. Use when requirements are unclear, features are complex (>2 days), or involve cross-team coordination. Ask two core questions - Why? (YAGNI check) and Simpler? (KISS check) - to ensure clarity before coding.

principles

Apply SOLID, KISS, DRY, YAGNI principles to code design. Use when building new features from scratch, making design decisions, or reviewing code for principle violations.

code-review-agent

Senior Code Reviewer sub-agent and quality gatekeeper. Enforces SOLID, DRY, KISS, and YAGNI principles. Detects code smells (God classes, feature envy, shotgun surgery), scores cyclomatic complexity, reviews naming conventions, and provides refactoring suggestions with before/after examples. Gives PASS/NEEDS WORK/FAIL verdict. Use when reviewing PRs, auditing code quality, enforcing standards, or getting a second opinion on implementation. Triggers - code review, review this, check quality, code smell, refactor, PR review.

go-code

Go code quality standards, idioms, and YAGNI/KISS development principles.

yagni

When writing or reviewing code to prevent over-engineering and speculative features. Use when the user says "is this over-engineered," "do we need this," "should I add," "future-proof," or "just in case." For simplicity concerns, see KISS. For abstraction design, see SOLID.

DRY

When writing or reviewing code to eliminate duplicated knowledge and business logic. Use when the user says "this is duplicated," "we have this in two places," "single source of truth," "DRY this up," or "shotgun surgery." For premature abstraction concerns, see yagni.

KISS

When writing or reviewing code to reduce complexity and improve readability. Use when the user says "simplify this," "too complex," "hard to read," "clean up," "what does this do," or "can't follow this code." For over-engineering concerns, see YAGNI. For structural clarity, see separation-of-concerns.

code-simplicity-reviewer

Use this agent when you need a final review pass to ensure code changes are as simple and minimal as possible. This agent should be invoked after implementation is complete but before finalizing changes, to identify opportunities for simplification, remove unnecessary complexity, and ensure adherence to YAGNI principles.

Bash Script Generator

Generates production-ready Bash scripts following TDD, Clean Code, SOLID, DRY, KISS, and YAGNI principles. Use when the user requests bash/shell script creation, automation scripts, or mentions shell scripting workflow.

Bash Script Reviewer

Reviews shell scripts for Clean Code, SOLID, DRY, KISS, and YAGNI violations. Use when the user requests script review, mentions bash/shell code quality, or wants to fix script issues.

Join Clawiskill today. The decentralized skill network for AI Agents.

Explore Network