evolutionary-change

Plan and execute incremental software changes in Kotlin-based Ktor projects.

1|Updated Mar 14, 2026

Search Tags:#architecture #refactoring #quality #kotlin #kanban #evolutionary

Ready to run

npx skills add https://github.com/agnaldo4j/kanban-vision-api-kt --skill evolutionary-change

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: evolutionary-change
Source: https://github.com/agnaldo4j/kanban-vision-api-kt/tree/main/.claude/skills/evolutionary-change
Command: npx skills add https://github.com/agnaldo4j/kanban-vision-api-kt --skill evolutionary-change

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents structural crises, quality degradation, and context loss during system evolution by enforcing incremental, normative changes instead of risky, dramatic refactors.

Core Features & Use Cases

Evolutionary Strategy: Provides a framework to classify changes as Normative, Medium, or Structural, ensuring each intervention is appropriately scoped.
Safety Guardrails: Integrates with project policies to maintain CI health, test coverage, and build stability during development.
Use Case: When planning a technical gap like adding pagination or upgrading a dependency, use this skill to determine if the change is safe to execute immediately or if it requires a formal Architectural Decision Record (ADR).

Quick Start

Use the evolutionary-change skill to evaluate the risk and execution strategy for the proposed GAP-J pagination implementation.

Frequently Asked Questions about evolutionary-change

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

FAQPage Schema

How do I plan incremental refactoring in Kotlin without causing structural degradation?▼

Incremental refactoring prevents structural degradation by classifying changes into Normative, Medium, or Structural scopes. This ensures interventions are appropriately sized, maintaining CI health, test coverage, and build stability throughout the evolution process.

When do I need an Architectural Decision Record for a Ktor dependency upgrade?▼

You need an Architectural Decision Record (ADR) for a Ktor dependency upgrade when the change is classified as Structural. The framework evaluates proposed gaps to determine if they are safe for immediate execution or require formal ADR-driven decision-making processes.

What is the best way to remediate technical debt while maintaining CI/CD safety thresholds?▼

The best way to remediate technical debt while maintaining CI/CD safety thresholds is through incremental, normative changes. This approach enforces safety guardrails that integrate with project policies to preserve test coverage and build stability during execution.

Does this evolutionary change framework work with Kanban workflows for technical debt management?▼

Yes, the evolutionary change framework supports Kanban workflows by providing a structured strategy to classify and execute technical debt remediation. It ensures safe, incremental system improvements that align with continuous delivery constraints.

How do I evaluate if adding pagination to a Ktor project is a safe immediate change?▼

To evaluate if adding pagination is safe, the framework classifies the proposed gap's risk level. It determines whether the implementation is a Normative change safe for immediate execution or a Structural change requiring formal documentation.

Why should I avoid dramatic refactors instead of incremental system improvements?▼

Avoiding dramatic refactors prevents structural crises, quality degradation, and context loss. Incremental system improvements enforce normative changes that maintain compliance with established safety thresholds and prevent structural degradation.