Architecture Fitness Function Designer

When to Use

You need to create automated, objective mechanisms that verify your architecture characteristics are maintained over time. Typical triggers:

• The user has identified architecture characteristics (scalability, deployability, testability, etc.) but has no automated way to verify them
• The user's architecture decisions are being violated without detection -- code is drifting from the intended design
• The user wants to enforce structural rules (layer dependencies, package access, no circular dependencies)
• The user wants CI/CD pipeline gates that prevent architecture degradation
• The user is concerned about architecture erosion -- decisions made months ago are no longer reflected in the code
• The user mentions chaos engineering, ArchUnit, NetArchTest, or architectural compliance testing

Before starting, verify:

• Are the target architecture characteristics already identified? (If not, invoke the architecture-characteristics-identifier skill first)
• Does the user have a CI/CD pipeline where fitness functions can be integrated?
• What technology stack is in use? (This determines which fitness function tools are available)

Context & Input Gathering