skills.rest
evanklem
evanklemCOMMUNITY
Explore all skills by this author →
GitHub

evanflow-improve-architecture

Identify architectural friction and propose one refactor plan per opportunity.

417|18|Updated Apr 27, 2026
Search Tags:#architecture#refactoring#code-review#system-design#modular-design#deletion-test#evanflow
One-click install
npx skills add https://github.com/evanklem/evanflow --skill evanflow-improve-architecture
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: evanflow-improve-architecture
Source: https://github.com/evanklem/evanflow/tree/main/skills/evanflow-improve-architecture
Command: npx skills add https://github.com/evanklem/evanflow --skill evanflow-improve-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architects and engineers often struggle to recognize when existing code structure harms maintainability. This Skill provides a disciplined approach to surface architectural friction and steer refactors using a structured workflow.

Core Features & Use Cases

  • Read Context First from CONTEXT.md and ADRs to respect domain language and prior decisions.
  • Identify Candidates by tracing friction points, complexity, and modular boundaries.
  • Apply the Deletion Test to determine if a candidate module is bloating the system or if it warrants deeper work.
  • Present Opportunities as isolated evanflow-writing-plans cycles with clear hand-offs.

Quick Start

Review CONTEXT.md and ADRs to identify a friction point, then propose a single focused evanflow-writing-plans cycle to address it.

Frequently Asked Questions about evanflow-improve-architecture

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

FAQPage Schema
How do I identify architectural friction and refactor opportunities in my codebase?▼

To identify architectural friction, trace complexity and modular boundaries across candidate modules, then apply the deletion test and seams analysis to surface actionable refactor opportunities while respecting prior decisions.

What is the deletion test in software architecture and how does it work?▼

The deletion test is an architectural evaluation method used to determine if a candidate module is bloating the system or warrants deeper work by analyzing whether its removal exposes unnecessary complexity or valid structural dependencies.

How do I plan a focused code refactoring cycle without disrupting the system?▼

Plan a focused code refactoring cycle by proposing a single isolated evanflow-writing-plans cycle per identified opportunity, ensuring clear hand-offs and limiting the scope to exactly one refactor per plan to avoid disruption.

How do I respect prior architectural decisions when proposing a system redesign?▼

To respect prior architectural decisions during system redesign, consult CONTEXT.md and docs/adr/ directories first to understand domain language and existing constraints before identifying friction points or proposing modular refactoring.

When do I need to analyze deep-modules and seams for a codebase refactoring?▼

You need to analyze deep-modules and seams when evaluating modular boundaries to identify structural friction, using this vocabulary to isolate complexity hotspots and determine where refactoring will most improve system maintainability.

Does this approach work for large legacy code refactoring or only new system design?▼

This refactoring approach works for existing codebases by reading context from ADRs to respect prior decisions, tracing friction points in current modular boundaries, and proposing isolated cycles suitable for legacy system maintenance.

Related Skills

Explore More Software Engineering Skills→
ralvarezdevralvarezdev
3

improve-codebase-architecture

Identify shallow modules and propose seam-based interface deepening refactors.

Community
Advanced
juniorfontenelejuniorfontenele

task-planner

Generate structured implementation plans from natural language task descriptions.

Community
Advanced
JeromyJSmithJeromyJSmith
3

improve-codebase-architecture

Identify shallow modules and propose interface-focused refactoring candidates.

Community
Advanced
guiledoguiledo

sdd-tdd-workflow

Plan and enforce SDD/TDD workflows with Red-Green-Refactor cycles.

Community
Advanced