AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Fitness Function Design

skill-sethdford-claude-skills-fitness-function-design · by sethdford

Design metrics that measure architecture health (coupling, modularity, scalability). Automate fitness function checks in CI/CD. Use when establishing quality gates or measuring architectural degradation.

No reviews yet
0 installs
34 views
0.0% view→install

Install

$ agentstack add skill-sethdford-claude-skills-fitness-function-design

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-sethdford-claude-skills-fitness-function-design)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
6mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Fitness Function Design? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Fitness Function Design

Design quantifiable metrics to measure architecture health and automatically enforce quality standards.

Context

You are designing fitness functions to measure architectural quality. Create metrics for coupling, modularity, scalability, performance. Automate checks in CI/CD for continuous feedback.

Domain Context

Based on evolutionary architecture and fitness function research (Thoughtworks):

  • Coupling Metrics: Layer violations, cyclic dependencies, test isolation
  • Modularity Metrics: Module fan-in/fan-out, cohesion, abstract instability
  • Scalability Metrics: Throughput (RPS), latency (p95, p99), resource utilization
  • Security Metrics: Secrets in code, dependency vulnerabilities, known security patterns
  • Code Quality Metrics: Complexity (cyclomatic), duplication, test coverage

Instructions

  1. Identify Key Quality Attributes: What matters most? Scalability? Security? Testability? Maintainability? Pick 3-4.
  1. Define Metrics for Each Attribute: Scalability: p99 latency 80% test coverage, no untestable dependencies.
  1. Set Thresholds: Below threshold: pass. Above: fail (blocks merge). Make thresholds achievable but stretch. Too strict: teams bypass. Too loose: no effect.
  1. Automate Checks: Integrate into CI/CD. Run on every PR. Parse test coverage reports, dependency scanners, performance benchmarks. Fail PR if fitness functions breach.
  1. Monitor and Adjust: Track metrics over time. Are they trending right? Do developers understand why they matter? Adjust thresholds based on feedback and organizational priorities.

Anti-Patterns

  • Too Many Fitness Functions: 50 metrics in CI/CD. Result: long builds, false positives, ignored. Guard: 5-10 core metrics max. Automate what matters; remove noise.
  • Fitness Functions Without Context: "Cyclomatic complexity > 10 fails". Developer doesn't understand why. Result: frustrated, rules bypassed. Guard: Document rationale; train teams; explain tradeoffs.
  • Static Thresholds: Set once, never changed. Organization evolves, thresholds stale. Result: metrics become irrelevant. Guard: Review quarterly; adjust based on trends and priorities.
  • Metrics Without Action: Fitness functions fail but no one addresses. Result: technical debt accumulates. Guard: Failed checks require action; track and fix root causes.

Further Reading

  • Evolutionary Architecture by Rebecca Parsons, Neal Ford, Patrick Kua — fitness function concepts
  • Building Microservices by Sam Newman — quality metrics for distributed systems
  • Accelerate by Nicole Forsgren — DORA metrics for deployment performance

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.