Validate development implementation plans against DRY, YAGNI, and TDD principles.
npx skills add https://github.com/rfxlamia/skillkit --skill validate-plan-rfxlamia
Please help me install this Agent Skill. Skill: validate-plan Source: https://github.com/rfxlamia/skillkit/tree/main/skills/validate-plan Command: npx skills add https://github.com/rfxlamia/skillkit --skill validate-plan-rfxlamia
This Skill rigorously validates development implementation plans against core software engineering principles like DRY, YAGNI, and TDD, preventing costly mistakes and ensuring high-quality execution.
Use the validate-plan skill to review the implementation plan located at 'plans/new-feature.md'.
High-intent search queries and answers about installing and using this skill.
You can validate a plan against DRY and YAGNI by performing gap analysis on the drafted specifications to identify duplicated logic, over-engineering, and anti-patterns. This ensures the development plan adheres to core software engineering best practices before execution begins.
Codebase-aware gap analysis reviews technical specifications to identify missing requirements, architectural inconsistencies, and potential disaster scenarios. It checks the implementation plan against existing codebase structures and test-driven development principles to prevent costly rework.
To check TDD compliance, validate the implementation specifications against test-driven development principles. The analysis identifies missing test coverage and anti-patterns, ensuring execution workflows integrate proper testing methodologies before coding starts.
Run a validation check before starting complex feature execution. Validating the plan early catches architectural inconsistencies, over-engineering, and duplicated logic, saving significant rework by identifying missing requirements beforehand.
Yes, plan validation supports integration with planning and execution workflows. The process reviews drafted implementation plans for best practice adherence, allowing the validated output to feed into downstream development pipelines.
Common anti-patterns include duplicated logic violating DRY, speculative features violating YAGNI, and missing test coverage ignoring TDD. Identifying these gaps in technical specifications prevents architectural inconsistencies and potential disaster scenarios.
mattg101Generate implementation-ready software technical specifications in markdown format.
fabricioctellesAutomate iterative Kiro spec task implementation with self-correction and progress tracking.
JylhisDetect Go vulnerabilities using govulncheck, static analysis, and DREAD scoring.
AshesOfTheUndeadGenerate structured, test-driven implementation plans for software development tasks.
