steerability-score

Quantify repository steerability with growth-invariant KPIs and guide refactoring.

30|12|Updated Jun 21, 2026
One-click install
npx skills add https://github.com/anthony-chaudhary/fak --skill steerability-score
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: steerability-score
Source: https://github.com/anthony-chaudhary/fak/tree/main/.claude/skills/steerability-score
Command: npx skills add https://github.com/anthony-chaudhary/fak --skill steerability-score

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill addresses the challenge of maintaining developer velocity in a growing codebase by measuring and improving structural steerability, ensuring that the effort required to navigate and modify the project remains constant even as the repository scales.

Core Features & Use Cases

  • Growth-Invariant Metrics: Provides a 0-100 steerability index based on modularity, coupling, and navigability KPIs that do not artificially inflate as the codebase size increases.
  • Structural Improvement: Guides the user through real architectural refactoring—such as splitting dispatch monoliths or breaking coupling hubs—rather than cosmetic changes.
  • Use Case: Run this scorecard after a major structural change or on a regular cadence to identify "drift" in the codebase and proactively reduce technical debt before it impacts development speed.

Quick Start

Run the steerability scorecard to measure the current index and identify the worst drift axis for improvement.

Frequently Asked Questions about steerability-score

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

FAQPage Schema
How do I measure codebase modularity and coupling as my repository grows?

Codebase modularity and coupling are measured using a 0-100 steerability index, which tracks structural navigability KPIs that remain growth-invariant as your repository scales. This prevents development effort from increasing alongside project size.

Why does development effort increase as my codebase scales?

Development effort increases during codebase scaling due to structural drift in modularity and coupling. An automated scorecard identifies these architectural bottlenecks, guiding refactoring workflows to keep navigation and modification effort flat.

What is the best way to identify architectural drift before it impacts velocity?

Running an automated scorecard analysis on a regular cadence is the best way to identify architectural drift. It quantifies structural steerability and pinpoints the worst coupling hubs or dispatch monoliths for targeted refactoring.

Do I need Python 3 to run the steerability scorecard scripts?

Yes, you need Python 3 and standard git tooling to execute the measurement scripts and validate structural integrity. These dependencies are required to quantify repository steerability and generate the scorecard analysis.

Can I use this scorecard to guide structural refactoring of dispatch monoliths?

Yes, the scorecard guides users through real architectural refactoring, such as splitting dispatch monoliths or breaking coupling hubs. It targets structural modularity improvements rather than cosmetic code changes to optimize repository steerability.

When should I run a repository steerability analysis?

You should run a repository steerability analysis after a major structural change or on a regular cadence. This proactively identifies codebase drift and reduces technical debt before it impacts development speed.